Open brent-statsig opened 5 hours ago
Oh - I figured out the issue, deleteBeforeReplace
needs to be enabled. This feels very unintuitive though, especially since so many GCP resources are globally unique by resource id, and will run into this problem. Especially with things like tables/datasets/etc, which will be referenced by their name external to pulumi, there is no "uptime" friendly way to do a replace.
Can these resources be changed to have deleteBeforeReplace
be defaulted to true?
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).