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 use it mainly when bundling resources in a `CustomResource` subclass. The `parent` relationship is visualized in the Resource Viewer on the Pulumi hosted platform (<http://app.pulumi.com|app.pulumi.com>)

The parent also affects the resolution of which provider to use for its children resources

I used it for bundling resources, but I noticed dependency track does not seem to work properly when using them.

when dependencies are wrong I noticed a myriad of problems that derive from this, ultimately including broken stacks.

I see if I can create a minimal example that reproduces what I am experiencing

Hum, never had any problems like that. I used `parent` multiple times across multiple resources, mostly to put thing under custom `ComponentResource`s that define providers. Keeps things organized in the code, the resource viewer and reuses code without having to pass multiple providers everywhere.
Essentially I do this:
```export class ProjectDefinition extends pulumi.ComponentResource {
  constructor(name, args, opts) {
    /// Instantiate the provider
    const provider = ...
    super('custom:utils:projectDefinition', name, args, {...opts, provider})
  }
}```

yes, thats what I do, but the problem is when I have a CustomResource A and then another CustomResource B that depends on A. In some situation B is being populated before A has completed, leading to errors.