Core

Terraform workspaces: state separation and environment isolation

Choose Terraform environment boundaries deliberately. Compare CLI workspaces with separate roots and backends, then trace the credentials and state used by a plan.

a free account opens the core tier · no card

RELATED CONCEPTS

Terraform State Locking Terraform Architecture Terraform Provider Upgrades

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 & 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?→Infrastructure as Code & ConfigurationPick and defend a remote state backend for a 40-engineer platform. Compare the realistic options.→