Make assignment model pluggable
The assignment controller and backend are really misnomers - there are effectively the "rest-of-identity", that was left over when we split out the actual identity piece (i.e. users and groups). Within this "assignment" component we have the store for domains, projects, roles....and the actual assignments themselves.
This blueprint process splitting the current "assignment" components into two, making each part more maintainable as well as enabling the part that actually represents our existing assignment model pluggable - hence allowing alternative models to be introduced.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Henry Nash
- Direction:
- Needs approval
- Assignee:
- Henry Nash
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
-
Implemented
- Milestone target:
-
2015.1.0
- Started by
- Henry Nash
- Completed by
- Henry Nash
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Make assignments pluggable.
Gerrit topic: https:/
Addressed by: https:/
Make controllers and managers reference new resource manager
Addressed by: https:/
Make unit tests call the new resource manager
Addressed by: https:/
Split the assignments controller
Addressed by: https:/
Move projects and domains to their own backend
Addressed by: https:/
Refactor assignment manager/driver methods
Addressed by: https:/
Make unit tests call the new, split out, role manager
Addressed by: https:/
Make controllers call the new, split out, role manager
Addressed by: https:/
Split roles into their own backend within assignments
