Client Extensions
Provide a mechanism for separately installed client extensions to hook in to the openstackclient structure and leverage the existing authentication and client libs.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Dean Troyer
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
m2
- Started by
- Dean Troyer
- Completed by
- Dean Troyer
Related branches
Related bugs
Sprints
Whiteboard
A more complete and general plugin mechanism was implemented in https:/
An initial naive implementation just provides the structure to load a pre-defined entry point namespace.
Ultimately we may need to add hooks for adding to the global command parser (adding EXT_XXX_API_VERSION vars for example?) and the version table.
Also, by default commands will be pre-authenticated, we don't have a mechanism to support un-authenticated commands today, do we need one? And an extension hook for it too?
OpenStack extensions also have the ability to add/modify fields in the APIs. This needs to be considered.
Gerrit topic: https:/
Addressed by: https:/
Add a simple extension hook
