Azure / azure-functions-dotnet-worker

Azure Functions out-of-process .NET language worker
MIT License
419 stars 184 forks source link

OpenAPI roadmap #1569

Open SeanFeldman opened 1 year ago

SeanFeldman commented 1 year ago

I'm trying to resolve the confusion around OpenAPI support for Isolated Worker SDK. There are several opened issues 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 C# class library functions. Isolated worker process C# class library functions and all other language runtimes should instead use Azure API Management integration from the portal.

So what's the roadmap for the Isolated Worker SDK, a code-based support via extension or the portal with APIM integration?

jviau commented 1 year ago

@brettsam / @fabiocav / @satvu - would this be covered by the aspnetcore integration work?

thushanperera95 commented 1 year ago

I would also like to know what's happening in this space. The extension appears to no longer work with the aspnetcore integration in place.