A user-defined path to describe the location of an artifact. Slashes do not create a directory structure, but you can use slashes to organize the repository. An artifact path does not include an artifact version.
Example: {@code project01/my-web-app/artifact-abc}
The OCID of the repository's compartment.
Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags.
Example: {@code {\"Operations\": {\"CostCenter\": \"42\"}}}
The artifact name with the format of {@code
Example: {@code project01/my-web-app/artifact-abc:1.0.0}
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags.
Example: {@code {\"Department\": \"Finance\"}}
The OCID of the artifact.
Example: {@code ocid1.genericartifact.oc1..exampleuniqueID}
The current state of the artifact.
The OCID of the repository.
The SHA256 digest for the artifact. When you upload an artifact to the repository, a SHA256 digest is calculated and added to the artifact properties.
The size of the artifact in bytes. Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
An RFC 3339 timestamp indicating when the repository was created.
A user-defined string to describe the artifact version.
Example: {@code 1.1.0} or {@code 1.2-beta-2}
The metadata of the artifact.