We’ve definitely talked about providing an OpenAPI spec at some point and it’s good to know it’d be useful. Right now, we don’t have an eta on when that would be available though.
Here’s an initial draft of an OpenAPI spec. The actual swagger 2.0 json file is here. If needed, you can convert it to OpenAPI 3.0 using the swagger converter.
I tried generating a client using autorest but it did not like the enum definition with duplicate entries. I was able to fix it manually. Having a 3.0 spec available via URL would be nice to feed it directly into the tooling and maybe even run CI notifications if the spec changes.
Is there an alternative way of formatting to accomplish this? (I basically want to dynamically write out a file onto the machine and first thought on quick&dirty approach was to use >)