From b149edb9f2108b70366be9e63edfeaf4c8af19b2 Mon Sep 17 00:00:00 2001 From: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> Date: Mon, 10 Jul 2023 16:14:20 -0400 Subject: [PATCH] Update daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md Co-authored-by: Mark Fussell Signed-off-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> --- .../building-blocks/pubsub/subscription-methods.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md b/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md index 61ee82465..dce9cbd9a 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md +++ b/daprdocs/content/en/developing-applications/building-blocks/pubsub/subscription-methods.md @@ -189,7 +189,7 @@ The `/checkout` endpoint matches the `route` defined in the subscriptions and th The dynamic programmatic approach returns the `routes` JSON structure within the code, unlike the declarative approach's `route` YAML structure. -> **Note:** Dynamic subscriptions are only read once during application start-up. +> **Note:** Programmatic subscriptions are only read once during application start-up. You cannot _dynamically_ add new programmatic subscriptions, only at new ones at compile time. In the example below, you define the values found in the [declarative YAML subscription](#declarative-subscriptions) above within the application code.