Gruntwork Newsletter, April 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.

This month’s newsletter covers:

• Terragrunt Stacks hits the “feature complete” milestone
• OpenTofu joins the CNCF
• New capabilities in Gruntwork Pipelines
• SageMaker support in Cloud-Nuke
• Gruntwork IaC Library support for EKS up to 1.32!
• And more!

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

Gruntwork Updates

Gruntwork Pipelines now supports Terragrunt Stacks and GitLab Enterprise Self-Hosted

We’ve announced that Terragrunt Stacks is now feature complete with same-day support for Stacks in Gruntwork Pipelines. We’re requesting community feedback to ensure it’s working well in the wild before labeling the feature Generally Available (GA). You can submit feedback in GitHub or in our Discord server.

Gruntwork Pipelines has also released support for GitLab Enterprise (self-hosted).

Gruntwork Pipelines gets performance improvements

Terragrunt has published a documentation page covering configuration options that are widely applicable and improve Terragrunt execution performance. New Gruntwork Pipelines customers will have these options enabled by default, while existing customers can enable them by adding the following values to their Pipelines configuration:

Copy
repository {
  env {
    TG_STRICT_CONTROL = "skip-dependencies-inputs"
    TG_DEPENDENCY_FETCH_OUTPUT_FROM_STATE = true
    TG_PROVIDER_CACHE = 1
  }
}

Copy
env:
  - name: TG_STRICT_CONTROL
    value: skip-dependencies-inputs
  - name: TG_DEPENDENCY_FETCH_OUTPUT_FROM_STATE
    value: true
  - name: TG_PROVIDER_CACHE
    value: 1

Cloud-Nuke now supports SageMaker

A few new resources have been added to cloud-nuke, including SageMaker-related resources, IAM instance profiles, and CloudFront distributions in 0.39.0 and 0.40.0.

Our EKS OpenTofu/Terraform module now supports EKS versions 1.31 and 1.32

The EKS Module Library now supports EKS versions 1.31 and 1.32 with its latest releases. This enables users to take advantage of the newest features and improvements available in these EKS versions.

Behind the scenes, significant development is underway as the EKS collection of modules moves toward a future v1 release. The primary focus of these ongoing updates is to accelerate the delivery of new AWS EKS features to users, while maintaining the stability and reliability that users depend on.

Stay tuned for further announcements as new features and capabilities are introduced, enabling faster adoption of the latest advancements in Amazon EKS through the Library Module.

We're working on a "v2" collection of OpenTofu/Terraform VPC modules

We’re well underway with a rewrite of our VPC modules to take advantage of updated AWS and OpenTofu/Terraform best practices. The new modules will be full replacements for the current modules and, at this time, we believe they will be released as a new major version on terraform-aws-vpc. We will have alpha/beta versions along with migration guides prior to release. You can follow along with development in our vpc-v2 feature branch.

We migrated the Gruntwork blog

We moved the Gruntwork blog from Medium to www.gruntwork.io/blog!

The new home for the Gruntwork blog allows us to supply a much better experience to blog readers, including:

• Improved code styling (including better rendering of code written in HCL)
• More control over how media is rendered.
• The ability to allow users to subscribe for blog content updates.
• The ability to better categorize content for the blog.
• Opens the door to many more enhancements in the future!

We'll also be making another round of design updates to the blog soon.

Announcing the Gruntwork Product Changelog

We ship new features all the time, but we only share this newsletter once each month. We also know it can be hard to keep track with updates spread across multiple tools. That’s why we’re excited to launch our new Product Changelog: a single place to stay up to date with the latest improvements and highlights from Gruntwork.

We’ll keep it short, sweet, and useful. This isn’t a full list of every change, and we won’t use it to market to you—just quick, meaningful updates with links if you want to dive deeper.

Terragrunt Updates

Terragrunt Stacks is now feature-complete

The Stacks experiment in Terragrunt is now feature complete.

To learn more about what this means for Terragrunt Stacks, read the dedicated blog post on it:

https://www.gruntwork.io/blog/the-road-to-1-0-terragrunt-stacks-feature-complete

Make sure to read the end of the post, where you can learn about the stabilization of Terragrunt Stacks, and the process by which we’re making Terragrunt Stacks generally available.

The CLI redesign is now feature-complete

Now that the CLI Redesign is feature-complete, usage of the newest features implemented as part of the Terragrunt CLI Redesign can now be done without usage of the --experiment cli-redesign flag. You can now use commands like the following by default:

• terragrunt backend
• terragrunt exec
• terragrunt run
• terragrunt find
• terragrunt list
• terragrunt dag
• terragrunt hcl
• terragrunt info
• terragrunt render

These commands offer new functionality that rename existing functionality in the Terragrunt CLI, and provide some net-new functionality, as described in the CLI Redesign RFC (#3445). Stay tuned for a future blog post, when we’ll do a breakdown of how the CLI has evolved, and announce the start of legacy CLI command removal.

Devops News

OpenTofu joins the CNCF

The Cloud Native Computing Foundation (CNCF) has voted to approve an exception to their license rule and accept OpenTofu as a CNCF Project! CNCF rules specify that all projects must be Apache licensed. OpenTofu cannot easily switch to Apache, however, due to the nature of the project as a MLv2 fork and without a Contributor License Agreement (CLA) - switching is a practical impossibility. The CNCF debated and ultimately accepted these circumstances and so begins the process bringing OpenTofu under the CNCF Umbrella.

Being a part of the CNCF provides even more of a guarantee that OpenTofu remains a vendor neutral, free and open source, forever.