Test Driven Delivery of Infrastructure-As-Code
summary
Claims that test-driven delivery of IaC cuts production incidents and shortens release timelines, with demonstrated tests against a Terraform-built VPC/EKS/S3 stack and a Terraform backend (S3 + Dynamo + KMS). Demo runs inspect (Chef) by feeding terraform output JSON to verify DNS, subnets and resources, and runs terratest (Go) to terraform apply then curl the EKS ingress; tests pass for the shown environment. Examples include handling a million-user onboarding event and citing 55% of breaches tied to misconfiguration. modular Terraform modules
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:06Test-driven delivery for infrastructure
- 10:34Benefits over development
- 17:55Test-ready infrastructure code
- 28:59Demo setup and tools
- 35:27Inspect tool: base module
- 41:30Inspect tool: network module
- 43:38Teratest: EKS cluster
- 47:09Infrastructure testing importance
- 49:19Conclusion and resources
- 50:26Q&A
related talks
17mTDD for Infrastructure Code
37mInfraCoding with Terraform: Writing Tests for Infrastructure-as-Code
35mTesting in Infrastructure as Code
36mBuild infrastructure as a code (IaC) using test-later...
47mInfrastructure Testing explained
46mThink of your infrastructure as code
29mEphemeral Cloud Infrastructure for Acceptance Tests with Terraform Enterprise & GitLab
10mInfrastructure as a Code Best Practices with Terraform