Untangling Infrastructure Code...
summary
Shows how to refactor an actual terraform config that builds a Chef server plus Supermarket test cluster on AWS, using Test Kitchen, kitchen terraform and InSpec to cover changes with tests first. Demonstrates reducing two AWS security groups to one security group, moving group code into a reusable Terraform module, and running kitchen converge / kitchen verify to prove the change and keep functionality. The claim is concrete, the tools are named, a surprising limit (500 SGs) motivates the work, and the refactor succeeds.
AI-written summary · about
chapters (4)
- 0:00Start
- 1:43Refactoring a Terraform config
- 7:33Confidence in code without tests is false confidence
- 27:30When refactoring always cover with tests
related talks
32mChef Tools & Terraform: Better Together
52mTest Driven Delivery of Infrastructure-As-Code
37mInfraCoding with Terraform: Writing Tests for Infrastructure-as-Code
10mInfrastructure as a Code Best Practices with Terraform
44mTaming the cloud sprawl
46mThink of your infrastructure as code
35mMisadventures with Terraform
29mBreaking Down the TofuLith. How We Reduced Lead Times for Multi-Tenant Infra Changes...