Skip to content

Commit 86abe9c

Browse files
author
Jill Grant
authored
Merge pull request #282901 from dlepow/tutrev
[APIM] Update revisions tutorial
2 parents d1cd0de + e54138e commit 86abe9c

File tree

6 files changed

+39
-19
lines changed

6 files changed

+39
-19
lines changed

articles/api-management/api-management-get-started-revise-api.md

Lines changed: 39 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,37 @@
11
---
2-
title: Tutorial - Use revisions in API Management to make non-breaking API changes safely
2+
title: Tutorial - Use revisions in API Management for safe nonbreaking API changes
33
titleSuffix: Azure API Management
4-
description: Follow the steps of this tutorial to learn how to make non-breaking changes using revisions in API Management.
4+
description: Follow the steps of this tutorial to learn how to make nonbreaking API changes using revisions in Azure API Management.
55
services: api-management
66
author: dlepow
7-
ms.service: api-management
7+
ms.service: azure-api-management
88
ms.custom: mvc, devx-track-azurecli, devdivchpfy22
99
ms.topic: tutorial
10-
ms.date: 03/30/2022
10+
ms.date: 07/31/2024
1111
ms.author: danlep
1212

1313
---
1414

15-
# Tutorial: Use revisions to make non-breaking API changes safely
15+
# Tutorial: Use revisions to make nonbreaking API changes safely
1616

