-
Notifications
You must be signed in to change notification settings - Fork 52
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
Re-creating materialized view fails (gcp.bigquery.Table) #2491
Comments
Oh - I figured out the issue, Can these resources be changed to have |
Hey @brent-statsig, thanks for reporting and sorry you've hit this. Glad you found a workaround, that seems like the right way to go about it. Unfortunately, you've hit a bit of a corner case with the pulumi resource model: pulumi/pulumi#918 I'll look into adding the |
Bigquery materialized views on tables seem to be structural, so due to pulumi/pulumi#918 the normal pulumi replace of creating and then deleting does not work. This PR enables DeleteBeforeRelace by default for the resource, fixing the issue. fixes #2491
This issue has been addressed in PR #2498 and shipped in release v8.5.0. |
Describe what happened
package.json
Updating a materialize view in bigquery triggers a replacement, that fails, because the table already exists in bigquery.
Sample program
pulumi up
Log output
Affected Resource(s)
No response
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: