Add capability for user to specify arbitrary version path
Bug #1413763 reported by
Terry Howe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack SDK |
Confirmed
|
Low
|
Unassigned |
Bug Description
The user should be able to have a user preference version preference to select a version module *and* the ability to select an arbitrary version path so they can access features the sdk may not know about. For instance if they wanted to access some network 2.1 API. They would specify some cli option like --os-api-
Changed in python-openstacksdk: | |
importance: | Undecided → Low |
Changed in python-openstacksdk: | |
status: | New → Confirmed |
milestone: | none → 1.0 |
Changed in python-openstacksdk: | |
milestone: | 1.0 → none |
Changed in python-openstacksdk: | |
assignee: | nobody → Marcellin Fom Tchassem (mf6510) |
Changed in python-openstacksdk: | |
assignee: | Marcellin Fom Tchassem (mf6510) → nobody |
To post a comment you must log in.
Right now, the --os-api-version option in the examples will allow something like a v2.1 path, but there is no fuzzy logic to match v2.1 to v2. Also, perhaps the --os-api- version- path option would allow more flexibility to the user if path should be something totally different than the version. For example v2 matches no version in the path or v2 matches 'two' in the path.