jclouds-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paya, Ashkan" <Ashkan.P...@dell.com>
Subject Re: AWS us-standard region
Date Tue, 04 Apr 2017 20:47:22 GMT
Hi Ignasi,

Sure, filed one https://issues.apache.org/jira/browse/JCLOUDS-1265. Also will send the corresponding
patch soon.


From: Ignasi Barrera <nacx@apache.org<mailto:nacx@apache.org>>
Reply-To: "user@jclouds.apache.org<mailto:user@jclouds.apache.org>" <user@jclouds.apache.org<mailto:user@jclouds.apache.org>>
Date: Monday, April 3, 2017 at 10:53 PM
To: "user@jclouds.apache.org<mailto:user@jclouds.apache.org>" <user@jclouds.apache.org<mailto:user@jclouds.apache.org>>
Subject: Re: AWS us-standard region

There is no reason AFAIK. Mind opening a bug in JIRA?

This also looks pretty straightforward to fix, do you want to try submitting a pull request
with the patch? I'll be happy to help!


On Apr 4, 2017 2:00 AM, "Paya, Ashkan" <Ashkan.Paya@dell.com<mailto:Ashkan.Paya@dell.com>>

According to (http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region) “us-standard”
got renamed to “us-east-1” some time back but in jclouds codebase[1] we still use the
former name. This causes BlobStore.listAssignableLocations to return an invalid region when
the user wants to list and specifically choose one, even though this is the default region.
Is there any reason for this inconsistence?

Thank you,

[1] apis/sts/src/main/java/org/jclouds/aws/domain/Region.java

View raw message