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

Do you have examples of these? AFAIK the CLI uses ARM for the most part

exactly! I found this as a proposed best practice

<https://github.com/pulumi/pulumi/issues/99>

Example: You create a webapp in Azure ARM. To connect it via source_control to a repository you _must_ use Azure CLI, no way around it. It's true! I have tried many times the source_control property from Azure ARM to no avail. It is Azure CLI moment to shine.

<https://docs.microsoft.com/en-us/cli/azure/webapp/deployment/source>

<https://github.com/Azure/azure-cli/blob/3635c161c36d240b57af95c79b043eeb3969e566/src/command_modules/azure-cli-appservice/azure/cli/command_modules/appservice/custom.py#L1016-L1078>

So I guess this _could_ be automated with a CustomResource if you want to maintain the resource semantics

There’s references in that code to a VSTS Provider for _something_ - I think this is because azure devops has provenance from a non-azure team and it has a completely separate API and directory… I wonder if it would be suited to its own provider actually (which is also something I could use!)

hey, <@UB8A66MPS> let's say I make a customComponent like this <https://pulumi.io/reference/component-tutorial.html> for the Azure elements I find lacking in AzureARM.

How would I go about contributing to the community? Have you got any suggestion or references? Sorry for bothering!

That’s a good question: the simplest option is to publish an npm package with them in. If you want them to land in an official repo, they could either go into some future `azurex`, or as overlays into the azure provider