> Well, one developer would have to consult the provider docs to figure out the > values.
Yes, sure. What I meant was more: "if your provider uses non-standard values, each developer is going to have to configure his/her local environment with the correct system properties, and is going to have to ensure any production installation uses those correct values, too". Would it make sense to consider moving the validation into the API method, rather than keeping them in the domain object? Because it appears that the question of whether a particular domain object is "valid" or not depends not so much on the object itself, but on the provider? --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs-openstack/pull/46#issuecomment-27334686
