Fix log level

[jimsnab]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
• Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.
• If an issue is assigned to the modular-magician user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to hashibot, a community member has claimed the issue already.

Terraform Version

Terraform v1.2.5
on linux_amd64

Affected Resource(s)

• google_*

Debug Output

The provider is using Terraform suggestion to print the log level in a log message, but Terraform has a bug where it captures the provider's output and prints it as [INFO]. Note the [INFO] and [DEBUG] on the same line. Hashicorp says they won't fix this.

Instead, they've provided their own logging API that the provider can use, which includes the log level as an explicit parameter. See tflog.

Actual Behavior

Example of Google Provider log output:

2022-07-14T10:26:03.548-0400 [INFO]  provider.terraform-provider-google_v4.28.0_x5: 2022/07/14 10:26:03 [DEBUG] Retry Transport: starting RoundTrip retry loop: timestamp=2022-07-14T10:26:03.548-0400
2022-07-14T10:26:03.548-0400 [INFO]  provider.terraform-provider-google_v4.28.0_x5: 2022/07/14 10:26:03 [DEBUG] Retry Transport: request attempt 0: timestamp=2022-07-14T10:26:03.548-0400
2022-07-14T10:26:03.889-0400 [INFO]  provider.terraform-provider-google_v4.28.0_x5: 2022/07/14 10:26:03 [DEBUG] Retry Transport: Stopping retries, last request was successful: timestamp=2022-07-14

Thus the provider's logging is very noisy.

Steps to Reproduce

1. Turn on logging, e.g., export TF_LOG=info
2. terraform apply in a project of your choosing that uses the google provider
3. Expect only INFO and higher, but actually get DEBUG (and TRACE, if the provider uses it)

[edwardmedia]

@jimsnab this is controlled by Terraform Core. Do you want to file an issue over there instead?

[jimsnab]

Using log.*() yes it is Terraform Core where it is already known and won't fix.

The Google provider can be changed to use the tflog api instead and solve the issue.