If you don’t need an orchestration any more, you can delete the orchestration. When you delete an orchestration, it’s no longer listed on the Orchestrations page, and you can’t perform any action on it. Orchestrations v2 can be deleted even when they are in a ready or error state. In such cases, any resources that have been created by the orchestration and haven’t been stopped or deleted yet, are deleted when you delete the orchestration.
To complete this task, you must have the
Compute_Operationsrole. If this role isn’t assigned to you or you’re not sure, then ask your system administrator to ensure that the role is assigned to you in Oracle Cloud Infrastructure Classic Console. See Modifying User Roles in Managing and Monitoring Oracle Cloud.
The orchestration that you want to delete must be in the Ready, Suspended, Stopped, or Error state. You can’t delete an instance in a transient state such as Starting or Stopping.
- Sign in to the Compute Classic console. If your domain spans multiple sites, select the appropriate site. To change the site, click the Site menu near the top of the page.
- Click the Orchestrations tab.
- Identify the orchestration that you want to delete. From the menu, select Delete.
When you delete an orchestration that isn’t in the Stopped state, all existing resources created by the orchestration are deleted.When all objects created by the orchestration have been deleted, the orchestration itself is deleted and it is no longer listed on the Orchestrations page.
To delete an orchestration using the CLI, use the
opc compute orchestration-v2 delete command. For help with that command, run the command with the
-h option. For the instructions to install the CLI client, see Preparing to Use the Compute Classic CLI in CLI Reference for Oracle Cloud Infrastructure Compute Classic.
To delete orchestrations v2 using the API, use the
DELETE /platform/v1/orchestration/orchestrationName method. See REST API for Oracle Cloud Infrastructure Compute Classic.