terraform-refactoring

To rename Terraform resources without destroying infrastructure, introduce moved blocks to your configuration. This mechanism updates the state address mapping so terraform plan recognizes the changes as non-destructive moves rather than resource replacements.

A Terraform moved block is a configuration construct used to migrate state addresses safely. Use it when refactoring module structure, renaming resources, or adjusting addresses to ensure state migrations occur without impacting existing infrastructure.

Converting Terraform count to for_each without recreating resources requires using moved blocks to remap old index-based addresses to new key-based addresses. This updates the state directly, preserving existing infrastructure during the module refactor.

Using moved blocks for module refactoring requires Terraform v1.1 or higher. This version introduced the moved block mechanism, which enables state migrations and non-destructive address changes across single or multi-module configurations.

Yes, you can split a large Terraform module into smaller pieces while preserving state by applying moved blocks. This refactoring pattern safely migrates resources to new module paths without triggering destructive changes during terraform plan.

Terraform plan shows destructive changes after renaming a resource address when moved blocks are missing from the configuration. Adding moved blocks explicitly tells Terraform to migrate the state safely, changing the output from resource destruction to address moves.