Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 0c201a4

Browse files
committedJul 14, 2021
combined the different version articles of how-to-manage-routes into a single tabbed article
1 parent aedfdf6 commit 0c201a4

25 files changed

+501
-619
lines changed
 

‎.openpublishing.redirection.json

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17264,11 +17264,18 @@
1726417264
"redirect_url": "/azure/digital-twins/concepts-ontologies-convert",
1726517265
"redirect_document_id": false
1726617266
},
17267+
1726717268
{
17268-
"source_path_from_root": "/articles/digital-twins/how-to-manage-routes.md",
17269-
"redirect_url": "/azure/digital-twins/how-to-manage-routes-apis-cli",
17269+
"source_path_from_root": "/articles/digital-twins/how-to-manage-routes-apis-cli.md",
17270+
"redirect_url": "/azure/digital-twins/how-to-manage-routes",
1727017271
"redirect_document_id": true
1727117272
},
17273+
{
17274+
"source_path_from_root": "/articles/digital-twins/how-to-manage-routes-portal.md",
17275+
"redirect_url": "/azure/digital-twins/how-to-manage-routes",
17276+
"redirect_document_id": true
17277+
},
17278+
1727217279
{
1727317280
"source_path_from_root": "/articles/digital-twins/how-to-use-parser.md",
1727417281
"redirect_url": "/azure/digital-twins/how-to-parse-models",

‎articles/digital-twins/TOC.yml

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -126,11 +126,7 @@
126126
- name: Connect output
127127
items:
128128
- name: Manage endpoints and routes
129-
items:
130-
- name: Portal
131-
href: how-to-manage-routes-portal.md
132-
- name: APIs and CLI
133-
href: how-to-manage-routes-apis-cli.md
129+
href: how-to-manage-routes.md
134130
- name: Route events with a managed identity
135131
href: how-to-route-with-managed-identity.md
136132
- name: Integrate with Azure Maps

‎articles/digital-twins/concepts-data-ingress-egress.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Azure Digital Twins can send data to connected **endpoints**. Supported endpoint
4040
* [Event Grid](../event-grid/overview.md)
4141
* [Service Bus](../service-bus-messaging/service-bus-messaging-overview.md)
4242

43-
Endpoints are attached to Azure Digital Twins using management APIs or the Azure portal. Learn more about how to attach an endpoint to Azure Digital Twins in [How-to: Manage endpoints and routes](how-to-manage-routes-apis-cli.md).
43+
Endpoints are attached to Azure Digital Twins using management APIs or the Azure portal. Learn more about how to attach an endpoint to Azure Digital Twins in [How-to: Manage endpoints and routes](how-to-manage-routes.md).
4444

4545
There are many other services where you may want to ultimately direct your data, such as [Azure Storage](../storage/common/storage-introduction.md), [Azure Maps](../azure-maps/about-azure-maps.md), [Azure Data Explorer](/azure/data-explorer/data-explorer-overview), or [Time Series Insights](../time-series-insights/overview-what-is-tsi.md). To send your data to services like these, attach the destination service to an endpoint.
4646

‎articles/digital-twins/concepts-route-events.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ To define an event route, developers first must define endpoints. An **endpoint*
5656
* Event Hub
5757
* Service Bus
5858

59-
To create an endpoint, you can use the Azure Digital Twins [REST APIs, CLI commands](how-to-manage-routes-apis-cli.md#create-an-endpoint-for-azure-digital-twins), or the [Azure portal](how-to-manage-routes-portal.md#create-an-endpoint-for-azure-digital-twins).
59+
To create an endpoint, you can use the Azure Digital Twins [REST APIs, CLI commands, or the Azure portal](how-to-manage-routes.md#create-an-endpoint-for-azure-digital-twins).
6060

6161
When defining an endpoint, you'll need to provide:
6262
* The endpoint's name
@@ -72,15 +72,15 @@ The endpoint APIs that are available in control plane are:
7272

7373
## Create an event route
7474

75-
To create an event route, you can use the Azure Digital Twins [REST APIs, CLI commands](how-to-manage-routes-apis-cli.md#create-an-event-route), or the [Azure portal](how-to-manage-routes-portal.md#create-an-event-route).
75+
To create an event route, you can use the Azure Digital Twins [REST APIs, CLI commands, or the Azure portal](how-to-manage-routes.md#create-an-event-route).
7676

7777
Here is an example of creating an event route within a client application, using the `CreateOrReplaceEventRouteAsync` [.NET (C#) SDK](/dotnet/api/overview/azure/digitaltwins/client?view=azure-dotnet&preserve-view=true) call:
7878

7979
:::code language="csharp" source="~/digital-twins-docs-samples/sdks/csharp/eventRoute_operations.cs" id="CreateEventRoute":::
8080

8181
1. First, a `DigitalTwinsEventRoute` object is created, and the constructor takes the name of an endpoint. This `endpointName` field identifies an endpoint such as an Event Hub, Event Grid, or Service Bus. These endpoints must be created in your subscription and attached to Azure Digital Twins using control plane APIs before making this registration call.
8282

83-
2. The event route object also has a [Filter](how-to-manage-routes-apis-cli.md#filter-events) field, which can be used to restrict the types of events that follow this route. A filter of `true` enables the route with no additional filtering (a filter of `false` disables the route).
83+
2. The event route object also has a [Filter](how-to-manage-routes.md#filter-events) field, which can be used to restrict the types of events that follow this route. A filter of `true` enables the route with no additional filtering (a filter of `false` disables the route).
8484

8585
3. This event route object is then passed to `CreateOrReplaceEventRouteAsync`, along with a name for the route.
8686

@@ -101,7 +101,7 @@ Before setting the dead-letter location, you must have a storage account with a
101101

102102
To learn more about SAS tokens, see: [Grant limited access to Azure Storage resources using shared access signatures (SAS)](../storage/common/storage-sas-overview.md)
103103

104-
To learn how to set up an endpoint with dead-lettering, see [How-to: Manage endpoints and routes in Azure Digital Twins (APIs and CLI)](how-to-manage-routes-apis-cli.md#create-an-endpoint-with-dead-lettering).
104+
To learn how to set up an endpoint with dead-lettering, see [How-to: Manage endpoints and routes in Azure Digital Twins](how-to-manage-routes.md#create-an-endpoint-with-dead-lettering).
105105

106106
### Types of event messages
107107

@@ -112,7 +112,7 @@ Different types of events in IoT Hub and Azure Digital Twins produce different t
112112
## Next steps
113113

114114
See how to set up and manage an event route:
115-
* [How-to: Manage endpoints and routes](how-to-manage-routes-apis-cli.md)
115+
* [How-to: Manage endpoints and routes](how-to-manage-routes.md)
116116

117117
Or, see how to use Azure Functions to route events within Azure Digital Twins:
118118
* [How-to: Set up an Azure function for processing data](how-to-create-azure-function.md)

0 commit comments

Comments
 (0)
Please sign in to comment.