Channels
#getting-started
Title
a
alert-nightfall-64120
08/27/2023, 6:53 AMDoes Pulumi have the concept of a private registry? I figure with the fact you are a cloud offering- providing your organization a private registry that you can publish custom component providers to just makes complete sense to do.
The documentation flow for completely private component providers (private registry, binaries, etc.) is non-existent from everything I have seen. Anyone find anything on this?
e.g. is there a way to view API Docs for in-house private providers?
s
salmon-account-74572
08/28/2023, 2:38 PMWe 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.
o
orange-policeman-59119
08/28/2023, 4:01 PMCertainly something we're interested in; could you elaborate on your use case or DM me?
a
alert-nightfall-64120
08/29/2023, 1:14 AMI sent @orange-policeman-59119 a DM.
What are the acceptable server URL formats for:
Copy code
pulumi plugin install --servero
orange-policeman-59119
08/29/2023, 1:29 AMIt 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><https://example.com/pulumi-${kind}-${name}-v${version}-${os}-${arch}.tar.gz><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>