hashicorp-vault include vaultKVUsePrefix setting (#1543)

* hashicorp-vault include vaultKVUsePrefix setting

as per pull request https://github.com/dapr/components-contrib/pull/929

* Update daprdocs/content/en/reference/components-reference/supported-secret-stores/hashicorp-vault.md

Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>

* Update hashicorp-vault.md

added detail for new field

Co-authored-by: Aaron Crawfis <Aaron.Crawfis@microsoft.com>
This commit is contained in:
Simone Banchieri 2021-07-08 18:55:17 +02:00 committed by GitHub
parent 702e38863f
commit 9b2bb23fab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 0 deletions

View File

@ -39,6 +39,8 @@ spec:
value : "[path_to_file_containing_token]"
- name: vaultKVPrefix # Optional. Default: "dapr"
value : "[vault_prefix]"
- name: vaultKVUsePrefix # Optional. default: "true"
value: "[true/false]"
```
{{% alert title="Warning" color="warning" %}}
The above example uses secrets as plain strings. It is recommended to use a local secret store such as [Kubernetes secret store]({{< ref kubernetes-secret-store.md >}}) or a [local file]({{< ref file-secret-store.md >}}) to bootstrap secure key storage.
@ -57,6 +59,7 @@ The above example uses secrets as plain strings. It is recommended to use a loca
| vaultTokenMountPath | Y | Path to file containing token | `"path/to/file"` |
| vaultToken | Y | [Token](https://learn.hashicorp.com/tutorials/vault/tokens) for authentication within Vault. | `"tokenValue"` |
| vaultKVPrefix | N | The prefix in vault. Defautls to `"dapr"` | `"dapr"`, `"myprefix"` |
| vaultKVUsePrefix | N | If false, vaultKVPrefix is forced to be empty. If the value is not given or set to true, vaultKVPrefix is used when accessing the vault. Setting it to false is needed to be able to use the BulkGetSecret method of the store. | `"true"`, `"false"` |
## Setup Hashicorp Vault instance