Open zbuchheit opened 6 months ago
Thanks for reporting and for the detailed repro!
Unfortunately, we'd need to sort out access credentials for the provider before we can address issues here.
adding some additional details to this as i have created my own instance of ISE in AWS.
In my testing, the provider is behaving as if the TF_LOG level is set to DEBUG automatically. When I test the equivalent in TF, I don't get the same behavior so this does appear to be a bug in the bridged provider.
Note similar issues in Meraki and https://github.com/pulumi/pulumi-databricks/issues/474. Potentially related too: https://github.com/pulumi/pulumi-gitlab/issues/514
When digging into it, it looks like this is likely coming from the go library used. That being said, I am curious why this behaves differently in the upstream provider.
source: https://github.com/netascode/go-ise/blob/b9cb4ca5f659fcad3ca9b0d4526abcfa5766e390/client.go#L142
When digging into it, it looks like this is likely coming from the go library used. That being said, I am curious why this behaves differently in the upstream provider.
source: https://github.com/netascode/go-ise/blob/b9cb4ca5f659fcad3ca9b0d4526abcfa5766e390/client.go#L142
Terraform doesn't display provider stdout to the user by default, but we do. https://github.com/pulumi/pulumi-terraform-bridge/issues/2489 tracks that discrepancy.
What happened?
While using the provider, all resources I was creating or functions I was using resulted in the corresponding api call being logged to the output.
Example
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).