STDOUT for destroy operations unexpectedly is logged at DEBUG level

[Kab1r]

Describe the bug

Running terragrunt destroy from a module that includes a parent causes destroy logs to go to DEBUG log level instead of stdout.

Steps To Reproduce

# Setup Directory
cd (mktemp -d)
mkdir terragrunt-destroy-log-bug
cd terragrunt-destroy-log-bug

# Setup Terragrunt Files
touch terragrunt.hcl
mkdir example
echo 'include {
  path = find_in_parent_folders()
}' > example/terragrunt.hcl
echo 'resource "null_resource" "example" {}' > example/example.tf

# Apply
cd example
terragrunt apply  -auto-approve

# Destroy
terragrunt destroy # No messages on stdout
terragrunt destroy --terragrunt-log-level debug # Messages appear

Expected behavior

Destroy logs should go to stdout.

Nice to haves

• Terminal output
• Screenshots

Terminal Recording of Bug:

Versions

• Terragrunt version: 0.69.7
• OpenTofu/Terraform version: v1.8.6
• Environment details (Ubuntu 20.04, Windows 10, etc.): MacOS Sonoma 14.7.1 (23H222)

Additional context

N/A

[yhakbar]

Thanks for reporting this, @Kab1r . We'll take a look at this soon and get back to you.

[levkohimins]

Resolved in v0.69.10 release.