-
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
Infer Map[string] when the Map's element type is unspecified #2316
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #2316 +/- ##
==========================================
- Coverage 56.93% 56.90% -0.03%
==========================================
Files 365 365
Lines 49957 49961 +4
==========================================
- Hits 28443 28431 -12
- Misses 19973 19987 +14
- Partials 1541 1543 +2 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great find! Did you test this in nomad?
Can we also add an integration test for the panic?
One more case missed in #1828 it seems. |
I tested this in nomad, the error case becomes unrepresentable. I haven't added an integration test for the panic in nomad, and we shouldn't need to: The bridge translation ensures that (TF) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense, you are saying the tfgen test is sufficient here. Sounds good
SDKv2 providers allow specifying a map type without a backing element type:
Previously, the bridge interpreted this as
map[any]
. This does not agree with TF's interpretation:map[string]
. This PR changes the bridge to correctly interpretmap[???]
asmap[string]
.Fixes pulumi/pulumi-nomad#389