OrchestrationV2s REST Endpoints
In earlier versions of Compute Classic, you could use orchestrations v1 to create and manage resources. From release 17.1.2 onwards, you can also create and provision resources using orchestrations v2.
Note: You should always use your orchestrations to manage resources that you've created using orchestrations. Don't, for example, use the web console or the REST API to delete an object that you created using an orchestration. This could cause your orchestration to either attempt to re-create the object and associated resources, or to go into an error state.
Also remember that you shouldn't try to use or manage resources created using orchestrations v1 by referencing them in orchestrations v2, or vice versa.
For more information, see About Orchestrations v2.
- Create an OrchestrationV2
- Method: postPath:
/platform/v1/orchestration/
- Delete an OrchestrationV2
- Method: deletePath:
/platform/v1/orchestration/{name}
- Retrieve Details of all OrchestrationV2 in a Container
- Method: getPath:
/platform/v1/orchestration/{container}/
- Retrieve Details of an OrchestrationV2
- Method: getPath:
/platform/v1/orchestration/{name}
- Retrieve Names of all OrchestrationV2 and Subcontainers in a Container
- Method: getPath:
/platform/v1/orchestration/{container}
- Retrieve Names of Containers
- Method: getPath:
/platform/v1/orchestration/
- Update an OrchestrationV2
- Method: putPath:
/platform/v1/orchestration/{name}