This message was deleted.

sparse-intern-71089

02/19/2024, 5:01 AM

This message was deleted.

little-cartoon-10569

02/19/2024, 5:17 AM

If the AMI no longer exists, then do you really want to try/catch the error? Don't you want to update the AMI to something that does exist?

gorgeous-keyboard-22299

02/20/2024, 4:57 AM

@little-cartoon-10569 - updating the AMI would completely destroy my staging or production EC2s, so definitely NOT! The better solution can be found @ https://app.slack.com/client/T85C88L30/CRH5ENVDX Thanks for your response. -- L

little-cartoon-10569

02/20/2024, 7:38 PM

That link doesn't work for me.

salmon-account-74572

02/20/2024, 8:15 PM

You could do an

ignoreChanges

on the AMI property of the EC2 instance: https://www.pulumi.com/docs/concepts/options/ignorechanges/ This would let you get past the missing AMI error (for now), but it’s still something you’ll need to address at some point.

little-cartoon-10569

02/20/2024, 8:28 PM

And you could avoid getAmi, and just hard-code the AMI id.

salmon-account-74572

02/20/2024, 9:22 PM

Or provide the AMI ID as a configuration value to the stack. 🙂

2 Views

Open in Slack

Previous Next

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.