Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface ChangeDeploymentBackupCompartmentRequest

example

Click here to see how to use ChangeDeploymentBackupCompartmentRequest.

Hierarchy

Properties

changeDeploymentBackupCompartmentDetails

changeDeploymentBackupCompartmentDetails: ChangeDeploymentBackupCompartmentDetails

Properties to change the compartment of a DeploymentBackup.

deploymentBackupId

deploymentBackupId: string

A unique DeploymentBackup identifier.

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 is updated or deleted only if the etag you provide matches the resource's current etag value.

Optional opcRequestId

opcRequestId: undefined | string

The client request ID for tracing.

Optional opcRetryToken

opcRetryToken: undefined | string

A token that uniquely identifies a request so it can be retried, in case of a timeout or server error, without the 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 was deleted and purged from the system, then a retry of the original creation request is 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