Sergej Zagursky

Formally it looks more like not a breaking change but an API clarification. But I do agree that it might break some code. I would certainly object against solutions like...

I believe this should be fixed in `tfenv` and not in Terragrunt. `tfenv` outputs its log messages to stdout, and Terragrunt can't control it. There is [an issue](https://github.com/tfutils/tfenv/issues/310) in `tfenv`...

I run inspec using Docker container as follows: ```bash docker run -it --rm -v $(pwd):/share chef/inspec exec spec.rb ``` Here's the `spec.rb` I use: ```ruby control "Test" do describe command("echo...

Also, ``` $ docker run -it --rm -v $(pwd):/share chef/inspec version 5.23.6 ```

Adding `TG_NO_DESTROY_DEPENDENCIES_CHECK=true` "fixes" the problem. It seems that without this option Terragrunt traverses the entire Git working copy and tries to parse all `terragrunt.hcl` it encounters.

I currently use the following fragile configuration snippet for Terragrunt as a workaround: ```hcl terraform { before_hook "asdf_current_copy" { commands = startswith(get_working_dir(), get_terragrunt_dir()) ? [] : ["init", "plan", "apply", "taint",...