> > HP should either have a default region for all language bindings > > @Chris: Would that work? If so, which region would make most sense?
If the desire is to set a default that matches the original region-a.geo-1 endpoint, then yes I think this would be the ONLY way to achieve it consistently. One of the problems with using first or last is that either one of them can change at any time depending on how keystone returns the endpoints list (adding a new region, for instance). My preference would be to force a caller to explicitly specify a region, but I think that will be the case anyway when we migrate to the new swift api provider from labs. Should I work this in to 1.8.1-SNAPSHOT later this week? Thanks, Chris -- Chris Custine On August 4, 2014 at 1:23:26 AM, Andrew Phillips (aphill...@qrmedia.com) wrote: > > We did not unhook google-cloud-storage from the release; not a release > > blocker but this could confuse users. > > Just to clarify: you mean we should probably *not* have released this? > > > HP should either have a default region for all language bindings > > @Chris: Would that work? If so, which region would make most sense? > > > Also we have not changed master from 1.8.0-SNAPSHOT to 2.0.0-SNAPSHOT. > > Thanks for the reminder. I have that commit waiting locally and am > planning to push it when the release goes out, although since we're > making a new branch there's actually not really a need for that. > > Everyone OK for 2.0.0-SNAPSHOT for master? > > Thanks for verifying and voting, Andrew G! > > ap >
