Gruntwork Newsletter, May 2025

Every few months, we send out a newsletter to all Gruntwork customers that describes all the updates we’ve made since the last newsletter and news from the DevOps industry. Note that some of the links below may go to private repositories in the Gruntwork Infrastructure as Code Library that are only accessible to customers.

As always, if you have any questions or need help, email us at support@gruntwork.io!

Gruntwork Updates

Gruntwork Library 1.0 Progress: EKS, ECS, Security and More

As announced in our March newsletter, we’ve been making steady progress maturing the IaC Library to 1.0 status. May was a big month for graduations, including:

• terraform-aws-ecs
• terraform-aws-server
• terraform-aws-monitoring
• terraform-aws-asg
• terraform-aws-security
• terraform-aws-cache
• terraform-aws-load-balancer
• terraform-aws-static-assets
• terraform-aws-eks

We’re actively working on a ground-up rewrite of terraform-aws-vpc and expect to tag a 1.0.0 once that is complete. Similarly a project is underway to update terraform-aws-eks which would be launched as 2.0.0.

Gruntwork Pipelines - Ignore List & Experimental Features

With Pipelines v3.9.0 (GitHub) and v1.5.0 (GitLab) we’ve launched two sets of features - The ignore list and experimental flags to customize Terragrunt job generation.

Ignore List

The ignore list allows users to define a list of patterns that match to files and folders in your repository that will cause pipelines to drop any jobs it would have otherwise generated from those locations. This is handy in several circumstances, common ones include avoiding generating jobs in documentation folders and for ignoring folders of infrastructure that are managed outside of Pipelines.

Experimental Flags

In response to both the launch of Terragrunt Stacks and customer feedback, we’ve added three new flags to govern how jobs are produced by Pipelines. We believe the behavior enabled when these flags are enabled is what most teams would prefer in their pipeline, however it does represent a change in how pipelines works. As a result, we’ve launched these changes behind feature flags to enable teams to opt in to the new behavior. Our aim is to enable these features by default with our next major breaking change, subject to further customer feedback.

Terragrunt Updates

Terragrunt v1 Docs Site Beta

We’re in the process of updating Terragrunt’s docs to be more modern, elegant and intuitive for users. To that end, we have a public beta of the next iteration of our docs we’re calling “Terragrunt V1 Docs” available here. The intention is to iterate on this site, incorporate feedback and eventually have it replace the existing Terragrunt website.

The current (old) website is a Jekyll site which has served us well for many years. The new v1 website is built with Starlight. The new platform allows us to have a high quality single-source-of-truth for many of the details of documentation, including CLI commands, flags and arguments, ensuring 100% consistency between the product and the docs. It also allows for dynamic data fetching/caching, so we can have, for example, up to date version references throughout the site with minimal maintenance. Also, we think it’s a significant look and feel update that we hope users will find pleasant, and improves the experience of learning Terragrunt.

Migration to GitHub Actions

In an effort to make Terragrunt easier to contribute to, the continuous integration for Terragrunt is moving to GitHub Actions from CircleCI.

Our test suite has already fully migrated over to GitHub Actions, meaning that contributors can now simply fork the repository, then allow GitHub Actions to run on forks (it’s off by default for security reasons) to run the Terragrunt test suite on their own without signing up for any additional services. We hope this will make the project more accessible for new developers.

The remaining effort for the migration to GitHub Actions is the update of the release process, which may be complete by the time you read this!

Version 0.79.x and 0.80.x

The v0.79.x line of releases introduced several new features, including:

• run --all automatically generates Terragrunt Stacks.
• stack clean now recursively deletes all generated stack directories.
• The catalog configuration block now supports all go-getter formatted URLs. The restriction on supported platforms (GitHub, GitLab, BitBucket, etc.) has been lifted, opting to gracefully degrade additional capabilities instead of preventing usage on additional platforms (you can use catalog if you’re using a niche Git provider, but you just won’t get the “View Source in Browser” button).
• Memoization of OpenTofu/Terraform -version calls by Terragrunt. In a micro benchmark, these changes have led to an 18% speed improvement and a 9% memory reduction.

Versions in the v0.80.x line so far include:

• Terraform 1.12 support.
• Updating the Terragrunt build toolchain to Go 1.24.
• terragrunt find now supports an --include flag for displaying include configuration block details when discovering units.
• Significant performance improvements for run --all. In a micro benchmark, these changes have led to a 42% speed improvement and a 43% memory reduction.
• terragrunt exec now supports the --tf-path argument. Thanks to @erpel to this contribution!