Terraform Import, Tainting Resources and Debugging
Debugging
This article explores enabling and using debugging in Terraform to troubleshoot and resolve issues effectively.
In this article, we explore how to enable and use debugging in Terraform to effectively troubleshoot and resolve issues. When Terraform errors occur, the first step is to review the log output. While Terraform’s error messages during provisioning are helpful, sometimes you need to dive deeper for an internal view.Terraform allows you to increase the debugging output by setting the environment variable TF_LOG to one of the available log level values. The supported log levels are: info, warning, error, debug, and trace—with trace providing the most detailed output.
For the most verbose logging, use TF_LOG=TRACE. This is particularly useful when facing complex issues that require insight into Terraform’s inner workings.
To enable the trace log level, set the TF_LOG environment variable as follows:
# export TF_LOG=<log_level>$ export TF_LOG=TRACE
After setting this variable, running any Terraform command will produce detailed logs corresponding to the selected verbosity level. For example, a Terraform plan run with TF_LOG set to TRACE might output hundreds or even thousands of lines, capturing every internal operation performed by Terraform plugins.Below is an example output from running terraform plan with elevated logging:
$ terraform plan2020/10/18 22:08:30 [INFO] Terraform version: 0.13.02020/10/18 22:08:30 [INFO] Go runtime version: go1.14.22020/10/18 22:08:30 [INFO] CLI args: []string{"C:\\Windows\\system32\\terraform.exe", "plan"}2020/10/18 22:08:30 [DEBUG] Attempting to open CLI config file: C:\\Users\\vpala\\AppData\\Roaming\\terraform.rc2020/10/18 22:08:30 [DEBUG] File doesn't exist, but doesn't need to. Ignoring.2020/10/18 22:08:30 [DEBUG] ignoring non-existing provider search directory terraform.d/plugins2020/10/18 22:08:30 [DEBUG] ignoring non-existing provider search directory C:\Users\\vpala\AppData\Roaming\HashiCorp\Terraform\plugins2020/10/18 22:08:30 [DEBUG] ignoring non-existing provider search directory 2020/10/18 22:08:30 [INFO] CLI command args: []string{"plan"}2020/10/18 22:08:30 [WARN] Log levels other than TRACE are currently unreliable, and are supported only for backward compatibility.Use TF_LOG=TRACE to see Terraform's internal logs.----2020/10/18 22:08:30 [DEBUG] New state was assigned lineage "f413959c-538a-f9ce-524e-1615073518d4"2020/10/18 22:08:30 [DEBUG] checking for provisioner in "."2020/10/18 22:08:30 [DEBUG] checking for provisioner in "C:\\Windows\\system32"2020/10/18 22:08:30 [INFO] Failed to read plugin lock file .terraform\plugins\windows_amd64\lock.json: The system cannot find the path specified.2020/10/18 22:08:30 [INFO] backend/local: starting Plan operation2020/10/18 22:08:30.646-0400 [DEBUG] plugin: starting plugin: path=terraform/plugins/registry.terraform.io/hashicorp/aws/3.11.0/windows_amd64/terraform-provider-aws_v3.11.0_x5.exe args=[]2020/10/18 22:08:30.935-0400 [DEBUG] plugin: waiting for RPC address: path.terraform/plugins/registry.terraform.io/hashicorp/aws/3.11.0/windows_amd64/terraform-provider-aws_v3.11.0_x5.exe pid=340162020/10/18 22:08:30.974-0400 [DEBUG] plugin: configuring server automatic mTLS:
If you want to persist these logs to a file for later review or to include them in bug reports, set the environment variable TF_LOG_PATH with the desired file path as shown below:
$ export TF_LOG_PATH=/tmp/terraform.log
All generated logs will then be recorded in the specified file. To quickly inspect the beginning of your log file, you can use a command like:
$ head -10 /tmp/terraform.log
An example snippet from the log file might look like this:
To completely disable the debugging output, simply unset the environment variables:
$ unset TF_LOG$ unset TF_LOG_PATH
Remember to unset these variables when you no longer need detailed logs, as verbose logging can expose sensitive information and impact performance.
That concludes our discussion on debugging Terraform. Up next, you’ll have the opportunity to practice Terraform tainting and explore additional debugging techniques through interactive exercises.For more information, visit the Terraform Documentation for an in-depth look at other available commands and best practices.
