Azure Api Management Automated Revisions

Azure API Management is designed to be an internet face for your API. The main reason that I started using it is the build-in trottling engine that should protect my API from unexpected workloads. But Azure API Management can do more. It tries to solve API versioning problems by introducing “Versions” and “Revisions”. The difference between those two is that “Version” is something that user decides to use by specifying URL part like “/v1” or “/v2” and “Revision” is the new version of particular version. By default API users are using the revision which developers forses them to use. Revisions is a good abstraction to use where you as a developer need to fix something in released API or introduce non-breaking changes. Here is my solution of how to automate new Azure API Management revisions delivery using powershell = your favorite CD tool:


comments powered by Disqus