🐢 Why is terraform plan Taking 20 Minutes? — Optimizing Terraform at Scale
Failed to add items
Add to cart failed.
Add to wishlist failed.
Remove from wishlist failed.
Follow podcast failed
Unfollow podcast failed
-
Narrated by:
-
Written by:
Is your development workflow grinding to a halt? In this performance-focused episode, Nat and Leo tackle the "Traffic Jam" of Terraform at scale. Nat plays an engineer who just joined a team where terraform plan takes long enough to grab a full lunch, while Leo acts as the performance profiler, breaking down exactly where those minutes are going. We explore the cost of the refresh step, the risks of -target, and why a monolithic state file is the ultimate bottleneck for high-velocity teams.
In this Deep Dive:
The Traffic Jam Metaphor: Why slow plans aren't caused by one "bad" resource, but by the accumulation of a thousand tiny API calls.
The Refresh Tax: Understanding the math behind 1,000 resources vs. Cloud Provider rate limits.
Surgical Precision: The -target flag—when it’s a lifesaver and why it’s a dangerous shortcut for your state's consistency.
Parallelism & Caching: Tuning the -parallelism engine and using provider mirrors to slash CI/CD init times.
The Monolith Breakup: Identifying the three "Red Flags" that tell you it’s time to split your state file into smaller, faster layers.
Terragrunt run-all: How to execute across multiple configurations without losing track of your dependency graph.
🚀 Speed up your feedback loop.Infrastructure as Code shouldn't feel like a waiting game. Learn the advanced profiling techniques and architectural patterns used by the world's fastest DevOps teams at:👉 https://certquests.com/