Refactoring Terraform: Moving Resources Without Destroying Them

This article provides a practical guide for refactoring Terraform codebases, specifically focusing on moving resources without causing destruction in production. It explains the challenges of renaming resources in Terraform, where changes can appear as destroy-and-create actions. The author introduces the moved block (Terraform 1.1+) as a safe method to rename resources while keeping state in sync, using Azure storage accounts as an example. The article also hints at covering the removed block and terraform state CLI for restructuring code into modules. It targets DevOps engineers and platform teams managing Terraform at scale, emphasizing safety and best practices.