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

Generally you won't need to worry about URNs. You can bulk import resources to a new stack:
<https://www.pulumi.com/docs/guides/adopting/import/#bulk-import-operations>
Then just `pulumi state delete` all those resources.

You may also consider moving resources from index.ts to ComponentResources, but that can happen later.

Screen Shot 2021-10-06 at 2.11.00 PM.png

I think, my problem with import &amp; delete is this :point_down:  (note the number of lines)
It’s not really feasible to move all those things one by one. I wish I could do `state delete` / `import` only on top level resources and expect it to be applied to all children, but pulumi doesn’t work this way for some reason..

Would you be able to do the reverse? Move / rename the stack so that most resources move to the right place, then move the minority back to the original stack?

While bulk importing is easy enough, the only way to do a bulk state delete is to export the stack, remove the relevant resources, and re-import the stack. This is obviously a higher-risk solution.

Of course, you could script the state delete... It'll take longer to write the script them update the state one resource at a time, but it'll be less boring and safer :slightly_smiling_face:

Yeah, I think scripting the whole process is what I’m going to do… I hope, it will eventually be possible to perform operations like this using the pulumi CLI itself :slightly_smiling_face: