S3 - Add case handling for Us Standard zone #177
Merged
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
|
Hi @callicles, Thank you for your contribution! We really value the time you've taken to put this together. Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement: |
|
I signed the agreement |
callicles
changed the title
|
+1 |
patriknw
approved these changes
Feb 13, 2017
| case None => | ||
| region match { | ||
| case "us-east-1" => Uri.Host(s"${s3Location.bucket}.s3.amazonaws.com") | ||
| case _ => Uri.Host(s"${s3Location.bucket}.s3-$region.amazonaws.com") |
There was a problem hiding this comment.
ok, so us-east-1 is some kind of special default
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.
Add a quick fix for the US standard zone
#175 - #171