API Version/Capability Detection
Going forward we *must* determine both the API versions and supported extensions for the endpoints rather than assuming them. This data would ideally be retrieved when the Horizon process is started, and should be stored in-memory and used to determine what clients to use and which features to hide/show/
Blueprint information
- Status:
- Complete
- Approver:
- Gabriel Hurley
- Priority:
- High
- Drafter:
- Gabriel Hurley
- Direction:
- Approved
- Assignee:
- None
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
-
ongoing
- Started by
- Gabriel Hurley
- Completed by
- David Lyle
Whiteboard
mrunge, Nov 20 2013: what's the status here? I see this has high prio and good progress. Do you have any code to inspect?
lcheng Feb 3 2014: Keystone client now provides a discovery class that provide a means to discover and create clients depending on the supported API
versions on the server. https:/
That would also clean-up some of the settings:
1. We would not need to specify the keystone version in the settings
2. We only need the KEYSTONE_BASE_URL rather than the URL with version in it.
This is probably a good candidate for J-1.
[david-lyle | 2015-08-12] No one is working on this and while a good idea, we have some workaround for it in place now. So marking obsolete. If someone is ready to work on a similar idea, we can start a new blueprint.
