Just as I did with GCP a few weeks ago, I needed to circle back and migrate my state files to a cloud storage bucket. This done mainly to centralize the storage location automatically and thus lower the chance of a state file loss or corruption.
Previously, I’d been separating the state files using the -state parameter. I then use a different input file and state file for each environment like this:
terraform apply -var-file=env1.tfvars -state=env1.tfstate
terraform apply -var-file=env2.tfvars -state=env2.tfstate
terraform apply -var-file=env3.tfvars -state=env3.tfstateTo instead store the state files in an AWS S3 bucket, create a backend.tf file with this content:
terraform {
backend "s3" {
bucket = "my-bucket-name"
workspace_key_prefix = "tf-state"
key = "terraform.tfstate"
region = "us-west-1"
}
}This will use a bucket named ‘my-bucket-name’ in AWS region us-west-1. Each workspace will store its state file in tfstate/<WORKSPACE_NAME>/terraform.tfstate
Note: if workspace_key_prefix is not specified, the directory ‘env:‘ will be created and used.
Since the backend has changed, I have to run this:
terraform init -reconfigureI then have to copy the local state files to the correct location that the workspace will be using. This is easiest done with the AWS CLI tool, which will automatically create the sub-directory if it doesn’t exist.
aws s3 cp env1.tfstate s3://my-bucket-name/tf-state/env1/terraform.tfstate
aws s3 cp env2.tfstate s3://my-bucket-name/tf-state/env2/terraform.tfstate
aws s3 cp env3.tfstate s3://my-bucket-name/tf-state/env3/terraform.tfstateI then create a workspace for each state file:
$ terraform workspace new env1
Created and switched to workspace "env1"!Now I’m ready to run the applies and verify state is matching input
$ terraform apply -var-file=env1.tfvars
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
$ terraform workspace new env2
Created and switched to workspace "env2"!
$ terraform apply -var-file=env2.tfvars
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.Doing it in the opposite order
An alternate way to do this migration is enable workspaces first, then migrate the backend to S3.
$ terraform workspace new env1
Created and switched to workspace "env1"!
$ mv env1.tfstate terraform.tfstate.d/env1/terraform.tfstate
$ terraform apply -var-file=env1.tfvars
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.Then create the backend.tf file and run terraform init -reconfigure. You’ll then be prompted to move the state files to S3:
$ terraform init -reconfigure
Initializing modules...
Initializing the backend...
Do you want to migrate all workspaces to "s3"?
Enter a value: yes
$ terraform apply -var-file=env1.tfvars
No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration and found no differences, so no changes are needed.
Apply complete! Resources: 0 added, 0 changed, 0 destroyed.Either way, the state files have to be individually migrated to the storage bucket
Layer 77 