Unify schema validation code for properties and parameters
In the current Heat code base we have a lot of duplicate code for schema validation for properties and parameters. The code should be refactored so we can share as much code as possible for property schemas and parameter schemas.
The benefit will be that developers do not have to get familiar with two completely different code paths for very similar use cases. Furthermore, the change will make future schema related enhancements easier.
Blueprint information
- Status:
- Complete
- Approver:
- Steve Baker
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Thomas Spatzier
- Definition:
- Approved
- Series goal:
- Accepted for icehouse
- Implementation:
-
Implemented
- Milestone target:
-
2014.1
- Started by
- Thomas Spatzier
- Completed by
- Thomas Spatzier
Related branches
Related bugs
| Bug #1230229: Heat constraints should be refactored to be common across parameters and properties | Fix Released |
Sprints
Whiteboard
This BP is a mirror of bug #1230229 to track dependency of https:/
The patches went into the master branch, so setting this BP to implemented.
Gerrit topic: https:/
Addressed by: https:/
Refactor Parameters Schema based on common Schema
Addressed by: https:/
Move param format for template-validate to API
Addressed by: https:/
Refactor Parameters Schema based on common Schema
Work Items
Dependency tree
* Blueprints in grey have been implemented.
