Wrangling Platforms: Cleaning Up the Mess
summary
Platform cleanup focuses on concrete moves: standardize on one IaC engine like Terraform or OpenTofu, stop building custom CI for IaC and use Tacos solutions or open source (Spacelift, Atlantis, Tofu Controller, Burrito), prefer community modules such as CloudPosi rather than internal rewrites, enforce pick one tool: Terraform or OpenTofu plus naming/tagging via the Terraform null_label pattern, run CI checks for security/format/lint/test/docs, and avoid teriths — example 40,000 resources causing 30–60 minute plans and OOM.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:10Why infrastructure as code matters
- 3:58Too many tools cause chaos
- 6:28Avoid building custom pipelines
- 8:54Don’t reinvent infrastructure modules
- 11:00Treat IaC like real software
- 13:05Naming and tagging superpower
- 15:10CI pipelines for IaC quality
- 17:17Break up giant IaC projects
- 20:04Recap of best practices
- 21:06Closing and Q&A
related talks
45mPlatform Engineering: A Deep Dive Conversation
38mPlatform Engineering in the Age of AI Teammates
41mScaling Infrastructure as Code
32mHow to win at platform engineering
15mThe Art of Platform Engineering
48mMoving from spaghetti infrastructure to composable cloud environments
21mPitfalls of Infrastructure as Code (And how to avoid them!)
39mPlatform Engineering as a (Community) Service