Lightning Talk: Staying in Sync: Managing Upgrades in OpenTofu and Terraform Modul...
summary
Practical guidance for upgrading OpenTofu and keeping Terraform modules reproducible, with concrete rules: pin versions to MAJOR.MINOR.PATCH in versions.tf, prefer semantic versioning for modules so consumers never get breaking changes unexpectedly, and use automation to catch problems before apply. The demo shows state migration when running openTofu init and openTofu apply, recommends tools like terraform-provider-migrate and CI bots, and includes a GitHub repo with a deliberately failing Action to practice fixes.
AI-written summary · about
chapters (8)
- 0:00Versioning in IaC
- 1:51Why upgrades break
- 2:55Pin all versions
- 4:01Version constraints explained
- 5:25Modules as APIs
- 6:29Automating upgrades
- 8:56Key takeaways
- 10:04Q&A
related talks
15mLightning Talk: Seamless at Scale: Migrating from Terraform to OpenTofu Without Mis...
32mNavigating the OpenTofu Landscape: From Basics to Mastery
32mNavigating the OpenTofu Landscape From Basics to Mastery
30mTaste Testing Tofu
23mBuild Your Tofu Toolbox: A Tour of Battle-Tested Tools for IaC at Sca...
11mLightning Talk: Migrating a Client onto OpenTofu for Cost + Speed
05mEnabling Product Thinking for Terraform Modules with OpenTelemetry (and OpenTofu)
14mLightning Talk: 5 Security Tips for Terraform