Update an OrchestrationV2

put

/platform/v1/orchestration/{name}

Orchestration cannot be updated when they are in the activating, suspending, or deactivating state. However, you can terminate or delete an orchestration irrespective of the current state of the orchestration.

* To activate an orchestration, use the PUT /platform/v1/orchestration/orchestrationName?desired_state=active method.

* To delete all the nonpersistent objects defined in the orchestration, use the PUT /platform/v1/orchestration/orchestrationName?desired_state=suspend method. When you suspend an active orchestration, only the nonpersistent objects are deleted; the persistent objects are not deleted.

* To delete all the objects in an orchestration, use the PUT /platform/v1/orchestration/orchestrationName?desired_state=inactive method.

Note: Instead of using PUT /platform/v1/orchestration/ to add, remove, or modify individual objects, use the Object API.

* To add an object to the orchestration, send the POST /platform/v1/object/ request.

* To modify an existing object in the orchestration, send the PUT /platform/v1/object/{name} request.

* To delete an object from the orchestration, send the DELETE /platform/v1/object/{name} request.

If you want to update an orchestration, get the latest version of the orchestration by sending the GET /platform/v1/orchestration/{name} request. Modify the orchestration as per your requirements, and then use the PUT /platform/v1/orchestration/{name} request to update the orchestration. Ensure that you specify the latest version of the orchestration in the request body.

Required Role: To complete this task, you must have the Compute_Operations role. 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 My Services. See Modifying User Roles in Managing and Monitoring Oracle Cloud.

Request

Supported Media Types
Path Parameters
  • The three-part name of the object (/Compute-identity_domain/user/object).
Query Parameters
Header Parameters
Body ()
The request body contains details of the orchestrationV2 that you want to update.
Root Schema : OrchestrationV2-put-request
Type: object
The request body contains details of the orchestrationV2 that you want to update.
Show Source
  • /Compute-identity_domain/default
  • Description of this orchestration
  • Specify the desired state of this orchestration: active, inactive, or suspend. Deletes only the non-persistent objects; persistent objects are not deleted when you change the state of an active orchestration to suspend.
  • The three-part name (/Compute-identity_domain/user/object) of the orchestration.
  • objects
    The list of objects in the orchestration. An object is the primary building block of an orchestration. An orchestration can contain up to 100 objects.
  • tags
    Strings that describe the orchestration and help you identify it.
  • Specify the latest version of the orchestration in the request body. Before updating the orchestration, retrieve its details. This ensures that you only update the latest version of the orchestration.
Nested Schema : objects
Type: array
The list of objects in the orchestration. An object is the primary building block of an orchestration. An orchestration can contain up to 100 objects.
Show Source
Nested Schema : tags
Type: array
Strings that describe the orchestration and help you identify it.
Show Source
Nested Schema : OrchestrationObject-post-request
Type: object
The request body contains details of the orchestration object that you want to create.
Show Source
  • /Compute-identity_domain/default
  • A text string describing the object.
  • The desired state of this object
  • A text string describing the object. Labels can't include spaces. In an orchestration, the label for each object must be unique. Maximum length is 256 characters.
  • The four-part name of the object (/Compute-identity_domain/user/orchestration/object). If you don't specify a name for this object, the name is generated automatically. Object names can contain only alphanumeric characters, hyphens, underscores, and periods. Object names are case-sensitive. When you specify the object name, ensure that an object of the same type and with the same name doesn't already exist. If such a object already exists, then another object of the same type and with the same name won't be created and the existing object won't be updated.
  • The three-part name (/Compute-identity_domain/user/object) of the orchestration to which the object belongs.
  • Specifies whether the object should persist when the orchestration is suspended. Specify one of the following:

    * true: The object persists when the orchestration is suspended.

    * false: The object is deleted when the orchestration is suspended.

    By default, persistent is set to false. It is recommended that you specify true for storage volumes and other critical objects. Persistence applies only when you're suspending an orchestration. When you terminate an orchestration, all the objects defined in it are deleted.

  • relationships
    The relationship between the objects that are created by this orchestration. The only supported relationship is depends, indicating that the specified target objects must be created first.

    Note that when recovering from a failure, the orchestration doesn't consider object relationships. Orchestrations v2 use object references to recover interdependent objects to a healthy state. SeeObject References and Relationships in Using Oracle Cloud Infrastructure Compute Classic.

  • template
    Additional Properties Allowed: additionalProperties
    The template attribute defines the properties or characteristics of the Compute Classic object that you want to create, as specified by the type attribute.

    The fields in the template section vary depending on the specified type. See Orchestration v2 Attributes Specific to Each Object Type in Using Oracle Cloud Infrastructure Compute Classic to determine the parameters that are specific to each object type that you want to create.

    For example, if you want to create a storage volume, the type would be StorageVolume, and the template would include size and bootable. If you want to create an instance, the type would be Instance, and the template would include instance-specific attributes, such as imagelist and shape.

  • Specify one of the following object types that you want to create.

    * Acl

    * Backup

    * BackupConfiguration

    * Instance

    * IpAddressAssociation

    * IpAddressPrefixSet

    * IpAddressReservation

    * IpNetwork

    * IpNetworkExchange

    * IPReservation

    * OSSContainer

    * Restore

    * Route

    * SecApplication

    * SecIPList

    * SecList

    * SecRule

    * SecurityProtocol

    * SecurityRule

    * SSHKey

    * StorageAttachment

    * StorageSnapshot

    * StorageSnapshot

    * StorageVolume

    * VirtualNicSet

    For the most up-to-date information about the supported object types, see Object Types in Orchestgations v2 in Using Oracle Cloud Infrastructure Compute Classic.

  • Version of this object, generated by the server
