ChangeCloudExadataInfrastructureCompartment
POST {{baseUrl}}/cloudExadataInfrastructures/:cloudExadataInfrastructureId/actions/changeCompartment
Moves a cloud Exadata infrastructure resource and its dependent resources to another compartment. Applies to Exadata Cloud Service instances and Autonomous Database on dedicated Exadata infrastructure only.For more information about moving resources to a different compartment, see Moving Database Resources to a Different Compartment.
Request Body
{"compartmentId"=>"<string>"}
HEADERS
| Key | Datatype | Required | Description |
|---|---|---|---|
opc-retry-token | string | A token that uniquely identifies a request so it can be retried in case of a timeout or | |
| server error without risk of executing that same action again. Retry tokens expire after 24 | |||
| hours, but can be invalidated before then due to conflicting operations (for example, if a resource | |||
| has been deleted and purged from the system, then a retry of the original creation request | |||
| may be rejected). | |||
opc-request-id | string | Unique identifier for the request. | |
if-match | string | For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match | |
| parameter to the value of the etag from a previous GET or POST response for that resource. The resource | |||
| will be updated or deleted only if the etag you provide matches the resource's current etag value. | |||
Content-Type | string | ||
Accept | string |