Extract Domain Logic out of DB and API layers
There is a lot of logic that lives in the db layer and the v1/v2 API layers that should really be handled in a single layer.
- policy checking
- notifications
- etc.
Blueprint information
- Status:
- Complete
- Approver:
- Brian Waldon
- Priority:
- High
- Drafter:
- Brian Waldon
- Direction:
- Approved
- Assignee:
- Mark Washenberger
- Definition:
- Drafting
- Series goal:
- Accepted for grizzly
- Implementation:
-
Implemented
- Milestone target:
-
2013.1
- Started by
- Brian Waldon
- Completed by
- Mark Washenberger
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add an image domain model and related helpers.
Addressed by: https:/
Add an image repo to encapsulate db api access
Addressed by: https:/
Add an image proxy to handle stored image data
Addressed by: https:/
Add an image repo proxy that handles notifications
Addressed by: https:/
Add domain proxies that do policy.enforce checks
Addressed by: https:/
Add domain proxies that stop unauthorized actions
Addressed by: https:/
Modify the v2 image controller to use domain model
Addressed by: https:/
Modify the v2 image tags to use domain model
Addressed by: https:/
Extend the domain model to v2 image data
