prehistoric-activity-61023
06/05/2022, 9:15 PMpulumi refresh
, I got a lot of complaints. The new disk created from the snapshot, even though it had the same name, differs from the original one because of snapshot
and image
fields values. My question is: is it a legit scenario in GCP where I should use ignore_changes
on Disk resource?image
parameter (so I could create the whole infrastructure on the new env without any issues) and added snapshot
and image
to ignore_changes
so it doesn’t complain if it changes on the cloud (mainly, image -> null
an snapshot -> <some value>
). It would be nice to get some 👍 /👎 from Pulumi/TF + GCP veteran 🙂.