-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Terraform commands prepend "o:" and "e:" to lines when run recursively inside local-exec #20293
Comments
This problem is caused by Terraform's mechanism for capturing Go panics, which re-runs Terraform inside a child process and captures the output in order to filter it for crash messages. When Terraform itself is the one launching The handling of this panic mechanism is encapsulated in the separate library That solution would address it for all users of Lines 99 to 100 in 75d3f1e
|
@teamterraform @apparentlymart Can I pick this issue up? |
Hi @avinashdhinwa! Running Terraform recursively inside itself is an unusual use-case that I would not normally encourage, but based on the above it seems like fixing this quirk shouldn't do any harm, so I think it's fine to do it for robustness. It's likely to be more of benefit to other software than to Terraform (other software might have more reason to recursively launch itself) so I'd be inclined to try for the fix in the With that said, |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Terraform Version
Terraform Configuration Files
Debug Output
Expected Behavior
Output of the provision command should be
default
.Actual Behavior
Output of the provision command is
o:default
.Steps to Reproduce
terraform init
terraform apply
Additional Context
This does not happen when I run
terraform workspace show
in the same directory in a different shell, while the plan is being executed. It only seems to happen when terraform is invoked within terraform.The text was updated successfully, but these errors were encountered: