Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface DeleteBackendRequest

example

Click here to see how to use DeleteBackendRequest.

Hierarchy

Properties

backendName

backendName: string

The name of the backend server to remove. If the backend was created with an explicitly specified name, that name should be used here. If the backend was created without explicitly specifying the name, but was created using ipAddress, this is specified as :. If the backend was created without explicitly specifying the name, but was created using targetId, this is specified as :.

Example: {@code 10.0.0.3:8080} or {@code ocid1.privateip..oc1.<unique_ID>:8080}

backendSetName

backendSetName: string

The name of the backend set associated with the backend server.

Example: {@code example_backend_set}

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