This message was deleted.

It seems that an error during the pulumi down operation just causes pulumi to assume everything is probably gone and remove it from the state?

I do not understand that behaviour? That's really annoying?

It should not! We save each delete operation to state before doing it and only clear the resource from state when the operation is successful. The only thing I can think of is maybe a bug with

--exclude-protected

, can you raise an issue about this with what resources got lost? Might help to see exactly what went missing.

I hope it is a bug, because this could be a showstopper for me! I'll create a ticket!

It's definitely not intended behaviour. The state system does a load of extra work compared to most IAC state systems to not loose track of resources.

Happy to hear that shouldn't happen. Created a bug: https://github.com/pulumi/pulumi/issues/14416

pulumi's ability to cleanup resources in aws is really terrible right now. it is basically broken for eks.

Haven't had any issues with EKS actually. It's more all the EC2 networking stuff that has been a pain.

yeah I am blocked by this now. the timing is annoying.