terragrunt 0.85.0

[BrewTestBot]

Created by brew bump

---

Created with brew bump-formula-pr.

Details

release notes

## 🛠️ Breaking Changes
Removal of legacy Terragrunt flags
All deprecated flags that start with --terragrunt-  have been removed in favor of their modern counterparts.
This is the next step in the removal of deprecated features in

Terragrunt on the road to Terragrunt 1.0, with more to follow. Read the  CLI Redesign migration guide for future breaking changes.
Update of stack run directory context
The stack run command no longer assumes that users will have a .terragrunt-stack directory present in the same directory as the terragrunt.stack.hcl file. This caused issues for users that were leveraging the no_dot_terragrunt_stack attribute, as the run might have skipped over units generated outside the .terragrunt-stack directory and thrown an error if all units were generated without the .terragrunt-stack directory.
For the following terragrunt.stack.hcl file:
unit "foo" {
  source = "../units/foo"
  path   = "foo"

  no_dot_terragrunt_stack = true
}

unit "bar" {
  source = "../units/bar"
  path   = "bar"
}
Users would experience the following stack run output:

They will now get the following:

✨ Features
The runner-pool experiment has been integrated with OpenTelemetry
The runner-pool experiment has been updated to integrate properly with OpenTelemetry.
🐛 Bug Fixes
stack output now respects no_dot_terragrunt_stack
Previously, when running the stack output command, Terragrunt would incorrectly assume that all units were generated within a .terragrunt-stack directory. This bug has been fixed, and Terragrunt will know to look directly in the stack directory for a given unit when supplied with no_dot_terragrunt_stack.
The runner-pool experiment no longer parses stack files as units during discovery
A bug in the logic for the discovery package resulted in discovery errors due to terragrunt.stack.hcl files being parsed as units. That bug has been fixed.
Fixed filesystem context for find_in_parent_folders() when used in terragrunt.stack.hcl
The use of find_in_parent_folders() now functions correctly when run in the context of a terragrunt.stack.hcl file. Previously, it relied on the current working directory of the Terragrunt CLI, which incorrectly assumed that users would always be generating terragrunt.stack.hcl files from the current working directory.
The discovery package now emits less false positive warnings during parsing
The discovery package used by the find and list commands, and the runner-pool experiment has been updated to emit less unimportant warnings when parsing configurations. These warnings were for early phase parsing that are known to be safe to ignore.
The discovery package no longer attempts to parse stack configurations as units
A bug in the implementation of the discovery package resulted in attempts from Terragrunt to parse terragrunt.stack.hcl files as units. That has been remediated.
📖 Docs
Edit Link Added
The terragrunt-v1.gruntwork.io docs now include an "Edit page" button that conveniently allows the community to contribute fixes to documentation from within their browsers, using the GitHub UI.

What's Changed

feat: runner-pool OpenTelemetry integration by @denis256 in feat: runner-pool opentelemetry integration gruntwork-io/terragrunt#4616
fix: Discovery false positive parsing errors by @denis256 in feat: Discovey false positive parsing errors gruntwork-io/terragrunt#4605
fix: Adding edit link back by @yhakbar in fix: Adding edit link back gruntwork-io/terragrunt#4629
fix: Make stack output respect no_dot_terragrunt_stack by @yhakbar in fix: Make stack output respect no_dot_terragrunt_stack gruntwork-io/terragrunt#4606
fix: Fix broken screenshot in logging page by @josh-padnick in Fix broken screenshot in logging page gruntwork-io/terragrunt#4630
fix: Improve error handling for missing includes and dependencies by @yhakbar in fix: Improve error handling for missing includes and dependencies gruntwork-io/terragrunt#4637
fix: ensure --queue-include-dir includes stack paths that have not yet been generated by @wakeful in ensure queue-include-dir includes stack paths that have not yet been generated gruntwork-io/terragrunt#4649
fix: Fixing bad link to stack output command by @yhakbar in fix: Fixing bad link to stack output command gruntwork-io/terragrunt#4652
fix: Fixing stack run when there are only units with no_dot_terragrunt_stack set by @yhakbar in fix: Fixing stack run when there are only units with no_dot_terragrunt_stack set gruntwork-io/terragrunt#4628
fix: Fixing find_in_parent_folders for terragrunt.stack.hcl files by @yhakbar in fix: Fixing find_in_parent_folders for terragrunt.stack.hcl files gruntwork-io/terragrunt#4669
fix: Addressing provider cache test flake by @yhakbar in fix: Addressing provider cache test flake gruntwork-io/terragrunt#4639
fix: Fixing discovery parsing stacks as units by @yhakbar in fix: Fixing discovery parsing stacks as units gruntwork-io/terragrunt#4615
docs: Updating migration guide for --terragrunt- flag removal by @yhakbar in docs: Updating migration guide for --terragrunt- flag removal gruntwork-io/terragrunt#4671
chore: Addressing review feedback by @yhakbar in chore: Addressing review feedback gruntwork-io/terragrunt#4672
chore: Getting rid of strict lint workflow by @yhakbar in chore: Getting rid of strict lint workflow gruntwork-io/terragrunt#4651
chore: Remove legacy terragrunt flags by @yhakbar in chore: Remove legacy terragrunt flags gruntwork-io/terragrunt#4650
chore: Sequencing workflows so that faster workflows run before slower ones by @yhakbar in feat: Sequencing workflows so that faster workflows run before slower ones gruntwork-io/terragrunt#4670
chore: Adding error message bug report by @yhakbar in chore: Adding error message bug report gruntwork-io/terragrunt#4638

Full Changelog: gruntwork-io/terragrunt@v0.84.1...v0.85.0

View the full release notes at https://github.com/gruntwork-io/terragrunt/releases/tag/v0.85.0.

---

[github-actions]

🤖 An automated task has requested bottles to be published to this PR.

Caution

Please do not push to this PR branch before the bottle commits have been pushed, as this results in a state that is difficult to recover from. If you need to resolve a merge conflict, please use a merge commit. Do not force-push to this PR branch.