The admin api should be a class which inherits the openstack API
Currently the "admin api" is the normal api but just tacks access to certain functions to the api by adding routes. This is brilliant, but not very extensible. Instead there should be a subclassed AdminAPI that inherits from API. This way we can use all existing functions as well as override to alter them if necessary for administrative use. The API only functions wouldn't exist at all in the superclass API. I think this adds a bit of safety and readability as it separates the code from the two APIs and the API superclass can't call functions from its subclass AdminAPI.
This may even open the door for future types of APIs that we haven't even thought of yet. SimpleAPI, ProjectOwnerAPI, SuperUserAPI, etc.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Nova API Team
- Definition:
- Superseded
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
- Vish Ishaya
Related branches
Related bugs
Sprints
Whiteboard
not sure if this is the optimal approach, and it overlaps a bit with the separate-admin-api blueprint. I will leave it up to the nova-api team to sort out. --Vish
I really want the admin api to be a separate endpoint intended *only* for admin functionality. -- Waldon
