https://pulumi.com logo
#aws
Title
# aws
f

fast-river-57630

08/01/2022, 7:55 PM
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
2 Views