https://pulumi.com
Join Slack
This message was deleted.
# typescript
s
This message was deleted.
l
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.
👍 1
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.
c
In Terraform it is easily solved with:
Copy code
lifecycle {
    ignore_changes = [ ami ]
  }
I suppose, Pulumi does not have an equivalent? 🤔
r
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
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.
b
@cuddly-magician-97620 it does have the equivalent
c
Great, then that's probably the right solution. 🙂
r
@billowy-army-68599 Do you have a reference on how that works?
b
r
Excellent, thanks!
Open in Slack
PreviousNext
Powered by

Pulumi Community

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.

Powered by