Port orchestration v1 to resource2/proxy2

Bug #1657787 reported by Brian Curtin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack SDK
Fix Released
Critical
Unassigned

Bug Description

Update the orchestration v1 service to use resource2/proxy2

When porting, do a walkthrough of the documentation to see if anything has changed so that we can keep the service updated.

tags: added: resource2-port
Qiming Teng (tengqim)
Changed in python-openstacksdk:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.