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

Hello all, I have a question about Pulumi components. Is it possible for me to easily distribute them via a private pypi? Can I just define a `pulumi.CommponentResource` suclasclass, publish that code privately, and import it without needing to use e.g. `PulumiPlugin.yaml` and the associated rigmarole?

To answer my own question, it seems like yes this is a supported workflow <https://www.pulumi.com/docs/iac/get-started/aws/create-component/|https://www.pulumi.com/docs/iac/get-started/aws/create-component/>

Yes, for sure. The tradeoff to be aware of is that you cannot consume them from other Pulumi languages if you distribute via PyPI.

In this case, we're a pure python shop with an internal registry so this suits us down to the ground :relaxed:

Anywhere we could do better to make this use case easier to find in the docs? I'm thinking we should have a guide like "Selecting Packaging for Components" or something like that

I think yes, either a separate page or else a subsection under the docs here for ‘Component Resources’ https://www.pulumi.com/docs/iac/concepts/components/