Skip to content

Conversation

andreasjansson
Copy link
Member

Lets the user override the hardcoded s3 region (currently us-east-1).

@bfirsh
Copy link
Member

bfirsh commented Mar 9, 2021

Could this just use the standard AWS_DEFAULT_REGION environment variable?

Signed-off-by: Andreas Jansson <[email protected]>
@andreasjansson andreasjansson force-pushed the configurable-s3-region branch from cf5b709 to b39327b Compare March 9, 2021 20:54
@andreasjansson andreasjansson changed the title KEEPSAKE_S3_REGION env var respect AWS_DEFAULT_REGION env var Mar 9, 2021
@andreasjansson
Copy link
Member Author

@bfirsh yes good point! updated

Copy link
Member

@bfirsh bfirsh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of things:

  • S3 regions can also be set in the configuration file, and however else S3's standard discovery process works, so there is probably some logic in the S3 Go library that determines the region that should be used/reimplemented here.
  • Maybe needs documenting? Or if it's using the built-in behavior, then perhaps it's implied.

Either way this is a lot better than nothing, so let's run with this. :)

@bfirsh bfirsh merged commit dd65d11 into replicate:main Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants