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

e.g. is there a way to view API Docs for in-house private providers?

We don’t yet have anything in the “private registry” space. For in-house private providers, you’d currently have to host/generate the API docs yourself in some fashion.

Certainly something we're interested in; could you elaborate on your use case or DM me?

I sent <@UFPFMDBTK> a DM.

What are the acceptable server URL formats for:
```pulumi plugin install --server```
?

The documentation simply states: A URL to download plugins from
Can I provide an authenticated URL?

It accepts HTTPS or a Github scheme URL (which should work with GitHub Enterprise) to download from a GitHub Release. Let me check the format.

<https://www.pulumi.com/docs/using-pulumi/pulumi-packages/how-to-author/#publish-your-package>

When provided with `--server <https://example.com>`, the URL searched is:

`<https://example.com/pulumi-${kind}-${name}-v${version}-${os}-${arch}.tar.gz>`

e.g.:

`<https://example.com/pulumi-resource-foo-v1.2.3-linux-amd64.tar.gz>`

As for authentication, I'm not sure; I don't think we have a test with basic auth (`<https://foo:bar@example.com>`) if the options there don't meet your internal needs, open an issue on the main Pulumi repository!