Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface ChangeRemotePeeringConnectionCompartmentRequest

example

Click here to see how to use ChangeRemotePeeringConnectionCompartmentRequest.

Hierarchy

  • BaseRequest
    • ChangeRemotePeeringConnectionCompartmentRequest

Properties

changeRemotePeeringConnectionCompartmentDetails

changeRemotePeeringConnectionCompartmentDetails: ChangeRemotePeeringConnectionCompartmentDetails

Request to change the compartment of a remote peering connection.

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.

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 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).

remotePeeringConnectionId

remotePeeringConnectionId: string

The OCID of the remote peering connection (RPC).

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