Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface ChangeMultiCloudResourceDiscoveryCompartmentRequest

example

Click here to see how to use ChangeMultiCloudResourceDiscoveryCompartmentRequest.

Hierarchy

  • BaseRequest
    • ChangeMultiCloudResourceDiscoveryCompartmentRequest

Properties

changeMultiCloudResourceDiscoveryCompartmentDetails

changeMultiCloudResourceDiscoveryCompartmentDetails: ChangeMultiCloudResourceDiscoveryCompartmentDetails

Moves the Multi Cloud Discovered resource to a different compartment.

Optional ifMatch

ifMatch: undefined | string

For optimistic concurrency control. In the PUT or DELETE call for a resource, set the {@code 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.

multiCloudResourceDiscoveryId

multiCloudResourceDiscoveryId: string

The OCID of the Multicloud Discovery Resource.

Optional opcRequestId

opcRequestId: undefined | string

The client request ID for tracing.

Optional opcRetryToken

opcRetryToken: undefined | string

A token that uniquely identifies a request, allowing it to be safely retried in the event of a timeout or server error without the risk of the action being executed more than once.

Retry tokens expire after 24 hours but can be invalidated sooner if conflicting operations occur.

For example, if a resource has been deleted and permanently purged from the system, a retry of the original creation request may be rejected.

Optional retryConfiguration

retryConfiguration: RetryConfiguration

RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made