Interopability With GCS for S3 QRep #502
Merged
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.
Support for using GCS buckets in S3 QRep
The S3 Peer now looks like:
Note that everything apart from
url
here is an optional field. If you leave any/all of the other fields out, they will be picked up from thedocker-compose.yml
file.auto
for automatically detecting region based on bucket locationThe conditions mentioned here still hold - ensure the GCS bucket you specify above exists already.
You can also set the AWS environment variables in
docker-compose.yml
Fixes #501