Centralize validation logic (Framework)
[Part 1 of 2]
Currently, we do all validations in the API layer. As we add more entry points (sink, MiniDNS, CLI tools), this logic is going to be needed.
We should investigate if it's possible to move some/all of this logic into the DesignateObject class where it can shared by all layers.
Mapping API v1+v2 style validation errors to a single validator will likely be the biggest roadblock.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Kiall Mac Innes
- Direction:
- Needs approval
- Assignee:
- Kiall Mac Innes
- Definition:
- Discussion
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Kiall Mac Innes
- Completed by
- Kiall Mac Innes
Related branches
Related bugs
Sprints
Whiteboard
The BP was filed in response to my comment on L68 of https:/
Gerrit topic: https:/
Addressed by: https:/
Convert Object FIELDS from list to dict
Addressed by: https:/
Migrate validations into the Objects
Addressed by: https:/
Implement a DesignateObject Registry
Addressed by: https:/
Support Nested/Recursive Object Validations
