The documentation you are viewing is for Dapr v1.8 which is an older version of Dapr. For up-to-date documentation, see the latest version.
Local file (for Development)
This Dapr secret store component reads plain text JSON from a given file and does not use authentication.
Warning
This approach to secret management is not recommended for production environments.Component format
To setup local file based secret store create a component of type secretstores.local.file
. Create a file with the following content in your ./components
directory:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
name: local-secret-store
spec:
type: secretstores.local.file
version: v1
metadata:
- name: secretsFile
value: [path to the JSON file]
- name: nestedSeparator
value: ":"
- name: multiValued
value: "false"
Spec metadata fields
Field | Required | Details | Example |
---|---|---|---|
secretsFile | Y | The path to the file where secrets are stored | "path/to/file.json" |
nestedSeparator | N | Used by the store when flattening the JSON hierarchy to a map. Defaults to ":" |
":" |
multiValued | N | Allows one level of multi-valued key/value pairs before flattening JSON hierarchy. Defaults to "false" |
"true" |
Setup JSON file to hold the secrets
Given the following JSON loaded from secretsFile
:
{
"redisPassword": "your redis password",
"connectionStrings": {
"sql": "your sql connection string",
"mysql": "your mysql connection string"
}
}
If multiValued
is "false"
, the store will load the file and create a map with the following key value pairs:
flattened key | value |
---|---|
“redisPassword” | “your redis password” |
“connectionStrings:sql” | “your sql connection string” |
“connectionStrings:mysql” | “your mysql connection string” |
Use the flattened key (connectionStrings:sql
) to access the secret. The following JSON map returned:
{
"connectionStrings:sql": "your sql connection string"
}
If multiValued
is "true"
, you would instead use the top level key. In this example, connectionStrings
would return the following map:
{
"sql": "your sql connection string",
"mysql": "your mysql connection string"
}
Nested structures after the top level will be flattened. In this example, connectionStrings
would return the following map:
JSON from secretsFile
:
{
"redisPassword": "your redis password",
"connectionStrings": {
"mysql": {
"username": "your mysql username",
"password": "your mysql password"
}
}
}
Response:
{
"mysql:username": "your mysql username",
"mysql:password": "your mysql password"
}
This is useful in order to mimic secret stores like Vault or Kubernetes that return multiple key/value pairs per secret key.
Related links
- Secrets building block
- How-To: Retrieve a secret
- How-To: Reference secrets in Dapr components
- Secrets API reference
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.