Orquesta workflow API documentor to Swagger OAS definition?

I’m looking to created standardized OAS v2 or v3 YAML to give to consumers of my workflows, such that they can import them into Insomnia, Postman, or other API client tools, or even just visualize in SwaggerHub.

I know I can get a JSON blob of a particular action by going through the API endpoint using an api key or token, but that isn’t quite sufficient for what I’m looking for.

I see that there is an OpenAPI generator for the main ST2 api created during the build process.

Has anyone successfully adapted it to do “documentation-by-code” or something similar that I can feed it my Orquesta actions and it will make a nice little OAS YAML file?

I’m not 100% sure what you’re asking for, and I’m not familiar with OAS, so I don’t know if I will be of any help.

AFAIK, Orquesta itself doesn’t have an HTTP API. ST2 has an HTTP API, as you’ve found:

Are you trying to get an OAS YAML API description of ST2 actions for a particular pack?

Yes, more specifically I’m seeking if anyone has already written a tool that scans your Orquesta workflow YAML to identify the input parameters and the output schema to create an OpenAPI compliant definition. I know that ST2’s built in API allows a JSON formatted version of this, but it’s not compatible with OpenAPI without conversion of some kind. Thought I’d ask before I go about writing one.