Move extensions into core
A large number of APIs have been implemented using the extension mechanism. We want to limit the use of extensions to things that are not supported. Some URLs will need to change as a result of refactoring the code, and backwards compatibility must be maintained. However, we can use microversions to limit the backwards compatibility to only versions below the microversion where the change is made.
Acceptance Criteria:
* Refactor the code such that there are no more extensions
* Ensure that for older microversions, the previous URLs redirect to the correct places
* Structure the change such that when the microversion that introduces this change is deprecated, the compatibility/
Blueprint information
- Status:
- Complete
- Approver:
- Ben Swartzlander
- Priority:
- Undefined
- Drafter:
- Valeriy Ponomaryov
- Direction:
- Needs approval
- Assignee:
- Valeriy Ponomaryov
- Definition:
- New
- Series goal:
- Accepted for mitaka
- Implementation:
-
Implemented
- Milestone target:
-
mitaka-1
- Started by
- Valeriy Ponomaryov
- Completed by
- Clinton Knight
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Port availability zones to core API
Addressed by: https:/
Port used limits to core API
Addressed by: https:/
Port quotas to core API
Addressed by: https:/
Port services to core API
Addressed by: https:/
Port manage/unmanage extensions to core API
Addressed by: https:/
Port share actions to core API
Addressed by: https:/
Port admin actions extension to core API
Addressed by: https:/
Port share type extensions to core API
Addressed by: https:/
Add new URLs for APIs ported from extensions
