title | description | services | documentationcenter | author | manager | editor | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.custom | ms.topic | ms.date | ms.author |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Use revisions to make non-breaking changes safely in Azure API Management | Microsoft Docs |
Follow the steps of this tutorial to learn how to make non-breaking changes using revisions in API Management. |
api-management |
vladvino |
cfowler |
api-management |
mobile |
na |
na |
mvc |
tutorial |
06/15/2018 |
apimpm |
When your API is ready to go and starts to be used by developers, you eventually need to make changes to that API and at the same time not disrupt callers of your API. It's also useful to let developers know about the changes you made. We can do this in Azure API Management using revisions. For more information, see Versions & revisions and API Versioning with Azure API Management.
In this tutorial, you learn how to:
[!div class="checklist"]
- Add a new revision
- Make non-breaking changes to your revision
- Make your revision current and add a change log entry
- Browse the developer portal to see changes and change log
- Complete the following quickstart: Create an Azure API Management instance.
- Also, complete the following tutorial: Import and publish your first API.
-
Select APIs page.
-
Select Demo Conference API from the API list (or other API to which you want to add revisions).
-
Click the Revisions tab from the menu near the top of the page.
-
Select + Add Revision
[!TIP] You can also choose Add Revision in the context menu (...) of the API.
-
Provide a description for your new revision, to help remember what it will be used for.
-
Select Create
-
Your new revision is now created.
[!NOTE] Your original API remains in Revision 1. This is the revision your users continue to call, until you choose to make a different revision current.
-
Select Demo Conference API from the API list.
-
Select the Design tab near the top of the screen.
-
Notice that the revision selector (directly above the design tab) shows Revision 2 as currently selected.
[!TIP] Use the revision selector to switch between revisions that you wish to work on.
-
Select + Add Operation.
-
Set your new operation to be POST, and the Name, Display Name and URL of the operation as test.
-
Save your new operation.
-
We have now made a change to Revision 2. Use the Revision Selector near the top of the page to switch back to Revision 1.
-
Notice that your new operation does not appear in Revision 1.
-
Select the Revisions tab from the menu near the top of the page.
-
Open the context menu (...) for Revision 2.
-
Select Make Current.
-
Check Post to Public Change log for this API, if you want to post notes about this change. Provide a description for your change that developers see, for example: Testing revisions. Added new "test" operation.
-
Revision 2 is now current.
-
In the Azure portal, select APIs.
-
Select Developer Portal from the top menu.
-
Select APIs, and then select Demo Conference API.
-
Notice your new test operation is now available.
-
Select API Change History from below the API name.
-
Notice that your change log entry appears in this list.
In this tutorial, you learned how to:
[!div class="checklist"]
- Add a new revision
- Make non-breaking changes to your revision
- Make your revision current and add a change log entry
- Browse the developer portal to see changes and change log
Advance to the next tutorial:
[!div class="nextstepaction"] Publish multiple versions of your API