Managing DevOps Artifacts
DevOps artifacts are referenced in a pipeline stage for automated deployment to the target environment. They are used to specify software package versions for deployment.
Each service in Oracle Cloud Infrastructure (OCI) integrates with Identity and Access Management (IAM) for authentication and authorization, for all interfaces (the Console, SDK and CLI, and REST API). Before you begin using the DevOps service, you must create policies to control who has access to DevOps, and the type of access for each group of users.
DevOps artifacts can be a container image, a generic artifact, helm chart, or they can be defined inline. The artifact source varies depending on the type of artifact. In DevOps, you can create references to the following types of artifacts.
- Container image repository: Refers to the Oracle Cloud Infrastructure (OCI) Container Registry repository in which Docker images are stored. See Adding a Container Image Repository Artifact.
- Instance group deployment configuration: Refers to the YAML formatted file that is used to manage instance group deployment. The file defines the artifacts to be downloaded to the instance and the location where the artifacts must be copied. For more information, see Deployment Configuration File.
- Kubernetes manifest: Refers to the Artifact Registry path, or is defined inline. See Adding an Artifact in Artifact Registry and Adding an Inline Artifact.
- General artifact: Refers to any generic software packages to be deployed. See Adding an Artifact in Artifact Registry and Adding an Inline Artifact.
- Helm Chart: Refers to the Helm charts that are stored in the OCI Container Registry repository. See Adding a Helm Chart.
- Command specification: Refers to a set of custom commands and steps that are run in a deployment pipeline. For more information, see Command Specification.