Mode for artifact parameter substitution.
The OCID of a compartment.
Defined tags for this resource. Each key is predefined and scoped to a namespace. See Resource Tags. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Type of the deployment artifact.
Optional description about the artifact to be deployed.
Deployment artifact identifier, which can be renamed and is not necessarily unique. Avoid entering confidential information.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. See Resource Tags. Example: {@code {"bar-key": "value"}}
Unique identifier that is immutable on creation.
A detailed message describing the current state. For example, can be used to provide actionable information for a resource in Failed state.
Current state of the deployment artifact.
The OCID of a project.
Usage of system tag keys. These predefined keys are scoped to namespaces. See Resource Tags. Example: {@code {"orcl-cloud": {"free-tier-retained": "true"}}}
Time the deployment artifact was created. Format defined by RFC3339.
Time the deployment artifact was updated. Format defined by RFC3339.
Artifacts are deployment manifests that are referenced in a pipeline stage for automated deployment to the target environment. DevOps artifacts can be an OCI Container image repository, Kubernetes manifest, an Artifact Registry artifact, or defined inline.