fix: gateway authorization based on env #174
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fforbeck
force-pushed
the
fix/authorize-staging-gateway
branch
from
71a15c9 to
dcc33bc
Compare
Website preview 🔗✨ |
fforbeck
force-pushed
the
fix/authorize-staging-gateway
branch
from
dcc33bc to
77679ad
Compare
Peeja
requested changes
Dec 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to create new spaces in
Stagingorlocalhostenvironments we need to configure the w3up-client to authorize the correct gateway service, otherwise, it will default to the Production Storacha Gateway.This PR implements the logic to create the gateway connection based on the environment variables and passes that connection to the
w3up-client.createSpacecall, so the correct service is authorized.