Azure / Azure/azure-functions-openapi-extension
Possible Feature Request: Ability to select which version operations in the Function are mapped to
- Dominant language
- C#
- Stars
- 388
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I would like to request the ability to select which version an operation belongs to without having to specify the version in the route. Similar to the `MapToApiVersion` and `ApiVersion` in Web API projects.
I currently make use of `tags` in the `OpenApiOperation` attribute to separate the OpenApi documentation by version when generating the docs using the CLI in this repo. I then publish these documentations in a Azure Pipeline to a Azure API Management Service Instance. However, once the docs are published to APIM, the version is duplicated in the URL path.
I am not sure if this is possible with the current release package but would help publish Functions to APIM.
Thanks for your consideration.
Contributor guide
Research direction
Review the existing OpenApiOperation tag handling and the CLI documentation-generation flow, then compare the requested behavior with MapToApiVersion and ApiVersion in Web API projects. Done means operations can be assigned to a selected version without adding that version to the route, and generated documentation can be published to Azure API Management without duplicating the URL path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, openapi
- Domain
- api, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100