-
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
Fix bigquery table replace hitting "already exists" issue #2498
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. Maintainer note: consult the runbook for dealing with any breaking changes. |
Seems reasonable, especially since BigQuery Tables seem to be a bit more about supporting the analytics world where liveness guarantees are less of a problem presumably than transactional databases. A bit drastic but the underlying resource lifecycle seemed completely not working right before so this looks like a good default. |
We've been using this for structural resources in AWS quite extensively - we don't really have much better options for resource like this = ( |
This PR has been shipped in release v8.5.0. |
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