-
Notifications
You must be signed in to change notification settings - Fork 54
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
Bigquery Dataset panic on partial state resource .get due to TF Importer method not being called #2285
Comments
This was fixed with a patch, so not a P1. |
The panic is still there without the patch, we should investigate further. |
Going to keep this as a P1 until we verify if there's a bridge bug. We want to be sure other providers are not affected. |
Root caused to pulumi/pulumi-terraform-bridge#2282 The issue is that the Importer method is not called but the bridge calls TF Refresh without a resource ID. This in turn, leads to the wrong GCP API call - it calls the GET method on which returns the wrong format for the response, breaking the code. Note that the GCP |
Because this is not a regression (it never worked) and because we no longer panic (with the patch), there is no reason for this to be a P1. |
What happened?
We have a recurring panic fixed via patch, where if we are reading a
gcp.bigquery.dataset
resource with a nonexistent Project, the provider panics on preview.This panic should instead surface an error.
We did not find a corresponding issue in the upstream provider and therefore suspect this is a bridge bug; however, we should verify that this is not an upstream bug.
Example
Here's the program (must be run on unpatched GCP provider, e.g. v6.50.0)
and after
pulumi up
we get the following stack trace:Output of
pulumi about
Note that this repro is done on an older version of pulumi-gcp. We have created a patch to address this issue.
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: