From e603307edc6d37a204b9a56e4554e2d88c29a8df Mon Sep 17 00:00:00 2001 From: Mark Fussell Date: Thu, 3 Mar 2022 14:15:44 -0800 Subject: [PATCH] Update daprdocs/content/en/operations/components/component-scopes.md Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com> --- .../content/en/operations/components/component-scopes.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/daprdocs/content/en/operations/components/component-scopes.md b/daprdocs/content/en/operations/components/component-scopes.md index f5ab6595e..14af6701a 100644 --- a/daprdocs/content/en/operations/components/component-scopes.md +++ b/daprdocs/content/en/operations/components/component-scopes.md @@ -72,7 +72,11 @@ In this example, the Redis component is only accessible to Dapr instances runnin {{< /tabs >}} -Note: It is possible to have the component YAML applied to namespace "A" *reference* the implementation in namespace "B". For example, a component YAML for Redis in namespace "production-A" can set the Redis host address to point to the Redis instance deployed in namespace "production-B". See [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-namespaces.md" >}}) for an example. +{{% alert title="Note" color="primary" %}} +The component YAML applied to namespace "A" can *reference* the implementation in namespace "B". For example, a component YAML for Redis in namespace "production-A" can point the Redis host address to the Redis instance deployed in namespace "production-B". + +See [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-namespaces.md" >}}) for an example. +{{% /alert %}} ## Application access to components with scopes Developers and operators might want to limit access for one database to a certain application, or a specific set of applications.