Class AddUtilityNodesRequest
Implements
Inherited Members
Namespace: Oci.BdsService.Requests
Assembly: OCI.DotNetSDK.Bds.dll
Syntax
public class AddUtilityNodesRequest : IOciRequest
Examples
Click here to see an example of how to use AddUtilityNodes request.
Properties
AddUtilityNodesDetails
Declaration
[Required(ErrorMessage = "AddUtilityNodesDetails is required.")]
[HttpConverter(TargetEnum.Body)]
public AddUtilityNodesDetails AddUtilityNodesDetails { get; set; }
Property Value
Type | Description |
---|---|
AddUtilityNodesDetails | Details for the newly added nodes. |
Remarks
Required
BdsInstanceId
Declaration
[Required(ErrorMessage = "BdsInstanceId is required.")]
[HttpConverter(TargetEnum.Path, "bdsInstanceId")]
public string BdsInstanceId { get; set; }
Property Value
Type | Description |
---|---|
string | The OCID of the cluster. |
Remarks
Required
IfMatch
Declaration
[HttpConverter(TargetEnum.Header, "if-match")]
public string IfMatch { get; set; }
Property Value
Type | Description |
---|---|
string | For optimistic concurrency control. In the PUT or DELETE call
for a resource, set the |
OpcRequestId
Declaration
[HttpConverter(TargetEnum.Header, "opc-request-id")]
public string OpcRequestId { get; set; }
Property Value
Type | Description |
---|---|
string | The client request ID for tracing. |
OpcRetryToken
Declaration
[HttpConverter(TargetEnum.Header, "opc-retry-token")]
public string OpcRetryToken { get; set; }
Property Value
Type | Description |
---|---|
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 might be rejected. |