You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the docs, setting TF_LOG to WARN should decrease Terraform log level. However, doing so fires a warning that such log level is unreliable. What's the purpose of having the log levels? Have they been deprecated? I think the docs could clarify a bit here. What is the best approach to keep the log level down? Should we use something as suggested in #27214?
Actual Behavior
[WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.
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.
ghost
locked as resolved and limited conversation to collaborators
Mar 29, 2021
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Terraform Version
Expected Behavior
According to the docs, setting
TF_LOG
toWARN
should decrease Terraform log level. However, doing so fires a warning that such log level is unreliable. What's the purpose of having the log levels? Have they been deprecated? I think the docs could clarify a bit here. What is the best approach to keep the log level down? Should we use something as suggested in #27214?Actual Behavior
[WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.
Steps to Reproduce
Set
TF_LOG
toWARN
and run any terraform command.Additional Context
References
The text was updated successfully, but these errors were encountered: