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.

Pulumi Community

I would look up the AMI ID by hand and put it in your config. It can of course be solved in code, but this lookup-once-deploy-many-times problem is easiest solved by hand.

Also, this way, you can decide (in the form of raising a PR and doing a code review) when you want to update the machine to the latest image.

In Terraform it is easily solved with:
```  lifecycle {
    ignore_changes = [ ami ]
  }```
I suppose, Pulumi does not have an equivalent? :thinking_face:

&gt;  I would look up the AMI ID by hand and put it in your config
This is what I ended up doing ultimately, but I'm still kind of interested how I could have accomplished what I was trying to do orginally

&gt;  I suppose, Pulumi does not have an equivalent?
Yeah, unless I missed it from what I could tell there were flags/behaviors I could set to cause when a resource would be force deleted but not when a specific property change should be ignored.

<@U03M5L2EMAM> it does have the equivalent

Great, then that's probably the right solution. :slightly_smiling_face:

<@UCWG26BH7> Do you have a reference on how that works?

<https://www.pulumi.com/docs/intro/concepts/resources/options/ignorechanges/>

<https://github.com/search?q=repo%3Apulumi%2Fexamples%20ignoreChanges&amp;type=code>