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 expected retainOnDelete to keep my EC2 Instance running and just spawn i new one when my AMI caused a replace.

Should I have run 'pulumi state delete' on the EC2 instance first to keep the old instance around?

I'm on pulumi 3.36.0 so I will go ahead and upgrade to 3.37.2 but not try again without confirmation from someone here

yeah i cant state delete due to relationships on DNS  entries.

OK yeah retainOnDelete worked when I didn't use "--target URN". WHYYY