terraform-backend-gcs

A Terraform plan for building a state locking backend in Google Cloud Storage

Background

By default, Terraform stores state information about the infrastructure it manages in a local file named terraform.tfstate. Any modifications to infrastructure definitions will reference this state information and update it once the required changes have been implemented. However, local state management is not suitable for team collaboration. Each team member would need a current copy of the state file. Even then, they would need to ensure that only one team member at a time can make changes to the infrastructure in order to avoid conflicting changes.

Fortunately, Terraform supports remote state management using a number of different backend solutions in which to centrally store state information. Many of these backends also support state locking to ensure that only one team member at a time can make changes to the infrastructure.

Implementation

The Terraform plan contained in this repository will create a backend in Google Cloud Storage for state file storage and locking operations. This backend can be creating using the following steps:

Clone the repository to your local machine.

$ git clone https://github.com/stealthllama/terraform-backend-gcs.git

Change into the repository directory.

$ cd terraform-backend-gcs

Create a terraform.tfvars file containing the variables defined in variables.tf and their values.

gcp_project_id = "terraform-test-243715"
gcp_region = "us-central1"
gcp_credential =<<EOF
{CREDENTIAL_FILE_CONTENTS_HERE}
EOF

Initialize the Terraform provider.

$ terraform init

Validate the Terraform plan.

$ terraform plan

Implement the Terraform plan.

$ terraform apply

The Terraform plan will output the name of the GCP storage bucket used for state storage and locking. These values will be referenced in other Terraform plans that utilize this backend.

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Outputs:

bucket = tfstate-bucket-3a12db2b

Usage

Once the backend has been created it can be used by another Terraform plan. However, it is recommended that you create a separate backend for each Terraform project in order to ensure state files in the backend are not overwritten.

To use this backend in a Terraform plan you will define a backend configuration such as the following either in an existing Terraform plan file or in a separate backend.tf file within the project directory:

terraform {
  backend "gcs" {
    bucket          = "tfstate-bucket-3a12db2b"
    prefix          = "/terraform.tfstate"
    credentials     = <<EOF
{CREDENTIAL_FILE_CONTENTS_HERE}
EOF
  }
}

Once included in a Terraform plan the backend will need to be initialized with the remainder of the plan. The output of the terraform init command should include the following output:

Initializing the backend...

Successfully configured the backend "gcs"! Terraform will automatically
use this backend unless the backend configuration changes.

From this point forward any Terraform commands issued within the project directory will reference the state information contained in the backend storage. All commands will also acquire a state lock in order to ensure the requestor has exclusive access to the state information. The lock will then be released once the command actions have completed.

Happy Terraforming!

ceskillets/Automation-Terraform-Backend-for-GCP

terraform-backend-gcs

Background

Implementation

Usage