The harm I'm not sure you are aware of is that people supply a value to this, and it isn't implemented. Without changing existing providers to throw, or some algo to make it work, a user calling this could be making a disasterous mistake in policy assumption.
That said, this is probably an already broken contract. For example there are probably othet parts of this class that are silently ignored. But then again.. broken windows shouldn't justify new ones. Anyway, you make the call. If it were me, I would add a disclaimer or Beta and who supports this on the method until we actually sort out how to address the others. That said, I don't feel strongly enough to say don't merge as I do see the pragmatic value in allowing one provider to escape labs. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds/pull/567#issuecomment-58689192
