Is it save to have a stack change from `gcp.projec...
# generalc
cool-egg-852
03/26/2020, 7:44 PMIs it save to have a stack change from
gcp.projects.Servicesgcp.projects.Servicew
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.Servicepulumi state deletegcp.projects.Servicesgcp.projects.Servicesc
cool-egg-852
03/26/2020, 7:48 PMThis 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 PMVery easy to completely break an entire GCP project
cool-egg-852
03/26/2020, 7:52 PMI am going the route of the state delete, but overall, this is quite scary
w
white-balloon-205
03/26/2020, 7:53 PM
Ahh - actually - there is a key thing I wasn't aware of -
gcp.projects.ServicesdisableOnDestroywhite-balloon-205
03/26/2020, 7:53 PM
Then you can make this change safely if you've deployed that change first.
c
cool-egg-852
03/27/2020, 1:11 PMCan’t though because the resource doesn’t exist anymore.
cool-egg-852
03/27/2020, 1:11 PMI’m already passed this, but other people may not be.
cool-egg-852
03/27/2020, 1:12 PMThe resource in the SDK that is