This message was deleted.

sparse-intern-71089

03/26/2020, 7:44 PM

This message was deleted.

white-balloon-205

03/26/2020, 7:48 PM

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.

cool-egg-852

03/26/2020, 7:48 PM

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

cool-egg-852

03/26/2020, 7:49 PM

Very easy to completely break an entire GCP project

cool-egg-852

03/26/2020, 7:52 PM

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

white-balloon-205

03/26/2020, 7:53 PM

Ahh - actually - there is a key thing I wasn't aware of -

gcp.projects.Services

has a

disableOnDestroy

which can be set to false.

white-balloon-205

03/26/2020, 7:53 PM

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

cool-egg-852

03/27/2020, 1:11 PM

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

cool-egg-852

03/27/2020, 1:11 PM

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

cool-egg-852

03/27/2020, 1:12 PM

The resource in the SDK that is

Open in Slack

Previous Next

Pulumi Community

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.