Original fetch author here. Glad you like it! A few months after calling it fetch, I regretted that we didn’t call it gethub.

Splitting up states is exactly what it's good for! Check out blog.gruntwork.io/how-to-manag....

Thanks for the feedback. I'm realizing we should create a "developer's guide to Terragrunt" where we can show devs the basics.

We (@gruntwork-io.bsky.social) have worked with 100s of customers and saw many devs succeed with the mental model of "specify module, specify inputs." Thanks again!

Thanks for this helpful feedback! Was there something specific you didn’t like about the end result with Terragrunt?

Any thoughts on what might have lowered the learning curve for other users of your Terragrunt repo?

Mostly, I’m interested in really understanding your experience.

Terragrunt company here. There is a strong case for using Terragrunt with OpenTofu! blog.gruntwork.io/terragrunt-o...

"If true"...ha! Can confirm. Though I realize I need to trick out my BlueSky profile.

That's great feedback on the change detection. Are you specifically looking to say "Which units changed? Now `terragrunt apply` all those units?"

Your assessment is spot on. Terraform/OpenTofu work well for defining reusable infrastructure patterns. Then it’s helpful to have an orchestrator on top of that to control how you deploy those patterns (like Terragrunt).

But to have another orchestrator on top of that doesn’t make much sense.