Setting the TF_LOG environment variable to DEBUG causes debug messages to be logged into stdout.
Setting the TF_LOG environment variable to DEBUG causes debug messages to be logged into stdout.
Setting the TF_LOG environment variable to DEBUG causes debug messages to be logged to stderr, not stdout. According to Terraform's documentation, detailed logs appear on stderr when this environment variable is enabled.
B Because it's stdrr
Setting the TF_LOG environment variable to DEBUG causes debug messages to be logged to standard output (stdout) or standard error (stderr)
chat gpt
Correct is B. False - not "stdut" but stderr" https://developer.hashicorp.com/terraform/internals/debugging "Terraform has detailed logs that you can enable by setting the TF_LOG environment variable to any value. Enabling this setting causes detailed logs to appear on stderr."
"Terraform has detailed logs that you can enable by setting the TF_LOG environment variable to any value. Enabling this setting causes detailed logs to appear on stderr." https://developer.hashicorp.com/terraform/internals/debugging
B Because it's stdrr
https://developer.hashicorp.com/terraform/internals/debugging
Setting the TF_LOG environment variable to DEBUG causes debug messages to be logged, but they are sent to the standard error (stderr) stream by default, not to standard output (stdout). To redirect or persist these logs, you can use additional configurations such as TF_LOG_PATH to specify a file for logging.
The correct answer is: ✅ A. True Explanation: Setting the TF_LOG environment variable to DEBUG causes Terraform to log debug-level messages into stdout (standard output). This is helpful for troubleshooting and understanding the inner workings of Terraform during execution.