-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix log level #12093
Milestone
Comments
@jimsnab this is controlled by Terraform Core. Do you want to file an issue over there instead? |
Using The Google provider can be changed to use the tflog api instead and solve the issue. |
modular-magician
added a commit
to modular-magician/terraform-provider-google
that referenced
this issue
Oct 23, 2024
[upstream:db2e60d6251d68d9cd98621e686c99078903cd24] Signed-off-by: Modular Magician <magic-modules@google.com>
modular-magician
added a commit
that referenced
this issue
Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Community Note
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 tohashibot
, a community member has claimed the issue already.Terraform Version
Affected Resource(s)
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:
Thus the provider's logging is very noisy.
Steps to Reproduce
export TF_LOG=info
terraform apply
in a project of your choosing that uses the google providerThe text was updated successfully, but these errors were encountered: