feat: use endpointURL for STORAGE_EMULATOR_HOST env var on GCS #47
Conversation
This file contains hidden or 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
If googleCredentials are in use and endpointURL is defined, the STORAGE_EMULATOR_HOST environment variable is set to the endpointURL value. This forces anonymous authentication. Signed-off-by: Francesco Canovai <[email protected]>
Contributor
Author
|
Closing this in favour of an alternative approach using environment variables. It would avoid tying endpointUrl (which in barman cloud is a aws only value) to gcs with the authentication side-effect. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
If googleCredentials are in use and endpointURL is defined, the STORAGE_EMULATOR_HOST environment variable is set to the endpointURL value. This forces anonymous authentication.