Would it be possible to have a video that digs deeper into the OpenApi attributes used within Azure Functions, also some guidance on applying attributes to models?
This is great.. how can we get the OpenAPI to produce the Swagger file and add it to our source code. In our scenario we are using authentication for the functionApp which is blocking access to the swagger url when we are automating our import of the APIM APIs.
HI Justin, do we use Function-App or OpenApi option in APIM to add the API/Az-function. The issue is if i use openAPI and add api using the Swagger.json file, i can see the service contracts, request header etc. But if i use the function-app option, i don't see any data-annotations that are added to the function app, like Parameter, Response etc....
Hi Shashank, Both importing the swagger.json file generated by the Function App or deploying to Azure API Management directly from Visual Studio is valid and a choice to be made on your exact scenario. With that said, all of the OpenAPI metadata added via the attribute classes should carry over to Azure API Management when you deploy from Visual Studio. Please file an issue with us on the OpenAPI Extension GitHub repo here; msft.it/6058ZLcbm so we can take a closer look.
@@MicrosoftAzure I tried deploying using swagger.json from APIM Azure portal and all Metadata is uploaded. Also tried Uploading directly to APIM from VS code. That works as well. Only thing that doesn't work I'd if I Add Api using Function App option on APIM portal. Will file an issue on Github. Thanks for your response 👍
Thanks Justin. Very glad that your package which helped me a lot in my current project now is official Microsoft package!
Wov awesome features, thanks for the great video. Thanks Justin and Scott, it really helped me in learning all these features so quick.
We're happy to hear that you enjoyed the video, and that you found it so helpful! 💙
Would it be possible to have a video that digs deeper into the OpenApi attributes used within Azure Functions, also some guidance on applying attributes to models?
I loved this feature. I didn't knew it was there in the first place.
Can we use Visual Studio 2019?
This is great.. how can we get the OpenAPI to produce the Swagger file and add it to our source code. In our scenario we are using authentication for the functionApp which is blocking access to the swagger url when we are automating our import of the APIM APIs.
Impressive stuff
HI Justin, do we use Function-App or OpenApi option in APIM to add the API/Az-function. The issue is if i use openAPI and add api using the Swagger.json file, i can see the service contracts, request header etc. But if i use the function-app option, i don't see any data-annotations that are added to the function app, like Parameter, Response etc....
Hi Shashank,
Both importing the swagger.json file generated by the Function App or deploying to Azure API Management directly from Visual Studio is valid and a choice to be made on your exact scenario. With that said, all of the OpenAPI metadata added via the attribute classes should carry over to Azure API Management when you deploy from Visual Studio. Please file an issue with us on the OpenAPI Extension GitHub repo here; msft.it/6058ZLcbm so we can take a closer look.
@@MicrosoftAzure I tried deploying using swagger.json from APIM Azure portal and all Metadata is uploaded.
Also tried Uploading directly to APIM from VS code. That works as well.
Only thing that doesn't work I'd if I Add Api using Function App option on APIM portal.
Will file an issue on Github.
Thanks for your response 👍
Awesome!!!
Only thing is, does anyone deploy like this without vnet, subnet, private endpoint, and oauth ? This may be fine for some quick setup during dev.
What are the costs?