Build infrastructure as a code (IaC) using test-later...
summary
Advocates building IaC first, then adding tests (TLD) and shows concrete tooling and failures: uses terraform validate and fmt for unit checks, adds variable validations and lifecycle pre/post conditions as contract tests to catch bad CIDR masks and missing default routes, and runs Terratest (Go) integration tests that init/apply/destroy module-only stacks. Full end-to-end SSH check applies the whole Oracle Cloud setup (two VCNs, public+private subnets, DRG, three VMs), reproduces plan-success/apply-fail issues, fixes them with validations, and then destroys the environment.
AI-written summary · about
chapters (4)
related talks
17mTDD for Infrastructure Code
52mTest Driven Delivery of Infrastructure-As-Code
37mInfraCoding with Terraform: Writing Tests for Infrastructure-as-Code
47mInfrastructure Testing explained
32mWe Still Need to Talk About Infrastructure Testing
35mTesting in Infrastructure as Code
46mInfrastructure testing - it's a real thing!
28mFrom Monitoring to Automated Testing of Your Infrastructure Code