Terraform state mv for refactoring - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the terraform state mv command?

It moves resources in the Terraform state file from one address to another without changing the actual infrastructure. This helps when refactoring or renaming resources.

beginner

When should you use terraform state mv?

Use it when you rename or reorganize resources in your Terraform code but want to keep the existing infrastructure intact and avoid recreating resources.

intermediate

What happens if you rename a resource in code but don't update the state with terraform state mv?

Terraform will think the old resource was deleted and a new one needs to be created, which can cause downtime or data loss.

beginner

How do you move a resource named aws_instance.old_name to aws_instance.new_name in Terraform state?

Run terraform state mv aws_instance.old_name aws_instance.new_name to update the state file accordingly.

advanced

Can terraform state mv move resources between different Terraform workspaces or backends?

No, it only moves resources within the same state file. Moving between workspaces or backends requires different approaches like state pull and push.

What does terraform state mv do?

A Deletes resources from the cloud provider

B Updates Terraform version

C Creates new resources in the cloud

D Moves resources in the state file without changing infrastructure

The command moves resource references inside the state file to reflect code changes without affecting actual infrastructure.

Why use terraform state mv after renaming a resource in code?

A To avoid Terraform recreating the resource

B To delete the old resource

C To upgrade Terraform

D To backup the state file

Moving the resource in state tells Terraform the resource is the same, preventing unnecessary recreation.

Which command moves aws_s3_bucket.old to aws_s3_bucket.new in state?

A terraform mv aws_s3_bucket.old aws_s3_bucket.new

B terraform state mv aws_s3_bucket.old aws_s3_bucket.new

C terraform state rename aws_s3_bucket.old aws_s3_bucket.new

D terraform move aws_s3_bucket.old aws_s3_bucket.new

The correct syntax is terraform state mv followed by old and new resource addresses.

Can terraform state mv move resources between different backends?

A Yes, but only for S3 backends

B Yes, automatically

C No, it only works within the same state file

D Only if you use the -backend flag

State moves only happen inside the same state file; moving between backends requires manual export/import.

What risk exists if you rename a resource in code but don't run terraform state mv?

A Terraform will destroy and recreate the resource

B Terraform will ignore the resource

C Terraform will crash

D Terraform will merge the resources

Terraform treats the renamed resource as new and the old as deleted, causing destruction and recreation.

Explain how and why you would use terraform state mv during a resource refactoring.

Think about what happens if you rename a resource but don't update the state.

Describe the limitations of terraform state mv and when it cannot be used.

Consider different Terraform environments and storage backends.