Terraform Workflow: Write, Plan, Apply
A focused chapter on terraform workflow: write, plan, apply, with practical delivery concerns, trade-offs, and the operational questions behind CI/CD work.
Where Infrastructure Comes From
When a team starts building an application, the first questions are almost always about code: which language to use, how to structure directories, how to
Write Infrastructure as Code Before You Click Another Button
You have an application that needs a server and a database. The usual approach is to log into your cloud provider's dashboard, click through a few pages
Why You Should Always See the Plan Before Running Terraform
You just finished writing a Terraform configuration for a new server and database. The file looks correct. You run terraform apply and wait. A few seconds
When Terraform Apply Actually Runs: What Happens After You Approve the Plan
You have reviewed the plan output. You have confirmed that Terraform will create two EC2 instances, not delete the existing database, and attach the
Why Terraform Needs a State File (And Why You Should Never Store It on Your Laptop)
You just ran terraform apply and successfully created a server and a database. Everything works. You close your laptop, satisfied. Tomorrow, you need to
When Running Terraform from Your Laptop Stops Being Enough
You have been managing infrastructure with Terraform from your terminal. It works fine when you are the only person making changes. You run terraform