I had to restore the disk from the snapshot and after `pulum

Question

I had to restore the disk from the snapshot and after `pulumi 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

prehistoric-activity-61023 · Answer

Well this is what I did at least I left the definition in code with `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 gt null` an `snapshot gt lt some value gt ` It would be nice to get some thumbsup thumbsdown from Pulumi TF + GCP veteran slightly smiling face