-
Notifications
You must be signed in to change notification settings - Fork 67
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
[question] - [DEBUG] messages from the ccloud-sdk ? #372
Comments
@FabioBatSilva thanks for creating the issue! Here are 2 code pointers that might be helpful: |
Thanks @linouk23, that was very helpfull. I believe i found the log entries tha are causing problem. When running with debug enabled i get :
It seems like the http call logs get double formatted for some reason.
I guess that might be causing issues with the pulumi bridge: I'll post my finding on the pulumi side, but perhaps we can also clean that up here.. Any idea where that message is getting formatted ? |
Thanks for investigating it @FabioBatSilva! I'm not sure whether it helps but
are coming from TF Provider logs directly:
whereas logs like
are coming from the SDK. It also seems like all of
correspond to SDK logs. |
Thanks.. Just got some pointers here The theory is that retryablehttp client seems to be using i'ts own logger
https://github.com/hashicorp/go-retryablehttp/blob/main/client.go#L609-L616 I think there might also be an issue with the way pulumi parses the logs Will try to test that out tomorow. |
Thank you for waiting. Fixed the formatting issues in the ccloud-sdk in the latest v1.81.0 terraform release |
I understand this might not be a issue with the confluent terraform provider
But i'm trying to track down this issue : pulumi/pulumi-confluentcloud#48 and it has led me here.
It seems like the terraform provider is flooding the logs with
[DEBUG]
messages from the ccloud-sdk.Is this something confluent terraform provider is configured to do ?
Can someone please point me to where the log level for the sdk is defined ?
Thanks
The text was updated successfully, but these errors were encountered: