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

Hey <@UK4HNFLCB>,

At this time, the provider generation code is closed source - if you want to build something native, you can look at the pulumi-kubernetes library as that also generates code from an open api spec - the azure provider works from a slightly different angle at this time

I think there was an idea to create a model provider purely driven by an Open API spec. Both k8s and Azure have a ton of stuff specific to those providers.

And so will the XenAPI provider probably. There is a single JSON file which is applicable to all versions of the XenAPI, documenting when fields and operations came into existance or where phased out. See the `lifecycle` section in the `xenapi.json`. This is also an XML-RPC based API where I also have to get the authentication in place. I’m not there yet, but starting from the spec would also give me a 100% coverage at day 1 (give or take some bugs in the generation :zany_face:).