CLI tool as a .NET Tool

[alanta]

For API Management integration, we generate OpenAPI specs at build time and push these specs to APIM during deployment.
This works very well with the CI/CD paradigm, much more so than manually importing the spec into APIM as suggested in the APIM integration article.

For WebAPI projects we use the Swashbuckle CLI tool which is a .net core tool and can be installed easily into an Azure DevOps pipeline agent. I'd love to have a similar solution using the CLI tool from this project for Azure Functions.

Is that in the plans? I'm willing to pitch in if that helps.

[filcole]

This looks like a duplicate of #58 .

[justinyoo]

@alanta Thanks for the suggestion! We DO have a CLI version of it, but it's very early stage, even in this preview.

[justinyoo]

Related to: aliencube/AzureFunctions.Extensions#132

[justinyoo]

Related to: aliencube/AzureFunctions.Extensions#126

[justinyoo]

As the PR, #489, has been merged, you can generate the OpenAPI doc on-the-fly, within the GitHub Actions workflow.