Re-order terms in role assignment API URLs
The v3 spec contains a series of URL APIs for role assignment management, e.g.:
PUT /domains/
This seems an un-natural ordering, especially in the light of us wanting to define additional terms to indicate inheritance. A more natural ordering within the url would be along the lines of how we describe a role assignment:
Create an assignment for "role X for User Y on Domain Z"
e.g. PUT /roles/
It is proposed that we use this new ordering going forward, deprecate the old ordering (but of course continue to support this for a few releases)
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Not
- Drafter:
- Henry Nash
- Direction:
- Needs approval
- Assignee:
- Henry Nash
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- None
- Started by
- Completed by
- Morgan Fainberg
Related branches
Related bugs
Sprints
Whiteboard
I can actually also see the argument for this ordering as an alternative:
Assign "User X role Y on Domain Z"
e.g. PUT /users/
I'd actually be OK with either of these - just not the current one!