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.
Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, provide the request ID.
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 earlier 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.
Unique repository identifier.
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
If fetch and merge is passed in, the changes from the upstream will be fetched and merged into the destination branch. If discard is passed in, the changes in the fork will be overwritten with the changes brought in from the upstream.
Details required for syncing a repository with its upstream.
Click here to see how to use SyncRepositoryRequest.