Azure / Azure/azure-functions-dotnet-worker
OpenAPI roadmap
- Dominant language
- C#
- Stars
- 466
- Forks
- 215
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 7
Description
I'm trying to resolve the confusion around OpenAPI support for Isolated Worker SDK.
There are several [opened issues](https://github.com/Azure/azure-functions-dotnet-worker/issues?q=is%3Aissue+is%3Aopen+openapi) on the topic. There's an Azure org repository with support for Swagger as an extension (https://github.com/Azure/azure-functions-openapi-extension). And there's an official document (https://learn.microsoft.com/en-us/azure/azure-functions/openapi-apim-integrate-visual-studio) which states the following:
> The OpenAPI and API Management integration featured in this article is currently only supported for [in-process](https://learn.microsoft.com/en-us/azure/azure-functions/functions-dotnet-class-library) C# class library functions. [Isolated worker process](https://learn.microsoft.com/en-us/azure/azure-functions/dotnet-isolated-process-guide) C# class library functions and all other language runtimes should instead **[use Azure API Management integration from the portal](https://learn.microsoft.com/en-us/azure/azure-functions/functions-openapi-definition)**.
So what's the roadmap for the Isolated Worker SDK, a code-based support via extension or the portal with APIM integration?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.