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

Yes. Once the `up` errors, you can export the stack. Down near the bottom will be the deleted resources, which will have the "delete" attribute with value "true". Delete all those resources and import. Pulumi will forget about them.

For my own interest, what resource creates tables in RDS?

I think you can create a single table with the RDSInstance class. But otherwise I’m using a provider.

I exported the stack but I started deleting via <https://www.pulumi.com/docs/reference/cli/pulumi_state_delete/> . It wasn’t that clear what to remove from the exported file.

Not sure that you can work with the internals of RDS instances using the rds package.. how would it know if it's SQL server, postgres, etc.?

`state delete` will remove resources that aren't currently "being deleted".. once they're in that state, Pulumi thinks they're already deleted and `state delete` doesn't work on them. I was trying that just an hour ago :slightly_smiling_face:

`state delete` is good for making Pulumi forget about resources.. it's for "unmanaging" them.

It won't delete the resources though. It just removes them from the state.

I think that’s what I needed, to unmanage them. They were already non-existant