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 Backup and DR.

This page introduces you to using Terraform with Backup and DR, including an
introduction to how Terraform works and some resources to help you get started using
Terraform with Google Cloud. You'll also find links to Terraform reference docs for
Backup and DR, code examples, and guides for using Terraform to provision
Backup and DR resources.

For instructions on how to get started with Terraform for Google Cloud, see
[Install and configure Terraform](https://docs.cloud.google.com/docs/terraform/install-configure-terraform.md.txt) or the
[Terraform for Google Cloud quickstart](https://docs.cloud.google.com/docs/terraform/create-vm-instance.md.txt).

## 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 Backup and DR resources.

The following steps explain how Terraform works:

1. 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.
2. 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.
3. You run the `terraform apply` command, which performs the following
   actions:

   1. It provisions your infrastructure based on your execution plan by invoking the corresponding Backup and DR APIs in the background.
   2. 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.
   3. 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 resources for Backup and DR

*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
Backup and DR:


| Service | Terraform resources | Data sources |
|---|---|---|
| Backup and DR | - [google_backup_dr_backup_plan_association](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/backup_dr_backup_plan_association) - [google_backup_dr_backup_vault](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/backup_dr_backup_vault) - [google_backup_dr_backup_plan](https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/backup_dr_backup_plan) | - [google_backup_dr_backup_plan_association](https://registry.terraform.io/providers/hashicorp/google/latest/docs/data-sources/backup_dr_backup_plan_association) |

<br />

## Terraform-based guides for Backup and DR

The following table lists Terraform-based how-to guides and tutorials for
Backup and DR:


| **Guide** | **Details** |
|---|---|
| [Create and manage a backup vault](https://docs.cloud.google.com/backup-disaster-recovery/docs/cloud-console/backup-vault-create.md.txt) | Explains how to create a backup vault. |
| [Create and manage a backup plan for vaulted resources](https://docs.cloud.google.com/backup-disaster-recovery/docs/cloud-console/backup-plan-create.md.txt) | Explains how to create a backup plan. |
| [Back up Compute Engine instances to a backup vault](https://docs.cloud.google.com/backup-disaster-recovery/docs/cloud-console/backup-vault-create.md.txt) | Explains how to configure a scheduled backup. |

<br />

## Terraform modules and blueprints for Backup and DR

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 modules and blueprints related to
Backup and DR:


| Module or blueprint | Details |
|---|---|
| [backup-dr](https://github.com/GoogleCloudPlatform/terraform-google-backup-dr) | Deploy backup/recovery appliances |

<br />

## What's next

- [Terraform code samples for Backup and DR](https://docs.cloud.google.com/docs/samples.md.txt?language=terraform)
- [Terraform on Google Cloud documentation](https://docs.cloud.google.com/docs/terraform.md.txt)
- [Google Cloud provider documentation in HashiCorp](https://registry.terraform.io/providers/hashicorp/google/latest/docs)
- [Infrastructure as code for Google Cloud](https://docs.cloud.google.com/docs/terraform/iac-overview.md.txt)