A user-defined path to describe the location of an artifact. You can use slashes to organize the repository, but slashes do not create a directory structure. An artifact path does not include an artifact version.
Example: {@code project01/my-web-app/artifact-abc}
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 identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID.
The OCID of the repository.
Example: {@code ocid1.artifactrepository.oc1..exampleuniqueID}
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
Updates an artifact with a specified {@code artifactPath} and {@code version}. You can only update the tags of an artifact.
A user-defined string to describe the artifact version.
Example: {@code 1.1.2} or {@code 1.2-beta-2}
Click here to see how to use UpdateGenericArtifactByPathRequest.