Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface AddHeatWaveClusterRequest

example

Click here to see how to use AddHeatWaveClusterRequest.

Hierarchy

Properties

addHeatWaveClusterDetails

addHeatWaveClusterDetails: AddHeatWaveClusterDetails

Request to add a HeatWave cluster.

dbSystemId

dbSystemId: string

The DB System OCID.

Optional ifMatch

ifMatch: undefined | string

For optimistic concurrency control. In the PUT or DELETE call for a resource, set the If-Match header 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

Customer-defined unique identifier for the request. If you need to contact Oracle about a specific request, please provide the request ID that you supplied in this header with the request.

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

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