← 🏗️ Declarative Infrastructure
Core
Terraform import: adopting existing infrastructure without accidental changes
Adopt existing resources into Terraform by establishing ownership, matching configuration and reviewing the import plan. Separate association with state from a safe no-change adoption.
a free account opens the core tier · no card
RELATED CONCEPTS
PRACTICE THIS IN REAL QUESTIONS
Infrastructure as Code & ConfigurationFive hundred resources were built by hand over three years and must come under Terraform. Walk me through importing them without breakage.→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 & ConfigurationName three things in the Terraform state file, and explain why it is a security artifact rather than a cache.→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?→