-
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
PlanResourceChange panic: can't use ElementIterator on null value #1964
Labels
impact/panic
This bug represents a panic or unexpected crash
kind/bug
Some behavior is incorrect or out of spec
resolution/fixed
This issue was fixed
Comments
VenelinMartinov
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 13, 2024
This seems to bottom out at #1970 |
This was referenced May 14, 2024
Yes I agree. fastly.resourceService.validateUniqueNames expects empty set instead of null. |
Can we fix this? |
mikhailshilkov
added
the
impact/panic
This bug represents a panic or unexpected crash
label
May 28, 2024
Marked it as |
This likely does not affect end-users right now as the bridge feature is only rolled out to a few resources. |
This was referenced Jun 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
impact/panic
This bug represents a panic or unexpected crash
kind/bug
Some behavior is incorrect or out of spec
resolution/fixed
This issue was fixed
What happened?
During PlanResourceChange testing, the following error was discovered:
pulumi-fastly paniced during preview on one of the resource with the above error
pulumi/pulumi-fastly#536
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).
The text was updated successfully, but these errors were encountered: