In the docs, this is what is described:

Why would you make a component resource instead of just a “simple” logical grouping that you can call and use like a generic library full of classes and functions? A component resource shows up in the Pulumi ecosystem just like any other resource. That means it has a trackable state, appears in diffs, and has a name field you can reference that refers to the entire grouping.

However, all three things don’t seem all that meaningful: 1. trackable state - in this thread on github, a pulumi contributor says “but state for component resources is basically meaningless anyway” 2. appears in diffs - if state on a component resource is meaningless, then so is any diff 3. a name field you can use to reference the entire grouping - you can also do this if you have a root component in the hierarchy you create inside a function via

parent

docs - https://www.pulumi.com/learn/abstraction-encapsulation/component-resources/ github issue - https://github.com/pulumi/pulumi/issues/2653#issuecomment-484956028

I’m trying to implement this but struggling with the typescript errors to be used like

this.addResource('role', aws.iam.Role, { … })

private addResource<T extends pulumi.Resource>(
    name: string,
    Resource: T,
    args: ConstructorParameters<T>[1]
  ) {
    return new Resource(`${this.name}-${name}`, args, { parent: this })
  }

got it kind of working but

Resource

is very loosely typed, could probably fix it if I new how to use

infer

correctly

private addResource<T extends new (...args: any) => any>(
    name: string,
    Resource: T,
    args: ConstructorParameters<T>[1]
  ) {
    return new Resource(`${this.name}-${name}`, args, { parent: this })
  }