No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

This looks like <https://github.com/pulumi/pulumi-gcp/issues/876> which was marked closed.

One thing I'd try is to do an update which _just_ sets deletionProtection. Then do another update which triggers the replace.

I’m having the same issue with a SQL db when doing a `down`.  Ver annoying.  In gcp console and my pulumi script, deletion protection is false.

I also have refresh enabled as well.

I had one case where the error message changed to _something_ _like_ “could not delete because 6 objects depend on the db_instance”.  Perhaps coincidentally a plug was updated just before I saw this.

We got rid of  some issues for sql.User and  sql.Databaseby setting:

Still need to manually delete the db instance via the console, gcloud cmd, etc. before doing a pulumi down.