The authentication API is going to become the backbone for when I start making the Pulumi provider for them.

Do you plan on releasing an OpenAPI specification for your api? There is a lot of ambient interest in a pulumi provider (or provider generator) for an arbitrary openAPI spec file

There is a lot of ambient interest in a pulumi provider (or provider generator) for an arbitrary openAPI spec file

There is an existing (community) provider generator for an openapi spec: https://github.com/cloudy-sky-software/pulschema

Thank you for the ping, @red-match-15116! ❤️

pulschema

is a great place to start. If you have questions, please feel free to reach out! I will warn you that based on the quality of the OpenAPI spec you are converting, you may have some work cleaning up some mess. In particular, if the API doesn't follow a RESTful resource model, you are likely not going to have much success and would have to resort to rolling your own native provider, much like Pulumi's own native providers for GCP and AWS native providers.

That is absolutely beautiful 😍 I'm on a mission to create providers for azure data explorer and Cribl stream; I will def check this out. Thanks!

@clever-sunset-76585 so we should use the OpenAI spec or make our own?

If you want that level of interoperability, then a well-defined OpenAPI 3.0 spec will be very valuable

Okay I don't know a lot about OpenAPI is there any docs about it that I could read please to get up to speed.

Start here 🙂 https://swagger.io/docs/specification/about/

Thanks!!