HashiCorp Terraform is an infrastructure-as-code (IaC) tool that lets you provision and manage cloud infrastructure. Terraform provides plugins called providers that let you interact with cloud providers and other APIs. You can use the Terraform provider for Google Cloud to provision and manage Google Cloud resources, including Artifact Registry.
How Terraform works
Terraform has a declarative and configuration-oriented syntax, which you can use to describe the infrastructure that you want to provision in your Google Cloud project. After you author this configuration in one or more Terraform configuration files, you can use the Terraform CLI to apply this configuration to your Artifact Registry resources.
The following steps explain how Terraform works:
- You describe the infrastructure you want to provision in a Terraform configuration file. You don't need to write code describing how to provision the infrastructure. Terraform provisions the infrastructure for you.
- You run the
terraform plan
command, which evaluates your configuration and generates an execution plan. You can review the plan and make changes as needed. -
You run the
terraform apply
command, which performs the following actions:- It provisions your infrastructure based on your execution plan by invoking the corresponding Artifact Registry APIs in the background.
- It creates a Terraform state file, which is a JSON file that maps the resources in your configuration file to the resources in the real-world infrastructure. Terraform uses this file to keep a record of the most recent state of your infrastructure, and to determine when to create, update, and destroy resources.
-
When you run
terraform apply
, Terraform uses the mapping in the state file to compare the existing infrastructure to the code, and make updates as necessary:- If a resource object is defined in the configuration file, but doesn't exist in the state file, Terraform creates it.
- If a resource object exists in the state file, but has a different configuration from your configuration file, Terraform updates the resource to match your configuration file.
- If a resource object in the state file matches your configuration file, Terraform leaves the resource unchanged.
Terraform-based guides for Artifact Registry
The following table lists all Terraform-based how-to guides and tutorials for Artifact Registry:
Guide | Details |
---|---|
Create a standard repository using Terraform | This guide describes how to create a standard mode repository with Terraform. |
Create a remote repository using Terraform | This guide describes how to create a remote mode repository with Terraform. |
Create a virtual mode repository using Terraform | This guide describes how to create a virtual mode repository with Terraform. |
Terraform modules and blueprints for Artifact Registry
Modules and blueprints help you automate provisioning and managing of Google Cloud resources at scale. A module is a reusable set of Terraform configuration files that creates a logical abstraction of Terraform resources. A blueprint is a package of deployable and reusable modules, and a policy that implements and documents a specific solution.
The following table lists all modules and blueprints related to Artifact Registry:
Module or blueprint | Details |
---|---|
artifact-registry | Create and manage Artifact Registry repositories |
secure-cicd | Builds a secure CI/CD pipeline on Google Cloud |
gcloud | Executes Google Cloud CLI commands within Terraform |
Terraform resources for Artifact Registry
Resources are the fundamental elements in the Terraform language. Each resource block describes one or more infrastructure objects, such as virtual networks or compute instances.
The following table lists the Terraform resources available for Artifact Registry:
Service | Terraform resources | Data sources |
---|---|---|
Artifact Registry |
|
What's next
- Terraform code samples for Artifact Registry
- Terraform on Google Cloud documentation
- Google Cloud provider documentation in HashiCorp
- Infrastructure as code for Google Cloud