Skip to main content

Gruntwork release 2025-10

Guides / Update Guides / Releases / 2025-10

This page is lists all the updates to the Gruntwork Infrastructure as Code Library that were released in 2025-10. For instructions on how to use these updates in your code, check out the updating documentation.

Here are the repos that were updated:

boilerplate​

v0.10.1​

Published: 10/2/2025 | Release notes

Added GitHub Actions workflows to start the migration of this project to GitHub Actions from CircleCI.

Added linting configurations to match what Terragrunt uses, and that also involved cleaning up some tests, and some small refactors throughout the codebase.

Full Changelog: https://github.com/gruntwork-io/boilerplate/compare/v0.10.0...v0.10.1

pipelines-actions​

v4.1.1​

Published: 10/27/2025 | Release notes

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v4.1.0...v4.1.1

v4.1.0​

Published: 10/22/2025 | Release notes

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v4.0.0...v4.1.0

v4.0.0​

Published: 10/8/2025 | Release notes

Full Changelog: https://github.com/gruntwork-io/pipelines-actions/compare/v3.6.4...v4.0.0

pipelines-cli​

v0.40.3​

Published: 10/30/2025 | Release notes

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.40.2...v0.40.3

v0.40.2​

Published: 10/23/2025 | Release notes

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.40.1...v0.40.2

v0.40.1​

Published: 10/21/2025 | Release notes

Pipelines will now always use --queue-include-units-reading instead of --units-that-include.

Previously, Pipelines would only use the former flag for FileChanged events for the sake of providing greater backwards compatibility, but the minimum supported version of Terragrunt in Pipelines now supports --units-that-include, and this is no longer necessary.

By making this change, Pipelines now behaves more in-line with customer expectations, as customers expect that a file with an .hcl extension read via an HCL function like read_terragrunt_config() should still result in inclusion into the run queue.

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.40.0...v0.40.1

v0.40.0​

Published: 10/8/2025 | Release notes

Full Changelog: https://github.com/gruntwork-io/pipelines/compare/v0.39.0...v0.40.0

pipelines-workflows​

v4.0.2​

Published: 10/30/2025 | Release notes

  • Fixed unknown event type when repository_dispatch is used
  • Reduced log noise during authentication

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v4...v4.0.2

v4.0.1​

Published: 10/27/2025 | Release notes

v4.0.0​

Published: 10/23/2025 | Release notes

Pipelines v4 is nearly a full rewrite of the pipelines implementation within GitHub. Prior to v4 the bulk of the "glue" logic to stitch together various components of the workflow was written in bash. In v4 we've replaced the majority of the bash code with golang code which is both faster, more maintainable and has significantly improved test coverage. v4 also includes a handful of new features:

Pipelines v3 has maximum Terragrunt version of 0.84. Pipelines v4 removes this restriction and will support all Terragrunt versions from 0.86.3 through to 1.0+.

As of this release we are promoting HCL to the default configuration language for Pipelines. This release includes additions to the pipelines HCL configuration specification that bring it up to full feature parity with YML, and we intend to build forwards using only HCL. As a result, the YML configuration for Pipelines is now deprecated and will be removed in a future release.

Pipelines will now request a custom log format from Terragrunt (via TG_LOG_CUSTOM_FORMAT) and then parse the resulting output into different streams, and present each Unit's output independently and deinterlaced in the pipelines comment engine.

Pipelines v4 includes support for Azure OIDC and state storage. New configuration options are now available in HCL configuration for Azure.

Pipelines v4 includes a rewrite of several components of the commenting engine which should result in less time spent calculating and posting PR comments.

Pipelines v4 includes a more expressive syntax for filters when triggering drift detection.

The following feature flags are now all enabled by default:

  • PIPELINES_FEATURE_EXPERIMENT_AGGRESSIVE_CONSOLIDATION
  • PIPELINES_FEATURE_EXPERIMENT_COLOCATED_FILE_UNIT_CHANGE_DETECTION
  • PIPELINES_FEATURE_EXPERIMENT_MINIMIZE_BLAST_RADIUS

Pipelines will now always use --queue-include-units-reading instead of --units-that-include.

Previously, Pipelines would only use the former flag for FileChanged events for the sake of providing greater backwards compatibility, but the minimum supported version of Terragrunt in Pipelines now supports --units-that-include, and this is no longer necessary.

By making this change, Pipelines now behaves more in-line with customer expectations, as customers expect that a file with an .hcl extension read via an HCL function like read_terragrunt_config() should still result in inclusion into the run queue.

Pipelines v4 now refers to leaf folders with a terragrunt.hcl file as units. Prior versions used the term module. This change aligns Pipelines' terminology with Terragrunt's.

Please see a full migration guide at https://docs.gruntwork.io/2.0/docs/pipelines/previous-versions/upgrading-github-v3-to-v4

Full Changelog: https://github.com/gruntwork-io/pipelines-workflows/compare/v3.9.0...v4.0.0

terraform-aws-architecture-catalog​

v4.0.1​

Published: 10/10/2025 | Release notes

v4.0.0​

Published: 10/8/2025 | Release notes

Updated devops-foundations-infrastructure-live-root, devops-foundations-infrastructure-live-access-control, devops-foundations-infrastructure-live-delegated, devops-foundations-infrastructure-modules & single-account-baseline templates to support usage in GitLab environments. Supporting components have been moved into blueprints folder for a single source of truth.

Templates now uses the following new variables

  • SCMProvider: to specify the platform. Options: "GitLab" or "GitHub"
  • SCMProviderGroup: replaces "GithubOrg"
  • SCMProviderRepo: replaces "InfraLiveRepoName"

