Gruntwork Pipelines now natively supports Terragrunt Stacks. Stacks help you manage your infrastructure at scale by logically grouping collections of OpenTofu/Terraform units into versioned entities, keeping your IaC dry and your blast radius small. For a detailed overview, see our announcement blog post.

Now when you push updates involving terragrunt.stack.hcl files in your pull/merge requests, Gruntwork Pipelines automatically evaluates the required changes and orchestrates the necessary infrastructure updates. This process ensures:

‍

1. Small IaC Footprint: Pipelines uses terragrunt stack generate to identify impacted units, so you don't need to check in the generated units—only the terragrunt.stack.hcl files.‍
2. Minimal Blast Radius: Pipelines identifies the minimum set of infrastructure units affected by your changes, avoiding unnecessary operations and limiting risk.‍
3. Complete Management: All relevant infrastructure actions triggered by your terragrunt.stack.hcl updates (create, read, update, destroy) are handled automatically.‍
4. DAG Aware Execution: Updates are applied while respecting the dependency graph (DAG) order so that adds, changes, and destroys all occur successfully.

You can freely mix changes to terragrunt.stack.hcl and terragrunt.hcl files within the same Pull/Merge Request. Pipelines will handle the rest.

This functionality is available now for both GitHub and GitLab. Refer to our docs and the migration guide for more information on how to get started with stacks.