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

as far as I understand, if you modify the state *manually* (remove some resources), they are not managed anymore by pulumi (regardless of the fact whether they still exist or not)

but the resources weren't removed when I looked into the pulumi console

just to make sure, you:
• exported the stack to JSON
• removed some resources manually from JSON
• removed these resources from the cloud
• import the modified JSON file

multiple times now, since it didn't remove my resources

I had to add some hardcoded resource IDs and run pulumi up a few times, to get things in the correct oder

by `multiple times now, since it didn't remove my resources` you mean from the pulumi console?

I deployed a resource, but because of a bug, it was missing some inputs that I needed to delete it anymore

then I exported the stack and tried to remove the resource from the pulumi stack

then I imported the stack again, but the import command said, no resources are affected

and in the pulumi console, the resources were still in the stack

then I rewrote my dynamic resource provider, so it had the missing inputs hardcoded

ran pulumi up every time I changed the hardcoded values for the next resource to delete etc.

now the resources are gone from my stack, but I'm still confused why I couldn't delete it with an export/import