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

I have a bunch of resources that I want to reparent underneath a new `ComponentResource`  to logically group them. However, when I run a preview, the provider wants to delete and create all these resources, even though nothing has changed besides the structure of my code. Am I doing something wrong? Or is there a way to work around this?

I can refactor things, but leave the `{ parent: this }` on the resource options out ... this means that the dependency isn't established which kind of defeats the point. I'm not sure why simply establishing the dependency on a logical component grouping would cause the engine to want to delete the existing resources

This seems like weird behavior, nothing else depends on my new component group, it's just a logical grouping for the benefit of clarity.

need to set an alias: <https://www.pulumi.com/blog/cumundi-guest-post/>

they go over that scenario in the blog post:
```const serviceAccountSecondCustomerKey = new gcp.serviceAccount.Key("ServiceAccountSecondCustomerKey",
    {
        serviceAccountId: serviceAccountSecondCustomer.email
    },
    {
        parent: serviceAccountSecondCustomer,
        aliases: [
            { parent: pulumi.rootStackResource }
        ]
    }
);```

awesome!! thank you, that's so helpful, much appreciated