| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| terragrunt_windows_amd64.exe | 2025-10-23 | 77.0 MB | |
| terragrunt_windows_386.exe | 2025-10-23 | 71.0 MB | |
| terragrunt_linux_arm64 | 2025-10-23 | 70.1 MB | |
| terragrunt_linux_amd64 | 2025-10-23 | 75.1 MB | |
| terragrunt_linux_386 | 2025-10-23 | 69.0 MB | |
| terragrunt_darwin_arm64 | 2025-10-23 | 73.1 MB | |
| SHA256SUMS | 2025-10-23 | 633 Bytes | |
| terragrunt_darwin_amd64 | 2025-10-23 | 78.2 MB | |
| README.md | 2025-10-23 | 4.5 kB | |
| v0.91.3 source code.tar.gz | 2025-10-23 | 8.3 MB | |
| v0.91.3 source code.zip | 2025-10-23 | 9.9 MB | |
| Totals: 11 Items | 531.7 MB | 0 | |
✨ New Features
--reading flag added to the find command
The find command now supports the --reading flag, which allows you to discover the shared configurations read by units and stacks when using the --json format.
:::bash
$ terragrunt find --reading --json
[
{
"type": "unit",
"path": "aws-account-1",
"reading": [
"aws-data.yml"
]
},
{
"type": "unit",
"path": "aws-account-2",
"reading": [
"aws-data.yml"
]
},
{
"type": "unit",
"path": "gcp-project-1",
"reading": [
"gcp-data.hcl"
]
}
]
You can use this information to drive custom logic in your workflows based on the changes related to particular files.
e.g.
:::bash
$ terragrunt find --reading --json | jq '[.[] | select(.reading[]? | contains("aws-data.yml"))| .path]'
[
"aws-account-1",
"aws-account-2"
]
$ terragrunt find --reading --json | jq '[.[] | select(.reading[]? | contains("gcp-data.hcl"))| .path]'
[
"gcp-project-1"
]
You can learn more about the --reading flag in the find documentation.
🐛 Bug Fixes
Empty stacks no longer throw errors
Previously, a bug in the logic used for making sure that users didn’t accidentally run on empty stacks resulted in users getting a non-zero exit code when all units in a stack were excluded (e.g. via the exclude block).
That bug has been fixed.
Dependency outputs can now be used in generate blocks
Previously, a bug in the way HCL parsing was done during discovery resulted in errors being thrown for users when dependency outputs were used in generate blocks. That error has since been resolved.
That bug has been fixed.
What's Changed
- feat: Adding reading support in
findby @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/5002 - fix: Removing filter enabled check on empty stacks by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/4992
- fix: reference of dependency outputs in generate by @denis256 in https://github.com/gruntwork-io/terragrunt/pull/4994
- docs: Documenting new
-readingflag forfindby @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/5003 - docs: Fixing --source-map explanation by @atheiman in https://github.com/gruntwork-io/terragrunt/pull/4997
- docs: Fixing
Filtersdocs by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/4996 - chore: Tracking DAG nodes in components by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/4998
- chore: Tracking reads in components by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/5000
- chore: Updating language in discovery commands by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/5001
- chore: Using a standard shell string parsing library instead of handling it ourselves by @yhakbar in https://github.com/gruntwork-io/terragrunt/pull/4991
- build(deps): bump the js-dependencies group across 1 directory with 5 updates by @dependabot[bot] in https://github.com/gruntwork-io/terragrunt/pull/4993
- build(deps): bump vite from 6.3.6 to 6.4.1 in /docs-starlight by @dependabot[bot] in https://github.com/gruntwork-io/terragrunt/pull/4999
New Contributors
- @atheiman made their first contribution in https://github.com/gruntwork-io/terragrunt/pull/4997
Full Changelog: https://github.com/gruntwork-io/terragrunt/compare/v0.91.2...v0.91.3