From eec904d34ea8245079e26c2e047be06e9249d713 Mon Sep 17 00:00:00 2001 From: Tiago Alves Macambira Date: Thu, 13 Oct 2022 16:28:52 -0700 Subject: [PATCH 1/3] Fix: codeblock wasn't properly closed Minor formatting fix. Signed-off-by: Tiago Alves Macambira --- .../supported-secret-stores/hashicorp-vault.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/reference/components-reference/supported-secret-stores/hashicorp-vault.md b/daprdocs/content/en/reference/components-reference/supported-secret-stores/hashicorp-vault.md index 3c7a9bb4f..76a33c54c 100644 --- a/daprdocs/content/en/reference/components-reference/supported-secret-stores/hashicorp-vault.md +++ b/daprdocs/content/en/reference/components-reference/supported-secret-stores/hashicorp-vault.md @@ -64,7 +64,7 @@ The above example uses secrets as plain strings. It is recommended to use a loca | vaultKVPrefix | N | The prefix in vault. Defaults 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"` | | enginePath | N | The [engine](https://www.vaultproject.io/api-docs/secret/kv/kv-v2) path in vault. Defaults to `"secret"` | `"kv"`, `"any"` | -| vaultValueType | N | Vault value type. `map` means to parse the value into `map[string]string`, `text` means to use the value as a string. 'map' sets the `multipleKeyValuesPerSecret` behavior. `text' makes Vault behave as a secret store with name/value semantics. Defaults to `"map"` | `"map"`, `"text"` | +| vaultValueType | N | Vault value type. `map` means to parse the value into `map[string]string`, `text` means to use the value as a string. 'map' sets the `multipleKeyValuesPerSecret` behavior. `text` makes Vault behave as a secret store with name/value semantics. Defaults to `"map"` | `"map"`, `"text"` | ## Setup Hashicorp Vault instance From 490f4371501af5bcb05256cbd38fe6040362d14e Mon Sep 17 00:00:00 2001 From: Tiago Alves Macambira Date: Fri, 14 Oct 2022 10:25:16 -0700 Subject: [PATCH 2/3] Fix broken link in components-concept page Commit https://github.com/dapr/docs/pull/2875/commits/043a39d3d161a7b44b95a7099ec862329d70eefa shuffled content around and removed a section called "Pluggable Components", breaking an existing link to this section. This PR fixes the link to point to the section now hosting the appropriate content. Signed-off-by: Tiago Alves Macambira --- daprdocs/content/en/concepts/components-concept.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/daprdocs/content/en/concepts/components-concept.md b/daprdocs/content/en/concepts/components-concept.md index 2ec3c936d..9a2c2bf41 100644 --- a/daprdocs/content/en/concepts/components-concept.md +++ b/daprdocs/content/en/concepts/components-concept.md @@ -11,7 +11,7 @@ Dapr uses a modular design where functionality is delivered as a component. Each You can contribute implementations and extend Dapr's component interfaces capabilities via: - The [components-contrib repository](https://github.com/dapr/components-contrib) -- [Pluggable components]({{}}). +- [Pluggable components]({{}}). A building block can use any combination of components. For example, the [actors]({{}}) and the [state management]({{}}) building blocks both use [state components](https://github.com/dapr/components-contrib/tree/master/state). From 1fdcfbd7dec4a67d1234a507fc1a225a49ed9600 Mon Sep 17 00:00:00 2001 From: Marcos Candeia Date: Tue, 18 Oct 2022 11:47:37 -0300 Subject: [PATCH 3/3] Simplifying kubernetes YAML config (#2908) * Simplifying Kubernetes YAML Signed-off-by: Marcos Candeia * Update pluggable-components-registration.md Signed-off-by: Marcos Candeia Signed-off-by: Marcos Candeia --- .../pluggable-components-registration.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/daprdocs/content/en/operations/components/pluggable-components/pluggable-components-registration.md b/daprdocs/content/en/operations/components/pluggable-components/pluggable-components-registration.md index c1242eaf8..068780d3b 100644 --- a/daprdocs/content/en/operations/components/pluggable-components/pluggable-components-registration.md +++ b/daprdocs/content/en/operations/components/pluggable-components/pluggable-components-registration.md @@ -174,11 +174,8 @@ spec: - name: component volumeMounts: # required, the sockets volume mount - name: dapr-unix-domain-socket - mountPath: /dapr-unix-domain-sockets + mountPath: /tmp/dapr-components-sockets image: YOUR_IMAGE_GOES_HERE:YOUR_IMAGE_VERSION - env: - - name: DAPR_COMPONENTS_SOCKETS_FOLDER # Tells the component where the sockets should be created. - value: /dapr-unix-domain-sockets ``` Before applying the deployment, let's add one more configuration: the component spec.