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 resource's current etag value.
The maximum number of items to return in a paginated "List" call.
Unique identifier for the request. If provided, the returned request ID will include this value. Otherwise, a random request ID will be generated by the service.
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).
The value of the {@code opc-next-page} response header from the previous "List" call.
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
The field to sort by. You can specify only one sort order. The default order for {@code TIMECREATED} is descending. The default order for {@code DISPLAYNAME} is ascending.
The sort order to use, either ascending ({@code ASC}) or descending ({@code DESC}).
The OCID of the vault.
Click here to see how to use ListVaultReplicasRequest.