Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface CreateBackendRequest

example

Click here to see how to use CreateBackendRequest.

Hierarchy

Properties

backendSetName

backendSetName: string

The name of the backend set to which to add the backend server.

Example: `example_backend_set`

createBackendDetails

createBackendDetails: CreateBackendDetails

The details to add a backend server to a backend set.

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 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 current etag value of the resource.

networkLoadBalancerId

networkLoadBalancerId: string

The OCID of the network load balancer to update.

Optional opcRequestId

opcRequestId: undefined | string

The unique Oracle-assigned identifier for the request. If you must contact Oracle about a particular request, then provide the request identifier.

Optional opcRetryToken

opcRetryToken: undefined | string

A token that uniquely identifies a request so that it can be retried in case of a timeout or server error without risk of rerunning that same action. Retry tokens expire after 24 hours but they 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 might 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