Enabling Developer Autonomy through IaC and Policy-as-Code: A Case Study
summary
TV4 and MTV standardize on OpenTofu and CDK for Terraform to give 60+ developers safe self-service: ~300 OpenTofu projects, ~1,400 workspaces, 18 teams, ~80 active users supported by a five‑person cloud team. CDKTF (TypeScript stacks) speeds onboarding, provides object‑oriented modules and strong typing that catches errors earlier, but has 352 MB bindings per install and sparse updates since Jan 2024. Open Policy Agent runs plan-time checks as policy-as-code, emitting warnings that developers fix pre‑apply and dramatically reduce support load.
AI-written summary · about
chapters (13)
- 0:00Developer autonomy with IaC
- 1:03TV4 and MTV3
- 2:27Scaling infrastructure ownership
- 4:56Reducing infrastructure code complexity
- 8:47CDKTF for developers
- 13:20CDKTF libraries
- 17:56CDKTF pros and cons
- 21:07CDKTF adoption best practices
- 22:11OPA for good infrastructure code
- 24:22OPA feedback loops
- 26:49OPA challenges and future
- 27:32Next steps and takeaways
- 28:20Q&A
related talks
26mEnabling OpenTofu for the Enterprise
32mNavigating the OpenTofu Landscape: From Basics to Mastery
42mWhen, Why, and How to Use the CDK for Terraform
30mTaste Testing Tofu
29mThe Path to Modern Infrastructure Automation: Revisited
30mOpenTofu Project Overview
10mLightning Talk: 800 Reasons To Love OpenTofu (We Counted Them All)
32mNavigating the OpenTofu Landscape From Basics to Mastery