Explanation
Terraform has detailed logs which can be enabled by setting the TF_LOG environment variable to any value.
This will cause detailed logs to appear on stderr.
You can set TF_LOG to one of the log levels TRACE, DEBUG, INFO, WARN or ERROR to change the
verbosity of the logs. TRACE is the most verbose and it is the default if TF_LOG is set to something other
than a log level name.
To persist logged output you can set TF_LOG_PATH in order to force the log to always be appended to a
specific file when logging is enabled. Note that even when TF_LOG_PATH is set, TF_LOG must be set in
order for any logging to be enabled.

Reference: https://cloud.google.com/kubernetes-engine/docs/how-to/creating-a-cluster-windows

Explanation
If supported by your backend, Terraform will lock your state for all operations that could write state. This
prevents others from acquiring the lock and potentially corrupting your state. Source:
https://www.terraform.io/language/state/locking

Explanation
The terraform fmt command is used to rewrite Terraform configuration files to a canonical format and style.
This command applies a subset of the Terraform language style conventions, along with other minor adjustments for readability.
Other Terraform commands that generate Terraform configuration will produce configuration files that conform to the style imposed by terraform fmt, so using this style in your own files will ensure consistency.
https://www.terraform.io/docs/commands/fmt.html