dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'v1.13' into issue_2923

This commit is contained in:
Hannah Hunter 2024-05-29 19:15:19 -04:00 committed by GitHub
parent fc42fe7e58 0260c0f5dd
commit 93f39e216e
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 21 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-scopes.md
View File

@ -69,17 +69,17 @@ The table below shows which applications are allowed to publish into the topics:
| | topic1 | topic2 | topic3 |
|------|--------|--------|--------|
| app1 | X | | |
| app2 | | X | X |
| app1 | ✅ | | |
| app2 | | ✅ | ✅ |
| app3 | | | |
The table below shows which applications are allowed to subscribe to the topics:
| | topic1 | topic2 | topic3 |
|------|--------|--------|--------|
| app1 | X | X | X |
| app1 | ✅ | ✅ | ✅ |
| app2 | | | |
| app3 | X | | |
| app3 | ✅ | | |
> Note: If an application is not listed (e.g. app1 in subscriptionScopes) it is allowed to subscribe to all topics. Because `allowedTopics` is not used and app1 does not have any subscription scopes, it can also use additional topics not listed above.
@ -143,17 +143,17 @@ The table below shows which application is allowed to publish into the topics:
| | A | B | C |
|------|---|---|---|
| app1 | X | | |
| app2 | X | X | |
| app3 | X | X | |
| app1 | ✅ | | |
| app2 | ✅ | ✅ | |
| app3 | ✅ | ✅ | |
The table below shows which application is allowed to subscribe to the topics:
| | A | B | C |
|------|---|---|---|
| app1 | | | |
| app2 | X | | |
| app3 | X | X | |
| app2 | ✅ | | |
| app3 | ✅ | ✅ | |
## Example 4: Mark topics as protected
@ -187,17 +187,17 @@ The table below shows which application is allowed to publish into the topics:
| | A | B | C |
|------|---|---|---|
| app1 | X | X | |
| app2 | | X | |
| app3 | | | X |
| app1 | ✅ | ✅ | |
| app2 | | ✅ | |
| app3 | | | ✅ |
The table below shows which application is allowed to subscribe to the topics:
| | A | B | C |
|------|---|---|---|
| app1 | X | X | |
| app2 | | X | |
| app3 | | | X |
| app1 | ✅ | ✅ | |
| app2 | | ✅ | |
| app3 | | | ✅ |
## Demo

12
daprdocs/content/en/operations/components/setup-pubsub/pubsub-namespaces.md
View File

@ -23,12 +23,12 @@ The table below shows which resources are deployed to which namespaces:
| Resource | namespace-a | namespace-b |
|------------------------ |-------------|-------------|
| Redis master | X | |
| Redis replicas | X | |
| Dapr's PubSub component | X | X |
| Node subscriber | X | |
| Python subscriber | X | |
| React UI publisher | | X |
| Redis master | ✅ | ❌ |
| Redis replicas | ✅ | ❌ |
| Dapr's PubSub component | ✅ | ✅ |
| Node subscriber | ✅ | ❌ |
| Python subscriber | ✅ | ❌ |
| React UI publisher | ❌ | ✅ |
{{% alert title="Note" color="primary" %}}
All pub/sub components support limiting pub/sub topics to specific applications using [namespace or component scopes]({{< ref pubsub-scopes.md >}}).