MayankBargali-MSFT
commented
2 years ago @scobie-optimizely Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
Open scobie-optimizely opened 2 years ago
MayankBargali-MSFT
commented
2 years ago @scobie-optimizely Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
kkazala
commented
2 weeks ago Could you also look at the sample Create serverless APIs in Visual Studio using Azure Functions and API Management integration/Update the function code for Isolated model?
It's referencing Microsoft.Azure.WebJobs.Extensions.OpenApi.Core.Attributes and Microsoft.Azure.WebJobs.Extensions.OpenApi.Core.Enums.
The Migrate .NET apps from the in-process model to the isolated worker model on the other hand says: "Your isolated worker model application should not reference any packages in the Microsoft.Azure.WebJobs.* namespaces or Microsoft.Azure.Functions.Extensions. If you have any remaining references to these, they should be removed."
It's below the table with Package references, between the two "Tip" fields
The information on adding an OpenAPI interface to Azure functions, in the portal, is wrong. The part about using API Management, importing functions, supposedly downloading the API json file... isn't there at all. And besides all this, it doesn't work when publishing an Azure Function from Visual Studio. It's not clear how to get it to work... to publish a .NET 6 (isolated proc) Azure Function from Visual Studio, with OpenAPI. Updating the API always fails. It requires some sort of manual steps... but then this doc page isn't even correct.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.