-
Notifications
You must be signed in to change notification settings - Fork 43
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
Empty map incorrectly translates to null #1106
Comments
t0yv0
added
needs-triage
Needs attention from the triage team
kind/bug
Some behavior is incorrect or out of spec
and removed
needs-triage
Needs attention from the triage team
labels
May 11, 2023
Some more context from debugging. main.py:
repro.sh:
Instrumented provider trace:
Pulumi schema:
gRPC trace of the Read method.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
The original issue pulumi/pulumi-aws#2517 (comment) uncovered a problem in the bridge. Under certain circumstances an empty object generated by the upstream provider turns into
null
on the wire when returned from the bridge, which is unexpected. A preferred form would use{}
or{"field": null}
possibly to represent this object.Expected Behavior
Empty objects are represented in a way distinct from null.
Steps to reproduce
pulumi/pulumi-aws#2517 has a full repro. We also have a unit test reproducing the issue available in #1105
Output of
pulumi about
Additional context
This may be fixed by #887
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: