-
Notifications
You must be signed in to change notification settings - Fork 107
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Interopability With GCS for S3 QRep (#502)
### Support for using GCS buckets in S3 QRep The S3 Peer now looks like: ```sql CREATE PEER s3_gcs_interop_peer FROM S3 WITH ( url = 's3://<gcs_bucket_name>/<prefix>', access_key_id = '<access_key_id>', secret_access_key = '<secret>', region = 'auto' -- preferable for GCS, endpoint = 'https://storage.googleapis.com' -- must for GCS ); ``` 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 the `docker-compose.yml` file. - Set the Access Key ID and Secret to your GCS HMAC keys. [Click here for more information ](https://cloud.google.com/storage/docs/authentication/managing-hmackeys) - Set the region to `auto` for automatically detecting region based on bucket location - Set the endpoint to https://storage.googleapis.com The conditions mentioned [here](https://docs.peerdb.io/sql/commands/create-peer#considerations-4) 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
- Loading branch information
1 parent
1fa5903
commit 1716500
Showing
14 changed files
with
415 additions
and
93 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.