-
Notifications
You must be signed in to change notification settings - Fork 155
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
https://github.com/pulumi/examples/tree/master/aws-ts-organizations panics #2513
Comments
Can you share your |
It's set in the example (explicit provider):
|
Looks like there's might be a behavior change originating from pulumi/pulumi-terraform-bridge#991 work. Looks like PreConfigureCallback may now be exposed to to Computed values representing "unknowns" at preview. This is an unintentional change. What should we do here, what's the desired by-design behavior, 🤔 Perhaps we should skip PreConfigurCallback? Replace unknowns with null before calling it? |
Let's see what the prior behavior was. I think what happens is if there are unknowns, the engine would call CheckConfig with the unknowns but if CheckConfig returns the unknowns back it would not call Configure. So the prior behavior was that the PreConfigureCallback would not get called at all in this situation I think. I can confirm experimentally. |
Updating to https://github.com/pulumi/pulumi-terraform-bridge/releases/tag/v3.46.1 bridge should fix the issue. |
As the original reporter of the issue in Slack, I can confirm that this issue is now resolved in |
What happened?
Trying to run https://github.com/pulumi/examples/tree/master/aws-ts-organizations (with some minor fixups to create the organization) causes a panic in the aws provider.
Expected Behavior
The example to work
Steps to reproduce
aws:region
andaws-ts-organizations:devAccountEmailContact
)pulumi up
Output of
pulumi about
Additional context
Reported initially on community slack at https://pulumi-community.slack.com/archives/C01PF3E1B8V/p1683276289324129
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: