teamterraform
commented
5 years ago 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 terraform, such as in local-exec, it mistakenly detects that it's already the child process and so the details of that filtering mechanism leak out.
The handling of this panic mechanism is encapsulated in the separate library panicwrap, so the fix for this would likely need to be made over there. One possible fix is for panicwrap.Wrap to immediately unset the environment variables it uses for detection after it's confirmed it's in the child process, so that any later code in the program -- including launching any child processes -- will see itself as a fresh execution context, not a panicwrap child.
That solution would address it for all users of panicwrap. A more localized solution would be to have Terraform itself unset the environment variable. panicwrap exposes DEFAULT_COOKIE_KEY, which means that Terraform could potentially unset it without duplicating that magic value. Were Terraform to handle it, it would need to happen just before calling wrappedMain so that it's stripped out before we run the main Terraform functionality:
avinashdhinwa
apparentlymart
ghost
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 initterraform applyAdditional Context
This does not happen when I run
terraform workspace showin the same directory in a different shell, while the plan is being executed. It only seems to happen when terraform is invoked within terraform.