Update an OrchestrationV2
/platform/v1/orchestration/{name}
* 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
- application/oracle-compute-v3+json
-
name: string
The three-part name of the object (
/Compute-identity_domain/user/object
).
-
desired_state(optional): string
Manage the state of the orchestration objects by changing the desired state of the orchestration.
-
Cookie: string
The Cookie: header must be included with every request to the service. It must be set to the value of the set-cookie header in the response received to the POST /authenticate/ call.
object
-
account(optional):
string
/Compute-identity_domain/default
-
description(optional):
string
Description of this orchestration
-
desired_state:
string
Specify the desired state of this orchestration:
active
,inactive
, orsuspend
. Deletes only the non-persistent objects; persistent objects are not deleted when you change the state of an active orchestration to suspend. -
name:
string
The three-part name (
/Compute-identity_domain/user/object
) of the orchestration. -
objects:
array 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(optional):
array tags
Strings that describe the orchestration and help you identify it.
-
version:
integer
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.
array
-
Array of:
object OrchestrationObject-post-request
The request body contains details of the orchestration object that you want to create.
object
-
account(optional):
string
/Compute-identity_domain/default
-
description(optional):
string
A text string describing the object.
-
desired_state(optional):
string
The desired state of this object
-
label:
string
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.
-
name(optional):
string
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. -
orchestration:
string
The three-part name (
/Compute-identity_domain/user/object
) of the orchestration to which the object belongs. -
persistent(optional):
boolean
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 tofalse
. 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(optional):
array 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:
object template
Additional Properties Allowed: additionalPropertiesThe 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 beStorageVolume
, and thetemplate
would includesize
andbootable
. If you want to create an instance, the type would beInstance
, and the template would include instance-specific attributes, such asimagelist
andshape
. -
type:
string
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(optional):
integer
Version of this object, generated by the server
array
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.
-
Array of:
object items
Additional Properties Allowed: additionalProperties
object
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
.
object
object
Response
- application/oracle-compute-v3+json
200 Response
-
set-cookie: string
The cookie value is returned if the session is extended
object
-
account(optional):
string
The default Compute Classic account, such as /Compute-acme/default.
-
description(optional):
string
Description of this orchestration
-
desired_state(optional):
string
The
desired_state
specified in the orchestration JSON file. A unique identifier for this orchestration. -
id(optional):
string
Unique identifier of this orchestration
-
name(optional):
string
The three-part name (
/Compute-identity_domain/user/object
) of the orchestration. -
objects(optional):
array objects
List of orchestration objects
-
status(optional):
string
Current status of this orchestration
-
tags(optional):
array tags
Strings that describe the orchestration and help you identify it.
-
time_audited(optional):
string
Time the orchestration was last audited
-
time_created(optional):
string
The time when the orchestration was added to Compute Classic.
-
time_updated(optional):
string
The time when the orchestration was last updated in Compute Classic.
-
uri(optional):
string
Uniform Resource Identifier
-
user(optional):
string
Name of the user who added this orchestration or made the most recent update to this orchestration.
-
version(optional):
integer
Version of this orchestration. It is automatically generated by the server.
object
-
account(optional):
string
/Compute-identity_domain/default
-
description(optional):
string
Description of this object
-
desired_state(optional):
string
The desired state of this object
-
health(optional):
object health
Additional Properties Allowed: additionalPropertiesDictionary containing the current state of the object
-
label(optional):
string
Human-readable identifier for this object
-
name(optional):
string
Name of this object, generated by the server
-
orchestration(optional):
string
The orchestration to which this object belongs
-
persistent(optional):
boolean
If the value is
true
, it indicates that the object is not deleted when the associated orchestration is suspended. If persistent is set tofalse
, the object is deleted when the associated orchestration is suspended. -
relationships(optional):
array relationships
List of relationships to other objects
-
template(optional):
object template
Additional Properties Allowed: additionalPropertiesTemplate of this object object
-
time_audited(optional):
string
Time the object was last audited
-
time_created(optional):
string
Object creation time
-
time_updated(optional):
string
Object modification time
-
type(optional):
string
Type of object this object represents
-
uri(optional):
string
Uniform Resource Identifier
-
user(optional):
string
User acting on this object
-
version(optional):
integer
Version of this object, generated by the server
object
array
-
Array of:
object items
Additional Properties Allowed: additionalProperties
object
object
object
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
andjack.jones@example.com
are example values. Replaceacme
with the identity domain ID of your Compute Classic account, andjack.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
andjack.jones@example.com
are example values. Replaceacme
with the identity domain ID of your Compute Classic account, andjack.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/firstorchestration
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=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
andjack.jones@example.com
are example values. Replaceacme
with the identity domain ID of your Compute Classic account, andjack.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
andjack.jones@example.com
are example values. Replaceacme
with the identity domain ID of your Compute Classic account, andjack.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:
-
Get the latest JSON body of the orchestration using the GET /platform/v1/orchestration/{name} HTTP request.
-
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 theobject
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.
-
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
andjack.jones@example.com
are example values. Replaceacme
with the identity domain ID of your Compute Classic account, andjack.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" }