Nested Schema : relationships
Type: array
The relationship between the objects that are created by this orchestration. The only supported relationship is depends, indicating that the specified target objects must be created first.

Note that when recovering from a failure, the orchestration doesn't consider object relationships. Orchestrations v2 use object references to recover interdependent objects to a healthy state. SeeObject References and Relationships in Using Oracle Cloud Infrastructure Compute Classic.

Show Source
Nested Schema : template
Type: object
Additional Properties Allowed
Show Source
The template attribute defines the properties or characteristics of the Compute Classic object that you want to create, as specified by the type attribute.

The fields in the template section vary depending on the specified type. See Orchestration v2 Attributes Specific to Each Object Type in Using Oracle Cloud Infrastructure Compute Classic to determine the parameters that are specific to each object type that you want to create.

For example, if you want to create a storage volume, the type would be StorageVolume, and the template would include size and bootable. If you want to create an instance, the type would be Instance, and the template would include instance-specific attributes, such as imagelist and shape.

Nested Schema : items
Type: object
Additional Properties Allowed
Show Source
Nested Schema : additionalProperties
Type: object
Nested Schema : additionalProperties
Type: object

Response

Supported Media Types

200 Response

OK. See Status Codes for information about other possible HTTP status codes.
Headers
Body ()
Root Schema : OrchestrationV2-response
Type: object
Show Source
Nested Schema : objects
Type: array
List of orchestration objects
Show Source
Nested Schema : tags
Type: array
Strings that describe the orchestration and help you identify it.
Show Source
Nested Schema : OrchestrationObject-response
Type: object
Show Source
Nested Schema : health
Type: object
Additional Properties Allowed
Show Source
Dictionary containing the current state of the object
Nested Schema : relationships
Type: array
List of relationships to other objects
Show Source
Nested Schema : template
Type: object
Additional Properties Allowed
Show Source
Template of this object object
Nested Schema : additionalProperties
Type: object
Nested Schema : items
Type: object
Additional Properties Allowed
Show Source
Nested Schema : additionalProperties
Type: object
Nested Schema : additionalProperties
Type: object

Examples

Activating an Orchestration

cURL Command

When you activate an orchestration, the objects defined in it are created and the orchestration moves to the active state. You can activate an orchestration which is in the inactive or suspend state.

Note:

If the desired_state parameter is set to active in the orchestration JSON file, the orchestration is automatically activated after it is uploaded to Compute Classic.

The following example shows how to activate an orchestration, /Compute-acme/jack.jones@example.com/firstOrchestration, by submitting a PUT request on the REST resource using cURL. For information about cURL, see Use cURL.

Enter the command on a single line. Line breaks are used in this example for readability.

curl -i -X PUT
     -H "Cookie: $COMPUTE_COOKIE"
     -H "Content-Type: application/oracle-compute-v3+json"
     -H "Accept: application/oracle-compute-v3+json"
     https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration?desired_state=active
  • COMPUTE_COOKIE is the name of the variable in which you stored the authentication cookie earlier. For information about retrieving the authentication cookie and storing it in a variable, see Authentication.

  • api-z999.compute.us0.oraclecloud.com is an example REST endpoint URL. Change this value to the REST endpoint URL of your Compute Classic site. For information about finding out REST endpoint URL for your site, see Send Requests.

  • acme and jack.jones@example.com are example values. Replace acme with the identity domain ID of your Compute Classic account, and jack.jones@example.com with your user name.

Example of Response Body

The following example shows the response body in JSON format when you activate an orchestration.

{
	"status": "activating",
	"account": "/Compute-acme/default",
	"time_updated": "2017-03-08T17:00:20Z",
	"description": "",
	"tags": [],
	"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration",
	"time_created": "2017-03-08T14:14:25Z",
	"name": "/Compute-acme/jack.jones@example.com/firstOrchestration",
	"time_audited": "2017-03-08T17:00:12Z",
	"objects": [{
		"relationships": [],
		"account": "/Compute-acme/default",
		"time_updated": "2017-03-08T17:00:20Z",
		"description": "",
		"user": "/Compute-acme/jack.jones@example.com",
		"persistent": false,
		"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/object/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7",
		"template": {
			"name": "/Compute-acme/jack.jones@example.com/seclist"
		},
		"label": "my-first-seclist",
		"time_audited": null,
		"version": 2,
		"health": {
			"status": "inactive"
		},
		"time_created": "2017-03-08T14:14:25Z",
		"orchestration": "/Compute-acme/jack.jones@example.com/firstOrchestration",
		"type": "SecList",
		"name": "/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7"
	}],
	"user": "/Compute-acme/jack.jones@example.com",
	"version": 2,
	"id": "dd3d3d40-a2ab-434f-be5c-1acfbb200872",
	"desired_state": "active"
}

The status of the orchestration of changes to activating, and then to active when the objects defined in the orchestration are created.

To monitor the status of the orchestration, send the GET /platform/v1/orchestration/{name} request.

Suspending an Orchestration

cURL Command

You can suspend an orchestration which is in the inactive or active state. When you suspend an orchestration which is in the active state, all non-persistent objects that were provisioned by that orchestration are deleted. The persistent objects are not deleted. When you suspend an orchestration which is in the inactive state, the persistent objects are created and non-persistent objects are not created. The following example shows how to suspend an orchestration, /Compute-acme/jack.jones@example.com/firstorchestration, which is in the active state by submitting a PUT request on the REST resource using cURL. For more information about cURL, see Use cURL.

Enter the command on a single line. Line breaks are used in this example for readability.

curl -i -X PUT
     -H "Cookie: $COMPUTE_COOKIE"
     -H "Content-Type: application/oracle-compute-v3+json"
     -H "Accept: application/oracle-compute-v3+json"
     https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration?desired_state=suspend
  • COMPUTE_COOKIE is the name of the variable in which you stored the authentication cookie earlier. For information about retrieving the authentication cookie and storing it in a variable, see Authentication.

  • api-z999.compute.us0.oraclecloud.com is an example REST endpoint URL. Change this value to the REST endpoint URL of your Compute Classic site. For information about finding out REST endpoint URL for your site, see Send Requests.

  • acme and jack.jones@example.com are example values. Replace acme with the identity domain ID of your Compute Classic account, and jack.jones@example.com with your user name.

Example of Response Body

The following example shows the response body in JSON format when you suspend an orchestration. All persistent objects, persistent: true, are created if they were not already created. All the non-persistent, persistent: false, objects are deleted.

{
	"status": "suspending",
	"account": "/Compute-acme/default",
	"time_updated": "2017-03-08T18:56:53Z",
	"description": "",
	"tags": [],
	"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration",
	"time_created": "2017-03-08T14:14:25Z",
	"name": "/Compute-acme/jack.jones@example.com/firstOrchestration",
	"time_audited": "2017-03-08T18:56:52Z",
	"objects": [{
		"relationships": [],
		"account": "/Compute-acme/default",
		"time_updated": "2017-03-08T18:56:53Z",
		"description": "",
		"user": "/Compute-acme/jack.jones@example.com",
		"persistent": false,
		"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/object/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7",
		"template": {
			"name": "/Compute-acme/jack.jones@example.com/seclist"
		},
		"label": "my-first-seclist",
		"time_audited": "2017-03-08T18:56:18Z",
		"version": 5,
		"health": {
			"status": "active",
			"object": {
				"account": "/Compute-acme/default",
				"description": "",
				"uri": "https://api-z999.compute.us0.oraclecloud.com/seclist/Compute-acme/jack.jones@example.com/seclist",
				"outbound_cidr_policy": "PERMIT",
				"policy": "DENY",
				"name": "/Compute-acme/jack.jones@example.com/seclist"
			}
		},
		"time_created": "2017-03-08T14:14:25Z",
		"orchestration": "/Compute-acme/jack.jones@example.com/firstOrchestration",
		"type": "SecList",
		"name": "/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7"
	}],
	"user": "/Compute-acme/jack.jones@example.com",
	"version": 5,
	"id": "dd3d3d40-a2ab-434f-be5c-1acfbb200872",
	"desired_state": "suspend"
}

As the object defined in the orchestration is not persistent, the object is deleted. The status of the orchestration changes to suspending, and then to suspend when the object is deleted.

To monitor the status of the orchestration, send the GET /platform/v1/orchestration/{name} request.

Releasing an Orchestration

cURL Command

You can release an orchestration which is in the inactive or active state. When you release an orchestration, the orchestration is deleted along with all the orchestration objects but it doesn???t delete the underlying objects provisioned by the orchestration. The following example shows that how to release an orchestration, /Compute-acme/jack.jones@example.com/firstorchestrationby submitting a PUT request on the REST resource using cURL. For more information about cURL, see Use cURL.

Enter the command on a single line. Line breaks are used in this example for readability.

curl -i -X PUT
     -H "Cookie: $COMPUTE_COOKIE"
     -H "Content-Type: application/oracle-compute-v3+json"
     -H "Accept: application/oracle-compute-v3+json"
     https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration?desired_state=release
  • COMPUTE_COOKIE is the name of the variable in which you stored the authentication cookie earlier. For information about retrieving the authentication cookie and storing it in a variable, see Authentication.

  • api-z999.compute.us0.oraclecloud.com is an example REST endpoint URL. Change this value to the REST endpoint URL of your Compute Classic site. For information about finding out REST endpoint URL for your site, see Send Requests.

  • acme and jack.jones@example.com are example values. Replace acme with the identity domain ID of your Compute Classic account, and jack.jones@example.com with your user name.

Example of Response Body

The following example shows the response body in JSON format when you release an orchestration. The orchestration, /Compute-acme/jack.jones@example.com/firstorchestration, and the orchestration object Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7 is deleted but it does not impact the underlying object, /Compute-acme/jack.jones@example.com/seclist

{
	"status": "deleting",
	"account": "/Compute-acme/default",
	"time_updated": "2017-03-08T19:16:53Z",
	"description": "",
	"tags": [],
	"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration",
	"time_created": "2017-03-08T14:14:25Z",
	"name": "/Compute-acme/jack.jones@example.com/firstOrchestration",
	"time_audited": "2017-03-08T18:56:52Z",
	"objects": [{
		"relationships": [],
		"account": "/Compute-acme/default",
		"time_updated": "2017-03-08T19:15:53Z",
		"desired_state": "inherit",
		"description": "",
		"user": "/Compute-acme/jack.jones@example.com",
		"persistent": false,
		"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/object/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7",
		"template": {
			"name": "/Compute-acme/jack.jones@example.com/seclist"
		},
		"label": "my-first-seclist",
		"time_audited": "2017-03-08T18:56:18Z",
		"version": 6,
		"health": {
			"status": "active",
			"object": {
				"account": "/Compute-acme/default",
				"description": "",
				"uri": "https://api-z999.compute.us0.oraclecloud.com/seclist/Compute-acme/jack.jones@example.com/seclist",
				"outbound_cidr_policy": "PERMIT",
				"policy": "DENY",
				"name": "/Compute-acme/jack.jones@example.com/seclist"
			}
		},
		"time_created": "2017-03-08T14:14:25Z",
		"orchestration": "/Compute-acme/jack.jones@example.com/firstOrchestration",
		"type": "SecList",
		"name": "/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7"
	}],
	"user": "/Compute-acme/jack.jones@example.com",
	"version": 6,
	"id": "dd3d3d40-a2ab-434f-be5c-1acfbb200872",
	"desired_state": "release"
}

The status of the orchestration changes to deleting, and then the orchestration and orchestration object is deleted. The underlying objects are not deleted.

Terminating an Orchestration

cURL Command

When you terminate an orchestration, all objects that were provisioned by that orchestration are deleted. When you terminate an orchestration which is in the active or suspend state, the state of the orchestration changes to inactive. The following example shows how to terminate an orchestration, /Compute-acme/jack.jones@example.com/simple_orchestration, by submitting a PUT request on the REST resource using cURL. For more information about cURL, see Use cURL.

Enter the command on a single line. Line breaks are used in this example for readability.

curl -i -X PUT
     -H "Cookie: $COMPUTE_COOKIE"
     -H "Content-Type: application/oracle-compute-v3+json"
     -H "Accept: application/oracle-compute-v3+json"
     https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration?desired_state=inactive
  • COMPUTE_COOKIE is the name of the variable in which you stored the authentication cookie earlier. For information about retrieving the authentication cookie and storing it in a variable, see Authentication.

  • api-z999.compute.us0.oraclecloud.com is an example REST endpoint URL. Change this value to the REST endpoint URL of your Compute Classic site. For information about finding out REST endpoint URL for your site, see Send Requests.

  • acme and jack.jones@example.com are example values. Replace acme with the identity domain ID of your Compute Classic account, and jack.jones@example.com with your user name.

Example of Response Body

The following example shows the response body in JSON format when you terminate an orchestration which is in the active state.

{
  "status": "deactivating",
  "account": "/Compute-acme/default",
  "time_updated": "2017-03-08T18:41:00Z",
  "description": "",
  "tags": [
    
  ],
  "uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/firstOrchestration",
  "time_created": "2017-03-08T14:14:25Z",
  "name": "/Compute-acme/jack.jones@example.com/firstOrchestration",
  "time_audited": "2017-03-08T18:40:52Z",
  "objects": [
    {
      "relationships": [
        
      ],
      "account": "/Compute-acme/default",
      "time_updated": "2017-03-08T18:41:00Z",
      "description": "",
      "user": "/Compute-acme/jack.jones@example.com",
      "persistent": false,
      "uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/object/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7",
      "template": {
        "name": "/Compute-acme/jack.jones@example.com/seclist"
      },
      "label": "my-first-seclist",
      "time_audited": "2017-03-08T18:40:48Z",
      "version": 3,
      "health": {
        "status": "active",
        "object": {
          "account": "/Compute-acme/default",
          "description": "",
          "uri": "https://api-z999.compute.us0.oraclecloud.com/seclist/Compute-acme/jack.jones@example.com/seclist",
          "outbound_cidr_policy": "PERMIT",
          "policy": "DENY",
          "name": "/Compute-acme/jack.jones@example.com/seclist"
        }
      },
      "time_created": "2017-03-08T14:14:25Z",
      "orchestration": "/Compute-acme/jack.jones@example.com/firstOrchestration",
      "type": "SecList",
      "name": "/Compute-acme/jack.jones@example.com/firstOrchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7"
    }
  ],
  "user": "/Compute-acme/jack.jones@example.com",
  "version": 3,
  "id": "dd3d3d40-a2ab-434f-be5c-1acfbb200872",
  "desired_state": "inactive"
}

The status of the orchestration changes to deactivating, and then inactive when the objects defined in the orchestration are deleted.

To monitor the status of the orchestration, send the GET /platform/v1/orchestration/{name} request.

Updating the request body of an orchestration

Instead of using this request to add, remove, or modify individual objects, use the Object API. You can use this request to modify multiple objects in an orchestration.

To modify multiple objects in an orchestration:

  1. Get the latest JSON body of the orchestration using the GET /platform/v1/orchestration/{name} HTTP request.

  2. Copy the response body to a new JSON file and update the file based on your requirements. For example, you can delete objects by deleting their entries in the object field, and you can add new ones by adding their entries to the object field. You can also modify the attributes of existing objects.

    You must specify the latest version of the orchestration in the request body of the updated orchestration.

  3. Save the changes, and then pass the updated file with the PUT request.

In the following example, updated_orch.json contains the updated object fields for /Compute-acme/jack.jones@example.com/simple_orchestration. In this example, the SSH key, instance, storage volumes, and IP reservation objects are deleted from the orchestration and a security list is added to the orchestration.

cURL Command

Enter the command on a single line. Line breaks are used in this example for readability.

curl -i -X PUT
     -H "Cookie: $COMPUTE_COOKIE"
     -H "Content-Type: application/oracle-compute-v3+json"
     -H "Accept: application/oracle-compute-v3+json"
     -d "@updated_orch.json"
     https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/simple_orchestration
  • COMPUTE_COOKIE is the name of the variable in which you stored the authentication cookie earlier. For information about retrieving the authentication cookie and storing it in a variable, see Authentication.

  • api-z999.compute.us0.oraclecloud.com is an example REST endpoint URL. Change this value to the REST endpoint URL of your Compute Classic site. For information about finding out REST endpoint URL for your site, see Send Requests.

  • acme and jack.jones@example.com are example values. Replace acme with the identity domain ID of your Compute Classic account, and jack.jones@example.com with your user name.

Example Request Body

{
	"desired_state": "inactive",
	"name": "/Compute-acme/jack.jones@example.com/simple_orchestration",
  "version": 2,
  "objects": [{
		"template": {
			"name": "/Compute-acme/jack.jones@example.com/security-list1", 
      "outbound_cidr_policy": "PERMIT", 
      "policy": "DENY"
		},
		"label": "my-seclist",
		"type": "SecList"
	}]
}

Example Response Body

{
	"status": "inactive",
	"account": "/Compute-acme/default",
	"time_updated": "2017-03-08T17:00:20Z",
	"description": "",
	"tags": [],
	"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/orchestration/Compute-acme/jack.jones@example.com/simple_orchestration",
	"time_created": "2017-03-08T14:14:25Z",
	"name": "/Compute-acme/jack.jones@example.com/simple_orchestration",
	"time_audited": "2017-03-08T17:00:12Z",
	"objects": [{
		"relationships": [],
		"account": "/Compute-acme/default",
		"time_updated": "2017-03-08T17:00:20Z",
		"description": "",
		"user": "/Compute-acme/jack.jones@example.com",
		"persistent": false,
		"uri": "https://api-z999.compute.us0.oraclecloud.com/platform/v1/object/Compute-acme/jack.jones@example.com/simple_orchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7",
		"template": {
			"name": "/Compute-acme/jack.jones@example.com/security-list1",
      "outbound_cidr_policy": "PERMIT", 
      "policy": "DENY"
		},
		"label": "my-seclist",
		"time_audited": null,
		"version": 1,
		"health": {
			"status": "inactive"
		},
		"time_created": "2017-03-08T14:14:25Z",
		"orchestration": "/Compute-acme/jack.jones@example.com/simple_orchestration",
		"type": "SecList",
		"name": "/Compute-acme/jack.jones@example.com/simple_orchestration/c18a1d1b-fdf4-48fd-b6f7-271bfa4d8bd7"
	}],
	"user": "/Compute-acme/jack.jones@example.com",
	"version": 3,
	"id": "dd3d3d40-a2ab-434f-be5c-1acfbb200872",
	"desired_state": "inactive"
}