Lack of Diagnostic Information when Bug present in Upstream Provider #2413
Labels
impact/accessibility
Something that is difficult or impossible for some people to use
kind/enhancement
Improvements or new features
What happened?
When an upstream provider has a bug that triggers an
inconsistent result of apply
error, our downstream providers displays this behavior as a spurious diff without any error or diagnostics. I would expect the behavior to display a log or show what is causing the spurious diff.Example
Example Error
When I translate the code to pulumi in a bridged provider instead of an error I get a spurious diff and doesn't appear in the logs even when TF_LOG=debug is used.
Output of
pulumi about
N/A
Additional context
I think the behavior itself is actually acceptable in that it doesn't throw an error and is an upstream bug that needs to be fixed, but I would expect a diagnostic log to show up to help troubleshoot this or some sort of warning.
Currently it is very difficult to figure out what is causing the spurious diff if the resource has a complex schema, whereas in TF the error points you to the problem immediately
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).
The text was updated successfully, but these errors were encountered: