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

That might not actually be safe.  The create of the new resource will happen before the delete of the old resource, and depending on how GCP and the upstream Terraform provider implement this, that may actually delete the service access.

If you want to be safe, you could add the `gcp.projects.Service`, deploy it, `pulumi state delete` the `gcp.projects.Services`, remove the `gcp.projects.Services` from code, and deploy again.

This seems like something that should probably have been handled when pulumi updated the terraform provider to v3

Very easy to completely break an entire GCP project

I am going the route of the state delete, but overall, this is quite scary

Ahh - actually - there is a key thing I wasn't aware of - `gcp.projects.Services` has a `disableOnDestroy` which can be set to false.

Then you can make this change safely if you've deployed that change first.

Can’t though because the resource doesn’t exist anymore.

I’m already passed this, but other people may not be.