This message was deleted.

This message was deleted.

I'm running into an issue deleting some resources and it's unclear why. I have two resources (both on Google Cloud), one (let's call it the "backend") is listed as a dependency of the other (in both Google Cloud and Pulumi) (let's call it the "instance group manager"). They are both to be deleted, but Pulumi is trying to delete the "instance group manager" first, which fails because internally to Google Cloud the dependency is present... ideally Pulumi (which knows about this dependency) would delete the thing that's holding the dependency first (the "backend") then delete the thing depended upon (the "instance group manager") -- any ideas on how to fix this ?

This message was deleted.

This message was deleted.

This message was deleted.

Hi folks, how can I make Pulumi not change my ECS task definition container image on subsequent runs? i.e. if said service already has an existing task definition, just reuse latest container image and update the other properties normally, creating a new revision.

This message was deleted.

This message was deleted.

This message was deleted.