Version Control for Infrastructure Code
What you'll learn: Why storing your Infrastructure as Code in version control systems like Git is essential for safe, collaborative infrastructure management.
Why Put Infrastructure in Git?
Just as developers use Git to track code changes, infrastructure engineers store IaC files (Terraform .tf files, CloudFormation templates, etc.) in version control. Your infrastructure configuration is code—and treating it like code means preserving every change, understanding who made it, and being able to roll back when something breaks.
Without version control, you're flying blind: Was this server config updated yesterday or last month? Who changed the security group? Why did we remove that resource? Version control answers all of these questions.
How It Works
You store your IaC configuration files in a Git repository. Each commit captures:
- What changed (added, modified, or deleted resources)
- Who changed it (author and committer)
- When it changed (timestamp)
- Why it changed (commit message)
When you need to deploy infrastructure, you pull the latest code, run your IaC tool's plan/preview command to verify changes, then apply. If something goes wrong, you can revert to a previous commit—instantly recovering a known-good configuration.
Collaboration and Code Review
Multiple team members can work on infrastructure simultaneously using branches. Before merging changes to the main branch, peers review the proposed modifications—catching mistakes before they reach production. Pull requests become your safety net, ensuring no one accidentally deletes a database or opens port 22 to the internet.
Version control also integrates seamlessly with CI/CD pipelines (as you learned in the previous lesson), automating testing and deployment workflows.
Key Takeaway: Store all IaC files in Git to track changes, enable collaboration through code review, and maintain a complete history for auditing and rollback—turning infrastructure management into a safe, reproducible process.