Allow roles to raise INVALID_VALUE and remove the instance
Review Request #155 - Created March 31, 2015 and submitted
|mitr, sgallagh, simo, twoerner|
Previously, we could only do limited checks on those options that were provided to the API, but this didn't allow us to check for missing attributes or attributes whose value is dependent on another setting, etc. With this patch, roles will be allowed to raise RolekitError(INVALID_VALUE) as long as they have not yet made any changes to the systemm
Attempted to create a database role with no settings file (and therefore no database name). The deployment failed but no invalid instance was left behind.