Full Changelog: https://github.com/gruntwork-io/terraform-aws-architecture-catalog/compare/v3.1.1...v4.0.0

terraform-aws-data-storage​

v0.41.1​

Published: 10/2/2025 | Modules affected: rds, aurora | Release notes

  • docs: Add PostgreSQL major version upgrade documentation
  • fix: Create an implicit dependency on the RDS resource
  • feat(aurora): Add database_insights_mode option to aurora module

terraform-aws-ecs​

v1.2.0​

Published: 10/2/2025 | Modules affected: ecs-task-definition, ecs-task-scheduler | Release notes

  • ecs-task-definition: New module that deploys an ECS Task Definition stand-alone (without a service)
  • ecs-task-scheduler: Fix a bug where the var ecs_target_network_configuration did not have a type definition

terraform-aws-eks​

v3.1.1​

Published: 10/14/2025 | Modules affected: eks-k8s-karpenter | Release notes

  • Expose resources configuration on Karpenter Helm Chart values.

v2.1.1​

Published: 10/6/2025 | Modules affected: eks-k8s-external-dns | Release notes

  • Add Support for Bitnami external-dns image repository (bitnami -> bitnamilegacy). Default image repository is now set as bitnamilegacy/external-dns.

v1.5.1​

Published: 10/6/2025 | Modules affected: eks-k8s-external-dns | Release notes

  • Add Support for Bitnami external-dns image repository (bitnami -> bitnamilegacy). Default image repository is now set as bitnamilegacy/external-dns.

v3.1.0​

Published: 10/1/2025 | Modules affected: eks-k8s-external-dns | Release notes

  • Add Support for Bitnami external-dns image repository (bitnami -> bitnamilegacy). Default image repository is now set as bitnamilegacy/external-dns.

terraform-aws-monitoring​

v1.2.0​

Published: 10/24/2025 | Modules affected: alarms | Release notes

  • alarms/sns-to-slack: new option var.enable_advanced_formatting to enable CloudWatchNotification formatting for sns-to-slack

v1.1.0​

Published: 10/3/2025 | Modules affected: alarms | Release notes

  • alarms/asg-disk-alarms: Fixed ASG disk alarm showing 'Insufficient Data' due to dimensions mismatch

terraform-aws-security​

v1.1.0​

Published: 10/10/2025 | Modules affected: aws-config-multi-region, ebs-encryption-multi-region, guardduty-multi-region, iam-access-analyzer-multi-region | Release notes

  • Adding region ap-southeast-4 as an optional region for use by GuardDuty

terraform-aws-service-catalog​

v0.130.7​

Published: 10/30/2025 | Modules affected: services/eks-workers | Release notes

  • Add Support for AL2023 EKS Worker AMI's

v0.130.6​

Published: 10/30/2025 | Modules affected: services, data-stores, networking | Release notes

  • services/ecs-fargate-cluster: Add standardized output names to ecs-fargate-cluster module
  • data-stores/aurora: Expose cluster-level Performance Insights and Database Insights parameters in Aurora module
  • networking/sns-topics: new option var.enable_advanced_formatting to enable CloudWatchNotification formatting for sns-to-slack

v0.130.5​

Published: 10/16/2025 | Modules affected: services/eks-core-services | Release notes

  • Add new variable cluster_autoscaler_container_extra_args to services/eks-core-services module for providing additional container args to the cluster autoscaler.

v0.130.4​

Published: 10/10/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-core-services | Release notes

  • Bump terraform-aws-eks library module to v1.5.1
    • Backport release to address upstream Bitnami Catalog Changes
    • Expose new variable in services/eks-core-services module for configuring external-dns image repository. New variable external_dns_image_repository created with default value set to bitnamilegacy/external-dns

v0.130.3​

Published: 10/9/2025 | Modules affected: modules/networking/vpc, modules/services/ec2-instance, modules/services/eks-argocd, modules/services/eks-cluster | Release notes

  • Add support for additional fstype configurations to services/ec2-instance module. Add/Expose the following variables to the services/ec2-instance module:
    • instance_device
    • instance_mount_path
    • instance_fstype
  • Bump terraform-aws-eks library module to v1.5.0
    • Add support for Node Repair Config for EKS Managed Node Groups.

v0.130.2​

Published: 10/9/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-core-services | Release notes

  • Bump terraform-aws-eks library module to v1.4.0
  • Bump default kubergrunt version to v0.18.1.
  • Add EKS Worker AL2023 Packer Template.

v0.130.1​

Published: 10/7/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-core-services | Release notes

  • Bump terraform-aws-eks library module to v1.3.0
  • Expose new variables asg_default_extra_block_device_mappings and autoscaling_group_configurations.extra_block_device_mappings in services/eks-workers and services/eks-cluster modules.

v0.130.0​

Published: 10/7/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-core-services | Release notes

  • Bump terraform-aws-eks library module to v1.2.0
  • Set default cluster_autoscaler_chart_version to 9.46.6 in eks-core-services module.

v0.129.3​

Published: 10/7/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-core-services | Release notes

  • Bump terraform-aws-eks library module to v1.1.1

v0.129.2​

Published: 10/3/2025 | Modules affected: modules/networking/vpc, modules/services/eks-argocd, modules/services/eks-cluster, modules/services/eks-core-services | Release notes

  • Bump terraform-aws-eks library module to v1.1.0

v0.129.1​

Published: 10/2/2025 | Modules affected: data-stores | Release notes

  • Fix monitoring_role_name reference in RDS module. Previously monitoring_role_name was being set by monitoring_role_arn and is now mapped correctly.