Hey folks! After years of wrestling with Terraform's state management at scale, we asked ourselves: "What if we could completely reimagine how IaC should work in 2024?" The pain points were clear: • State file locks blocking parallel deployments • Growing state files becoming unwieldy • Teams waiting on each other to apply changes • Accidental resource deletions in large changesets So we built Mantis - bringing task-based workflows to IaC. Think 'make' for infrastructure, with independent state management per task. We've written about why we need this approach and how it works technically: https://getmantis.ai/blog/how_mantis_iac_works If you've hit similar walls with Terraform, would love to hear your thoughts.

How did you identify the pain points?

Hi @Ben 👋- author of the post and creator of Mantis here. We've had several conversations with both devops practitioners and developers to understand the pain points around IaC in general (across Terraform, Helm) and some of these challenges around state management were surfaced. We'd love to hear your thoughts around it.