From 6e2558fbf53fd4bd372acfffc92500deadbc5317 Mon Sep 17 00:00:00 2001 From: Phil Kedy Date: Tue, 14 Sep 2021 16:46:57 -0400 Subject: [PATCH] Tweak --- .../building-blocks/pubsub/howto-route-messages.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-route-messages.md b/daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-route-messages.md index 7ed5557a0..26a8daa8e 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-route-messages.md +++ b/daprdocs/content/en/developing-applications/building-blocks/pubsub/howto-route-messages.md @@ -8,6 +8,7 @@ description: "Learn how to route messages from a topic to different event handle {{% alert title="Note" color="primary" %}} This is an preview feature. To enable it, add the `PubSub.Routing` feature entry to your application configuration. +{{% /alert %}} ```yaml apiVersion: dapr.io/v1alpha1 @@ -24,8 +25,6 @@ spec: [Content-based routing](https://www.enterpriseintegrationpatterns.com/ContentBasedRouter.html) is a messaging pattern that utilizes a DSL instead of imperative application code. PubSub routing is an implementation of this pattern that allows developers to use expressions to route [CloudEvents](https://cloudevents.io) based on their contents to different URIs/paths and event handlers in your application. If no route matches, then an optional default route is used. This becomes useful as your applications expands to support multiple event versions, or special cases. Routing can be implemented with code; however, keeping routing rules external from the application can improve portability. -{{% /alert %}} - This feature is available to both the declarative and programmatic subscription approaches. ## Declarative subscription