Descriptionenvirons/ec2: specify public-bucket-region
Fixes LP #1083017
Our public bucket, juju-dist, lives in the us-east-1 region and can only be accessed via that endpoint. If you attempt to do so via another endpoint you get an unhelpful 301 error with an xml blob telling you how to request the bucket. The solution is to add a configuration option, with sensible default, to ec2/config.go to specify the region of the public bucket independantly of the private bucket.
https://code.launchpad.net/~dave-cheney/juju-core/052-environs-ec2-always-request-public-tools-from-us-east-1-II/+merge/136299
Requires: https://code.launchpad.net/~dave-cheney/juju-core/056-environs-ec2-tests-pass-on-quantal/+merge/136297
(do not edit description out of merge proposal)
Patch Set 1 #Patch Set 2 : environs/ec2: specify public-bucket-region #
Total comments: 6
Patch Set 3 : environs/ec2: specify public-bucket-region #Patch Set 4 : environs/ec2: specify public-bucket-region #Patch Set 5 : environs/ec2: specify public-bucket-region #Patch Set 6 : environs/ec2: specify public-bucket-region #Patch Set 7 : environs/ec2: specify public-bucket-region #
MessagesTotal messages: 11
|