Throwing an error seems to make the most sense for now. Having jclouds pick what amounts to a random region seems worse than failing forward and throwing an error. ________________________________________ From: Andrew Gaul [g...@apache.org] Sent: Monday, August 04, 2014 7:26 PM To: dev@jclouds.apache.org Subject: Re: [DISCUSS] Release Apache jclouds 1.8.0 RC1
On Mon, Aug 04, 2014 at 11:47:03PM +0200, Andrew Phillips wrote: > I understand Andrew G's point about minimizing disruption for users, > but if I get this correctly (and I'm hardly the expert here) the > behaviour so far has simply been broken. > If we can document a way in the examples and/or release notes to > allow people to easily continue with the old behaviour if they wish, > that would be helpful. And obviously, it would be good to clarify if > we are confident that this behaviour won't change *again* with the > change to openstack-swift soon. While we could quibble over the existing broken behavior, changing the default from the first region to the last region is more broken. Even if we accept that users of the default region-a will now store blobs in region-b, if HP Cloud introduces region-c, jclouds will store data in it depending on the ordering that the openstack catalog provides! Instead we should define a default region or throw an error without a default. -- Andrew Gaul http://gaul.org/
