4
votes

Given that Azure Functions can be imported to API Management as described here, how do we keep the API up to date when Azure Functions change? For example, if the Function signature changes or a function is added or removed. How can this process be automated, so once the Azure Functions change, the changes are reflected in the API?

Microsoft's API Management team has a proposed solution here, but it's not clear to me how this solution can be applied with Azure Function App as the backed-end for the API.

2
So I can improve the question, when you downvote, please provide feedback as to why.dev.e.loper

2 Answers

1
votes

Yes, you need to make it as part of your release process. After publishing the new version of Azure Functions, you'll import the new specification into API Management.

https://marketplace.visualstudio.com/items?itemName=stephane-eyskens.apim

1
votes

Once you import and publish an API in APIM it will not be updated automatically. So, even though the developers released a new build, the consumers would still consume the older version of the API published in APIM.

Try to use Azure DevOps pipelines for continuous delivery of APIs to Azure API Management Service.

Add a create/update task, which will create or update the API in APIM based on the Swagger file and also set different API policies. This task will also update the API in APIM in case the Dev guy will create new API methods or remove API methods.