So what do we want to do here? I can make it return first item, I can add a check for jclouds.region, or whatever you guys want to do. I did a quick survey of some projects I know using HP Cloud and all of them were using jclouds.region so this would never have affected them.
I apologize for the possible blocker on the release, I never really considered that someone would depend on jclouds selecting a consistent default region. I can remedy this tonight if there is a consensus on what should happen here. Thanks, Chris -- Chris Custine On August 1, 2014 at 8:06:10 AM, Andrew Phillips (aphill...@qrmedia.com) wrote: > > We'll keep this thread posted about the progress. For specifics about > > the bug feel free to watch bug 645 [1]. > > Thanks for the update, Shri! Just to clarify: we're still considering > this a blocker at this point. > > ap >
