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

No, unfortunately not. No changes :confused:

Actually looking at that error I wonder if resource has hooked onto that security group which isn't being managed by Pulumi (or for which Pulumi has not dependency tracked correctly). Might have to go check in your cloud console to track that down, if it out to be a resource that pulumi knew about ping back here we should work out why it didn't get dep tracked.

The root cause is probably mixing 2.x with 3.x pulumi cli. A 2.x cli failed, which ended up in this state.
I solved it now, by removing the resources manually. Feels a bit dirty though.