Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface ChangeLoadBalancerCompartmentRequest

example

Click here to see how to use ChangeLoadBalancerCompartmentRequest.

Hierarchy

Properties

changeLoadBalancerCompartmentDetails

changeLoadBalancerCompartmentDetails: ChangeLoadBalancerCompartmentDetails

The configuration details for moving a load balancer to a different compartment.

Optional ifMatch

ifMatch: undefined | 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 for the load balancer. This value can be obtained from a GET or POST response for any resource of that load balancer.

For example, the eTag returned by getListener can be specified as the ifMatch for updateRuleSets.

The resource is updated or deleted only if the ETag you provide matches the resource's current ETag value.

Example: {@code example-etag}

loadBalancerId

loadBalancerId: string

The OCID of the load balancer to move.

Optional opcRequestId

opcRequestId: undefined | string

The unique Oracle-assigned 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 (e.g., if a resource has been deleted and purged from the system, then 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