1717
[!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
1818

1919
When your API is ready to go and is 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.
2020

21-
In Azure API Management, use *revisions* to make non-breaking API changes so you can model and test changes safely. When ready, you can make a revision current and replace your current API.
21+
In Azure API Management, use *revisions* to make nonbreaking API changes so you can model and test changes safely. When ready, you can make a revision current and replace your current API.
2222

23-
For background, see [Versions & revisions](https://azure.microsoft.com/blog/versions-revisions/) and [API Versioning with Azure API Management](https://azure.microsoft.com/blog/api-versioning-with-azure-api-management/).
23+
For background, see [Versions](api-management-versions.md) and [Revisions](api-management-revisions.md).
2424

2525
In this tutorial, you learn how to:
2626

2727
> [!div class="checklist"]
2828
> * Add a new revision
29-
> * Make non-breaking changes to your revision
29+
> * Make nonbreaking changes to your revision
3030
> * Make your revision current and add a change log entry
3131
> * Browse the developer portal to see changes and change log
32+
> * Access an API revision
3233
33-
:::image type="content" source="media/api-management-getstarted-revise-api/azure-portal.png" alt-text="API revisions in the Azure portal":::
34+
:::image type="content" source="media/api-management-getstarted-revise-api/azure-portal.png" alt-text="Screenshot of API revisions in the Azure portal." lightbox="media/api-management-getstarted-revise-api/azure-portal.png":::
3435

3536
## Prerequisites
3637

@@ -41,24 +42,24 @@ In this tutorial, you learn how to:
4142
## Add a new revision
4243

4344
1. Sign in to the [Azure portal](https://portal.azure.com), and go to your API Management instance.
44-
1. Select **APIs**.
45+
1. In the left menu, under **APIs**, select **APIs**.
4546
2. Select **Demo Conference API** from the API list (or another API to which you want to add revisions).
4647
3. Select the **Revisions** tab.
4748
4. Select **+ Add revision**.
4849

49-
:::image type="content" source="media/api-management-getstarted-revise-api/07-add-revisions-01-add-new-revision.png" alt-text="Add API revision":::
50+
:::image type="content" source="media/api-management-getstarted-revise-api/07-add-revisions-01-add-new-revision.png" alt-text="Screenshot of adding an API revision in the portal.":::
5051

5152
> [!TIP]
5253
> You can also select **Add revision** in the context menu (**...**) of the API.
5354
54-
5. Provide a description for your new revision, to help remember what it'll be used for.
55+
5. Provide a description for your new revision, to help remember what it is used for.
5556
6. Select **Create**.
5657
7. Your new revision is now created.
5758

5859
> [!NOTE]
5960
> 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.
6061
61-
## Make non-breaking changes to your revision
62+
## Make nonbreaking changes to your revision
6263

6364
1. Select **Demo Conference API** from the API list.
6465
1. Select the **Design** tab near the top of the screen.
@@ -67,10 +68,10 @@ In this tutorial, you learn how to:
6768
> [!TIP]
6869
> Use the revision selector to switch between revisions that you wish to work on.
6970
1. Select **+ Add Operation**.
70-
1. Set your new operation to **POST**, and the Name, Display Name and URL of the operation as **test**.
71+
1. Set your new operation to **POST**, and the **Display name**, **Name**, and **URL** of the operation as **test**.
7172
1. **Save** your new operation.
7273

73-
:::image type="content" source="media/api-management-getstarted-revise-api/07-add-revisions-02-make-changes.png" alt-text="Modify revision":::
74+
:::image type="content" source="media/api-management-getstarted-revise-api/07-add-revisions-02-make-changes.png" alt-text="Screenshot showing how to add an operation in a revision in the portal.":::
7475
1. You've now made a change to **Revision 2**. Use the **revision selector** near the top of the page to switch back to **Revision 1**.
7576
1. Notice that your new operation doesn't appear in **Revision 1**.
7677

@@ -84,7 +85,7 @@ In this tutorial, you learn how to:
8485
1. Select the **Post to Public Change log for this API** checkbox, if you want to post notes about this change. Provide a description for your change that the developers can see, for example: **Testing revisions. Added new "test" operation.**
8586
1. **Revision 2** is now current.
8687

87-
:::image type="content" source="media/api-management-getstarted-revise-api/revisions-menu.png" alt-text="Revision menu in Revisions window":::
88+
:::image type="content" source="media/api-management-getstarted-revise-api/revisions-menu.png" alt-text="Screenshot of revision menu in Revisions window in the portal." lightbox="media/api-management-getstarted-revise-api/revisions-menu.png":::
8889

8990
### [Azure CLI](#tab/azure-cli)
9091

@@ -146,22 +147,41 @@ az apim api release delete --resource-group apim-hello-word-resource-group \
146147

147148
If you've tried the [developer portal](api-management-howto-developer-portal-customize.md), you can review the API changes and change log there.
148149

149-
1. In the Azure portal, select **APIs**.
150+
1. In the Azure portal, navigate to your API Management instance.
151+
1. In the left menu, under **APIs**, select **APIs**.
150152
1. Select **Developer portal** from the top menu.
151153
1. In the developer portal, select **APIs**, and then select **Demo Conference API**.
152154
1. Notice your new **test** operation is now available.
153155
1. Select **Changelog** near the API name.
154156
1. Notice that your change log entry appears in the list.
155157

156-
## Next steps
158+
159+
## Access an API revision
160+
161+
Each revision to your API can be accessed using a specially formed URL. Add `;rev={revisionNumber}` at the end of your API URL path, but before the query string, to access a specific revision of that API. For example, you might use this URL to access revision 2 of the Demo Conference API:
162+
163+
`https://apim-hello-world.azure-api.net/conf;rev=2/speakers`
164+
165+
You can find the URL paths for your API's revisions on the **Revisions** tab in the Azure portal.
166+
167+
:::image type="content" source="media/transform-api/revision-url-path.png" alt-text="Screenshot of revision URLs in the portal.":::
168+
169+
> [!TIP]
170+
> You can access the *current* revision of your API using the API path without the `;rev` string, in addition to the full URL that appends `;rev={revisionNumber}` to your API path.
171+
172+
173+
## Summary
157174

158175
In this tutorial, you learned how to:
159176

160177
> [!div class="checklist"]
161178
> * Add a new revision
162-
> * Make non-breaking changes to your revision
179+
> * Make nonbreaking changes to your revision
163180
> * Make your revision current and add a change log entry
164181
> * Browse the developer portal to see changes and change log
182+
> * Access an API revision
183+
184+
## Next steps
165185

166186
Advance to the next tutorial:
167187

5.48 KB
Loading
-49.3 KB
Loading
-20.9 KB
Loading
-2.99 KB
Loading
20 KB
Loading

0 commit comments

Comments
 (0)