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}
Uploads an artifact. Provide artifact path, version and content. Avoid entering confidential information when you define the path and version.
For optimistic concurrency control. In the PUT or DELETE call for a resource, set the {@code if-match} parameter to the value of the {@code etag} from a previous GET or POST response for that resource. The resource will be updated or deleted only if the {@code etag} you provide matches the resource's current {@code etag} value. When 'if-match' is provided and its value does not exactly match the 'etag' of the resource on the server, the request fails with the 412 response code.
Unique Oracle-assigned request ID
Example: {@code bxxxxxxx-fxxx-4xxx-9xxx-bxxxxxxxxxxx} If you contact Oracle about a request, provide this request ID.
The OCID of the repository.
Example: {@code ocid1.repository.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
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 PutGenericArtifactContentByPathRequest.