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

Update daprdocs/content/en/operations/components/component-scopes.md 

Co-authored-by: Hannah Hunter <94493363+hhunter-ms@users.noreply.github.com>
This commit is contained in:
Mark Fussell 2022-03-03 14:15:58 -08:00 committed by GitHub
parent e603307edc
commit 013890ec13
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
daprdocs/content/en/operations/components/component-scopes.md
View File

@ -79,7 +79,7 @@ See [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-name
{{% /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.
Developers and operators might want to limit access to one database from a certain application, or a specific set of applications.
To achieve this, Dapr allows you to specify `scopes` on the component YAML. Application scopes added to a component limit only the applications with specific IDs to be able to use the component.
The following example shows how to give access to two Dapr enabled apps, with the app IDs of `app1` and `app2` to the Redis component named `statestore` which itself is in the `production` namespace