Barbican's Version API should be similar to Nova, Keystone, Manila, etc.
Barbican's Version API should be similar to Nova, Keystone, Manila, etc. This keeps Barbican consistent with other OpenStack projects and provides expected behavior. In addition, the version endpoint should not be protected as it currently is.
Examples:
Keystone: http://
Nova: http://
Manila: https:/
Blueprint information
- Status:
- Complete
- Approver:
- Douglas Mendizábal
- Priority:
- Medium
- Drafter:
- John Wood
- Direction:
- Approved
- Assignee:
- Juan Antonio Osorio Robles
- Definition:
- Approved
- Series goal:
- Accepted for liberty
- Implementation:
-
Implemented
- Milestone target:
-
1.0.0
- Started by
- Douglas Mendizábal
- Completed by
- Douglas Mendizábal
Related branches
Related bugs
Sprints
Whiteboard
See also the paste config file for Manila that configures the root version resource separately from the application resources (that start with /v1): https:/
atiwari:
It is addressed by https:/
Gerrit topic: https:/
This has already been merged.
Addressed by: https:/
Add tempest tests to run in devstack gate
Addressed by: https:/
Display all versions info in versions controller