Options
All
  • Public
  • Public/Protected
  • All
Menu

Namespace DeleteReplicationRequest

example

Click here to see how to use DeleteReplicationRequest.

Properties

Optional deleteMode

deleteMode: DeleteMode

You can choose a mode for deleting the replication resource.

  • {@code FINISH_CYCLE_IF_CAPTURING_OR_APPLYING} Before deleting, complete the current delta cycle. If cycle is idle, delete immediately. Safest option.
  • {@code ONE_MORE_CYCLE} Before deleting, complete the current delta cycle, and initiate one more cycle. If cycle is idle, initiate one more cycle. Use for lossless failover.
  • {@code FINISH_CYCLE_IF_APPLYING} Before deleting, finish applying. If cycle is idle or capturing, delete immediately. Fastest option.

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.

Optional opcRequestId

opcRequestId: undefined | string

Unique identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.

replicationId

replicationId: string

The OCID of the replication.

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