Skip to main content

Auto recognition of terragrunt dependencies

Feature RequestsTerragrunt

As the terragrunt dependencies can be used between stacks, it’d be great that they are recognized automatically, so we don’t need to update them one by one.

Workaround
Manual dependency set
Problem
Status: ❌ Rejected2 comments

Log in to comment and vote

Comments2

  • Jonah Kowall

    Team•

    Jul 12

    Thanks for the idea. Within a single stack, native Terragrunt support with run-all already resolves your Terragrunt dependency graph: https://docs.spacelift.io/vendors/terragrunt/run-all. Automatically inferring cross-stack dependencies from Terragrunt config is a large investment we can’t justify at current demand, so I’m closing this. If you’re splitting Terragrunt across many stacks and manual dependencies are painful at scale, describe the setup and we’ll revisit.

  • Black Breeze

    •

    Jun 10, 2025

    Thanks for this request! We're interested in making Terragrunt dependencies smoother, but we'd love to understand the job you're trying to get done a bit better. **Can you help us understand:** - How many dependencies are you currently managing manually? - What does your current process look like when you need to wire up a new dependency? - When dependencies change in your Terragrunt setup, what breaks or gets tedious? **Most importantly:** If this worked perfectly, what would your ideal workflow look like? Walk us through what you'd want to happen from the moment you add a new `dependency` block in terragrunt.hcl to having it work in Spacelift. The more specific you can be about your current pain and ideal outcome, the better we can design something that actually solves your problem rather than guessing at the implementation.