← 🏗️ Declarative Infrastructure
Advanced
Terraform resource addresses: safe renames, moved blocks and keyed instances
Preserve existing infrastructure when Terraform addresses change. Compare moved blocks with import, reason about count versus for_each and review plans for unintended replacement.
View Premium accesscourse lessons, concepts and answers · see current terms
RELATED CONCEPTS
PRACTICE THIS IN REAL QUESTIONS
Infrastructure as Code & ConfigurationWalk me through terraform init, plan, apply and destroy. What is each one actually doing?→Infrastructure as Code & Configurationcount versus for_each in Terraform: when does list ordering cause a destroy and recreate?→Infrastructure as Code & ConfigurationTwo engineers run terraform apply against the same backend at the same time. What happens?→Infrastructure as Code & ConfigurationOne Terraform module tree, three environments. How do you lay out state so a production apply can never touch anything else?→Infrastructure as Code & ConfigurationName three things in the Terraform state file, and explain why it is a security artifact rather than a cache.→Infrastructure as Code & ConfigurationWhere does Terraform stop and Ansible start? Give me a case where using the wrong one hurts.→