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

no, you’d create a component that includes resources from the provider, not the other way around

a provider talks directly to an API. A component is a grouping of resources

I was hoping to make a single distributable (provider?) where Component A creates (groups?) Resource B and Resource C.

But looks like I need to put Resource B and Resource C into their own resource provider, then put Component A into its own component provider and distribute both to users.

Still learning the ropes!

Right now, the best way is to distribute a custom provider with the raw resources, and a component provider for the components. This is a <https://github.com/pulumi/pulumi-go-provider/issues/18|know problem> and we are actively working on improving the situation.

<@UCWG26BH7> I think that <@U04FXSF8KNH> was discussing creating a provider that serves both custom resources and component resources, which should be possible (and is done in the example they referenced).

Thanks <@U02GSM8UU1H> I’ll watch that issue