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 <@UL49Z5Q12>, every Pulumi plugin is centered around the Pulumi schema. This describes the available configuration options each resource has, which type it should be, etc. Our YAML engine reads this schema to find out if the given properties are correct.

Assuming my components are private and not on the Pulumi registry, then I’d need to 

pulumi plugin install —server

To install my component package from my GitHub release 

Is that correct ?

In the Pulumi Schema, you can configure the download URL for your plugin binary. Since v3.35.3, we have explicit github support (which uses the Github API). If you have a `GITHUB_TOKEN` configured as an env variable, a Github release from a private repo should work automatically.
<https://www.pulumi.com/docs/guides/pulumi-packages/how-to-author/#support-for-github-releases>

<@UK4HNFLCB> I'm not sure I understand how you let a blank (new) Pulumi project know about our Component Package

You mentioned that everything is in the schema, but how would a new Pulumi project know about this schema ?
Surely we'd have to download/install something first, correct ?

<@UL49Z5Q12> we lack documentation for this on our website, but for the YAML engine, you have to repeat the download url in your YAML setup. Here is a small example:
<https://github.com/pulumi/pulumi-yaml/blob/60bfab81632daf5cb945e04b57412dc135fed4d8/pkg/pulumiyaml/testing/test/testdata/aws-resource-options-multiple-providers.pp/yaml/aws-resource-options-multiple-providers.yaml#L26-L29|https://github.com/pulumi/pulumi-yaml/blob/60bfab81632daf5cb945e04b57412dc135fed4d[…]-providers.pp/yaml/aws-resource-options-multiple-providers.yaml>