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

This is <https://github.com/pulumi/pulumi/issues/458> and we have a WIP solution for this in <https://github.com/pulumi/pulumi/pull/2404>.  Landing this is very important for allowing this sort of flexible refactoring without risk of impact on production infrastructure.  Feedback on the proposal in that issue would be appreciated.

If you do need to work around this in the meantime, you can technically do so by hand editing the checkpoint (`pulumi stack export &gt; stack.son`, edit, `pulumi stack import &lt; stack.json`) to change the names of existing resources to the new names that will be used as part of our new components.  This of course isn't a scalable solution, hence the issue and PR above, but could unblock if needed before that lands.

Ahh I see. I think adjusting the parent in the stack file should suffice for now. It is a bit tedious but should get the job done. Looking forward to `0.22.x` / `0.23.x` though :wink: Thanks for you quick and exhaustive reply, <@UB3BGTV63>! (As always)