diff --git a/daprdocs/content/en/contributing/contributing-docs.md b/daprdocs/content/en/contributing/contributing-docs.md index 66d1c5881..1e73bda86 100644 --- a/daprdocs/content/en/contributing/contributing-docs.md +++ b/daprdocs/content/en/contributing/contributing-docs.md @@ -274,7 +274,7 @@ Will result in the following output: {{< code-snippet file="contributing-1.py" lang="python" marker="#SAMPLE" >}} -Use the `replace-key-[token]` and `replace-value-[token]` parameters to limit the embedded snipped to a portion of the sample file. This is useful when you want abbreviate a portion of the code sample. Multiple replacements are supported with multiple values of `token`. +Use the `replace-key-[token]` and `replace-value-[token]` parameters to limit the embedded snipped to a portion of the sample file. This is useful when you want abbreviate a portion of the code sample. Multiple replacements are supported with multiple values of `token`. The shortcode below and code sample: diff --git a/daprdocs/content/en/developing-applications/building-blocks/actors/actor-reentrancy.md b/daprdocs/content/en/developing-applications/building-blocks/actors/actor-reentrancy.md index 7283e6785..a9f861328 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/actors/actor-reentrancy.md +++ b/daprdocs/content/en/developing-applications/building-blocks/actors/actor-reentrancy.md @@ -67,7 +67,7 @@ func configHandler(w http.ResponseWriter, r *http.Request) { ``` ### Handling reentrant requests -The key to a reentrant request is the `Dapr-Reentrancy-Id` header. The value of this header is used to match requests to their call chain and allow them to bypass the actor's lock. +The key to a reentrant request is the `Dapr-Reentrancy-Id` header. The value of this header is used to match requests to their call chain and allow them to bypass the actor's lock. The header is generated by the Dapr runtime for any actor request that has a reentrant config specified. Once it is generated, it is used to lock the actor and must be passed to all future requests. Below is a snippet of code from an actor handling this is Golang: diff --git a/daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md b/daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md index 249fe28a3..193a3c8b5 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md +++ b/daprdocs/content/en/developing-applications/building-blocks/actors/howto-actors.md @@ -25,7 +25,7 @@ Refer [api spec]({{< ref "actors_api.md#invoke-actor-method" >}}) for more detai Actors can save state reliably using state management capability. You can interact with Dapr through HTTP/gRPC endpoints for state management. -To use actors, your state store must support multi-item transactions. This means your state store [component](https://github.com/dapr/components-contrib/tree/master/state) must implement the [TransactionalStore](https://github.com/dapr/components-contrib/blob/master/state/transactional_store.go) interface. The list of components that support transactions/actors can be found here: [supported state stores]({{< ref supported-state-stores.md >}}). Only a single state store component can be used as the statestore for all actors. +To use actors, your state store must support multi-item transactions. This means your state store [component](https://github.com/dapr/components-contrib/tree/master/state) must implement the [TransactionalStore](https://github.com/dapr/components-contrib/blob/master/state/transactional_store.go) interface. The list of components that support transactions/actors can be found here: [supported state stores]({{< ref supported-state-stores.md >}}). Only a single state store component can be used as the statestore for all actors. ## Actor timers and reminders @@ -200,7 +200,7 @@ public void ConfigureServices(IServiceCollection services) { // Register actor types and configure actor settings options.Actors.RegisterActor(); - + // Configure default settings options.ActorIdleTimeout = TimeSpan.FromMinutes(60); options.ActorScanInterval = TimeSpan.FromSeconds(30); @@ -312,7 +312,7 @@ public void ConfigureServices(IServiceCollection services) { // Register actor types and configure actor settings options.Actors.RegisterActor(); - + // Configure default settings options.ActorIdleTimeout = TimeSpan.FromMinutes(60); options.ActorScanInterval = TimeSpan.FromSeconds(30); diff --git a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md index 0738b032d..859ac8470 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md +++ b/daprdocs/content/en/developing-applications/building-blocks/pubsub/pubsub-raw.md @@ -3,7 +3,7 @@ type: docs title: "Pub/Sub without CloudEvents" linkTitle: "Pub/Sub without CloudEvents" weight: 7000 -description: "Use Pub/Sub without CloudEvents." +description: "Use Pub/Sub without CloudEvents." --- ## Introduction diff --git a/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md b/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md index 83a933e54..333f4d8e8 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md +++ b/daprdocs/content/en/developing-applications/building-blocks/secrets/secrets-scopes.md @@ -21,7 +21,7 @@ Watch this [video](https://youtu.be/j99RN_nxExA?start=2272) for a demo on how to ## Scenario 1 : Deny access to all secrets for a secret store -In this example all secret access is denied to an application running on a Kubernetes cluster which has a configured [Kubernetes secret store]({{}}) named `mycustomsecretstore`. In the case of Kubernetes, aside from the user defined custom store, the default store named `kubernetes` is also addressed to ensure all secrets are denied access (See [here]({{}}) to learn more about the Kubernetes default secret store). +In this example all secret access is denied to an application running on a Kubernetes cluster which has a configured [Kubernetes secret store]({{}}) named `mycustomsecretstore`. In the case of Kubernetes, aside from the user defined custom store, the default store named `kubernetes` is also addressed to ensure all secrets are denied access (See [here]({{}}) to learn more about the Kubernetes default secret store). To add this configuration follow the steps below: diff --git a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md index f26facf54..571f49c2f 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md +++ b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/howto-invoke-discover-services.md @@ -1,4 +1,4 @@ ---- +--- type: docs title: "How-To: Invoke services using HTTP" linkTitle: "How-To: Invoke with HTTP" diff --git a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md index 31a3235e9..a4f22f543 100644 --- a/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md +++ b/daprdocs/content/en/developing-applications/building-blocks/service-invocation/service-invocation-overview.md @@ -83,7 +83,7 @@ Connection establishment via gRPC to the target sidecar has a timeout of 5 secon ### Pluggable service discovery -Dapr can run on a variety of [hosting platforms]({{< ref hosting >}}). To enable service discovery and service invocation, Dapr uses pluggable [name resolution components]({{< ref supported-name-resolution >}}). For example, the Kubernetes name resolution component uses the Kubernetes DNS service to resolve the location of other applications running in the cluster. Self-hosted machines can use the mDNS name resolution component. The Consul name resolution component can be used in any hosting environment including Kubernetes or self-hosted. +Dapr can run on a variety of [hosting platforms]({{< ref hosting >}}). To enable service discovery and service invocation, Dapr uses pluggable [name resolution components]({{< ref supported-name-resolution >}}). For example, the Kubernetes name resolution component uses the Kubernetes DNS service to resolve the location of other applications running in the cluster. Self-hosted machines can use the mDNS name resolution component. The Consul name resolution component can be used in any hosting environment including Kubernetes or self-hosted. ### Round robin load balancing with mDNS @@ -105,7 +105,7 @@ The API for service invocation can be found in the [service invocation API refer ### gRPC proxying -Dapr allows users to keep their own proto services and work natively with gRPC. This means that you can use service invocation to call your existing gRPC apps without having to include any Dapr SDKs or include custom gRPC services. For more information, see the [how-to tutorial for Dapr and gRPC]({{< ref howto-invoke-services-grpc.md >}}). +Dapr allows users to keep their own proto services and work natively with gRPC. This means that you can use service invocation to call your existing gRPC apps without having to include any Dapr SDKs or include custom gRPC services. For more information, see the [how-to tutorial for Dapr and gRPC]({{< ref howto-invoke-services-grpc.md >}}). ## Example diff --git a/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md b/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md index a7408a91e..fcecb016b 100644 --- a/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md +++ b/daprdocs/content/en/developing-applications/debugging/bridge-to-kubernetes.md @@ -6,7 +6,7 @@ weight: 300 description: "Debug Dapr apps locally which still connected to your Kubernetes cluster" --- -Bridge to Kubernetes allows you to run and debug code on your development computer, while still connected to your Kubernetes cluster with the rest of your application or services. This type of debugging is often called *local tunnel debugging*. +Bridge to Kubernetes allows you to run and debug code on your development computer, while still connected to your Kubernetes cluster with the rest of your application or services. This type of debugging is often called *local tunnel debugging*. {{< button text="Learn more about Bridge to Kubernetes" link="https://aka.ms/bridge-vscode-dapr" >}} diff --git a/daprdocs/content/en/developing-applications/debugging/debug-k8s/debug-daprd.md b/daprdocs/content/en/developing-applications/debugging/debug-k8s/debug-daprd.md index b1b2806ff..ac38d8257 100644 --- a/daprdocs/content/en/developing-applications/debugging/debug-k8s/debug-daprd.md +++ b/daprdocs/content/en/developing-applications/debugging/debug-k8s/debug-daprd.md @@ -91,5 +91,5 @@ All done. Now you can point to port 40000 and start a remote debug session to da - [Overview of Dapr on Kubernetes]({{< ref kubernetes-overview >}}) - [Deploy Dapr to a Kubernetes cluster]({{< ref kubernetes-deploy >}}) -- [Debug Dapr services on Kubernetes]({{< ref debug-dapr-services >}}) +- [Debug Dapr services on Kubernetes]({{< ref debug-dapr-services >}}) - [Dapr Kubernetes Quickstart](https://github.com/dapr/quickstarts/tree/master/hello-kubernetes) \ No newline at end of file diff --git a/daprdocs/content/en/developing-applications/ides/vscode/vscode-how-to-debug-multiple-dapr-apps.md b/daprdocs/content/en/developing-applications/ides/vscode/vscode-how-to-debug-multiple-dapr-apps.md index 48a10e959..92451972b 100644 --- a/daprdocs/content/en/developing-applications/ides/vscode/vscode-how-to-debug-multiple-dapr-apps.md +++ b/daprdocs/content/en/developing-applications/ides/vscode/vscode-how-to-debug-multiple-dapr-apps.md @@ -56,7 +56,7 @@ In the case of the hello world quickstart, two applications are launched, each w "type": "python", "request": "launch", "name": "Pythonapp with Dapr", - "program": "${workspaceFolder}/app.py", + "program": "${workspaceFolder}/app.py", "console": "integratedTerminal", "preLaunchTask": "daprd-debug-python", "postDebugTask": "daprd-down-python" @@ -69,7 +69,7 @@ Each configuration requires a `request`, `type` and `name`. These parameters hel - `type` defines the language used. Depending on the language, it might require an extension found in the marketplace, such as the [Python Extension](https://marketplace.visualstudio.com/items?itemName=ms-python.python). - `name` is a unique name for the configuration. This is used for compound configurations when calling multiple configurations in your project. -- `${workspaceFolder}` is a VS Code variable reference. This is the path to the workspace opened in VS Code. +- `${workspaceFolder}` is a VS Code variable reference. This is the path to the workspace opened in VS Code. - The `preLaunchTask` and `postDebugTask` parameters refer to the program configurations run before and after launching the application. See step 2 on how to configure these. For more information on VSCode debugging parameters see [VS Code launch attributes](https://code.visualstudio.com/Docs/editor/debugging#_launchjson-attributes). @@ -153,7 +153,7 @@ Below are the supported parameters for VS Code tasks. These parameters are equiv | `appPort` | This parameter tells Dapr which port your application is listening on | Yes | `"appPort": 4000` | `appProtocol` | Tells Dapr which protocol your application is using. Valid options are http and grpc. Default is http | No | `"appProtocol": "http"` | `appSsl` | Sets the URI scheme of the app to https and attempts an SSL connection | No | `"appSsl": true` -| `args` | Sets a list of arguments to pass on to the Dapr app | No | "args": [] +| `args` | Sets a list of arguments to pass on to the Dapr app | No | "args": [] | `componentsPath` | Path for components directory. If empty, components will not be loaded. | No | `"componentsPath": "./components"` | `config` | Tells Dapr which Configuration CRD to use | No | `"config": "./config"` | `controlPlaneAddress` | Address for a Dapr control plane | No | `"controlPlaneAddress": "http://localhost:1366/"` diff --git a/daprdocs/content/en/developing-applications/integrations/workflows.md b/daprdocs/content/en/developing-applications/integrations/workflows.md index 572899c53..ec30a0e1e 100644 --- a/daprdocs/content/en/developing-applications/integrations/workflows.md +++ b/daprdocs/content/en/developing-applications/integrations/workflows.md @@ -80,28 +80,28 @@ Prerequisites: 1. Set up the environment variables containing the Azure Storage Account credentials: {{< tabs Windows "macOS/Linux" >}} - + {{% codetab %}} ```bash export STORAGE_ACCOUNT_KEY= export STORAGE_ACCOUNT_NAME= ``` {{% /codetab %}} - + {{% codetab %}} ```bash set STORAGE_ACCOUNT_KEY= set STORAGE_ACCOUNT_NAME= ``` {{% /codetab %}} - + {{< /tabs >}} 1. Move to the workflows directory and run the sample runtime: ```bash cd src/Dapr.Workflows - + dapr run --app-id workflows --protocol grpc --port 3500 --app-port 50003 -- dotnet run --workflows-path ../../samples ``` @@ -109,8 +109,8 @@ Prerequisites: ```bash curl http://localhost:3500/v1.0/invoke/workflows/method/workflow1 - - {"value":"Hello from Logic App workflow running with Dapr!"} + + {"value":"Hello from Logic App workflow running with Dapr!"} ``` ### Kubernetes @@ -153,7 +153,7 @@ Prerequisites: ```bash curl http://localhost:3500/v1.0/invoke/workflows/method/workflow1 - + {"value":"Hello from Logic App workflow running with Dapr!"} ``` @@ -186,35 +186,35 @@ Prerequisites: 1. Next, apply the Dapr component: {{< tabs Self-hosted Kubernetes >}} - + {{% codetab %}} Place the binding yaml file above in a `components` directory at the root of your application. {{% /codetab %}} - + {{% codetab %}} ```bash kubectl apply -f my_binding.yaml ``` {{% /codetab %}} - + {{< /tabs >}} 1. Once an event is sent to the bindings component, check the logs Dapr Workflows to see the output. {{< tabs Self-hosted Kubernetes >}} - + {{% codetab %}} In standalone mode, the output will be printed to the local terminal. {{% /codetab %}} - + {{% codetab %}} On Kubernetes, run the following command: - + ```bash kubectl logs -l app=dapr-workflows-host -c host ``` {{% /codetab %}} - + {{< /tabs >}} ## Example diff --git a/daprdocs/content/en/getting-started/install-dapr-selfhost.md b/daprdocs/content/en/getting-started/install-dapr-selfhost.md index 6c1d8fd0e..d50d6325b 100644 --- a/daprdocs/content/en/getting-started/install-dapr-selfhost.md +++ b/daprdocs/content/en/getting-started/install-dapr-selfhost.md @@ -7,7 +7,7 @@ aliases: - /getting-started/install-dapr/ --- -Now that you have the [Dapr CLI installed]({{}}), it's time to initialize Dapr on your local machine using the CLI. +Now that you have the [Dapr CLI installed]({{}}), it's time to initialize Dapr on your local machine using the CLI. Dapr runs as a sidecar alongside your application, and in self-hosted mode this means it is a process on your local machine. Therefore, initializing Dapr includes fetching the Dapr sidecar binaries and installing them locally. @@ -29,11 +29,11 @@ This recommended development environment requires [Docker](https://docs.docker.c {{% codetab %}} If you run your Docker commands with sudo, or the install path is `/usr/local/bin` (default install path), you will need to use `sudo` below. {{% /codetab %}} - + {{% codetab %}} Make sure that you run Command Prompt as administrator (right click, run as administrator) {{% /codetab %}} - + {{< /tabs >}} ### Step 2: Run the init CLI command diff --git a/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-no-docker.md b/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-no-docker.md index ed538b3ac..0fdf85a6a 100644 --- a/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-no-docker.md +++ b/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-no-docker.md @@ -20,16 +20,16 @@ The Dapr CLI provides an option to initialize Dapr using slim init, without the dapr init --slim ``` -In this mode two different binaries are installed `daprd` and `placement`. The `placement` binary is needed to enable [actors]({{< ref "actors-overview.md" >}}) in a Dapr self-hosted installation. +In this mode two different binaries are installed `daprd` and `placement`. The `placement` binary is needed to enable [actors]({{< ref "actors-overview.md" >}}) in a Dapr self-hosted installation. In this mode no default components such as Redis are installed for state management or pub/sub. This means, that aside from [Service Invocation]({{< ref "service-invocation-overview.md" >}}), no other building block functionality is available on install out of the box. Users are free to setup their own environment and custom components. Furthermore, actor based service invocation is possible if a state store is configured as explained in the following sections. ## Service invocation -See [this sample](https://github.com/dapr/samples/tree/master/hello-dapr-slim) for an example on how to perform service invocation in this mode. +See [this sample](https://github.com/dapr/samples/tree/master/hello-dapr-slim) for an example on how to perform service invocation in this mode. ## Enabling state management or pub/sub -See configuring Redis in self-hosted mode [without docker](https://redis.io/topics/quickstart) to enable a local state store or pub/sub broker for messaging. +See configuring Redis in self-hosted mode [without docker](https://redis.io/topics/quickstart) to enable a local state store or pub/sub broker for messaging. ## Enabling actors @@ -51,7 +51,7 @@ INFO[0001] leader is established. instance=Nicoletaz-L10. ``` -From here on you can follow the sample example created for the [java-sdk](https://github.com/dapr/java-sdk/tree/master/examples/src/main/java/io/dapr/examples/actors), [python-sdk](https://github.com/dapr/python-sdk/tree/master/examples/demo_actor) or [dotnet-sdk]({{< ref "dotnet-actors-howto.md" >}}) for running an application with Actors enabled. +From here on you can follow the sample example created for the [java-sdk](https://github.com/dapr/java-sdk/tree/master/examples/src/main/java/io/dapr/examples/actors), [python-sdk](https://github.com/dapr/python-sdk/tree/master/examples/demo_actor) or [dotnet-sdk]({{< ref "dotnet-actors-howto.md" >}}) for running an application with Actors enabled. Update the state store configuration files to have the Redis host and password match the setup that you have. Additionally to enable it as a actor state store have the metadata piece added similar to the [sample Java Redis component](https://github.com/dapr/java-sdk/blob/master/examples/components/state/redis.yaml) definition. diff --git a/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-overview.md b/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-overview.md index 49a417b9f..aa24c213c 100644 --- a/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-overview.md +++ b/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-overview.md @@ -8,7 +8,7 @@ description: "Overview of how to get Dapr running on a Windows/Linux/MacOS machi ## Overview -Dapr can be configured to run in self-hosted mode on your local developer machine or on production VMs. Each running service has a Dapr runtime process (or sidecar) which is configured to use state stores, pub/sub, binding components and the other building blocks. +Dapr can be configured to run in self-hosted mode on your local developer machine or on production VMs. Each running service has a Dapr runtime process (or sidecar) which is configured to use state stores, pub/sub, binding components and the other building blocks. ## Initialization @@ -17,13 +17,13 @@ Dapr can be initialized [with Docker]({{< ref self-hosted-with-docker.md >}}) (d - A Zipkin container for diagnostics and tracing. - A default Dapr configuration and components installed in `$HOME/.dapr/` (Mac/Linux) or `%USERPROFILE%\.dapr\` (Windows). -The `dapr-placement` service is responsible for managing the actor distribution scheme and key range settings. This service is not launched as a container and is only required if you are using Dapr actors. For more information on the actor `Placement` service read [actor overview]({{< ref "actors-overview.md" >}}). +The `dapr-placement` service is responsible for managing the actor distribution scheme and key range settings. This service is not launched as a container and is only required if you are using Dapr actors. For more information on the actor `Placement` service read [actor overview]({{< ref "actors-overview.md" >}}). Diagram of Dapr in self-hosted Docker mode ## Launching applications with Dapr -You can use the [`dapr run` CLI command]({{< ref dapr-run.md >}}) to a Dapr sidecar process along with your application. Additional arguments and flags can be found [here]({{< ref arguments-annotations-overview.md >}}). +You can use the [`dapr run` CLI command]({{< ref dapr-run.md >}}) to a Dapr sidecar process along with your application. Additional arguments and flags can be found [here]({{< ref arguments-annotations-overview.md >}}). ## Name resolution diff --git a/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-upgrade.md b/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-upgrade.md index 5aa9ad56a..5e541761d 100644 --- a/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-upgrade.md +++ b/daprdocs/content/en/operations/hosting/self-hosted/self-hosted-upgrade.md @@ -12,7 +12,7 @@ description: "Follow these steps to upgrade Dapr in self-hosted mode and ensure {{% alert title="Note" color="warning" %}} This will remove the default `$HOME/.dapr` directory, binaries and all containers (dapr_redis, dapr_placement and dapr_zipkin). Linux users need to run `sudo` if docker command needs sudo. {{% /alert %}} - + ```bash dapr uninstall --all ``` @@ -29,7 +29,7 @@ description: "Follow these steps to upgrade Dapr in self-hosted mode and ensure ```bash $ dapr --version - + CLI version: 1.3 Runtime version: 1.3 ``` diff --git a/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md b/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md index d1d2e7ff7..44a453649 100644 --- a/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md +++ b/daprdocs/content/en/operations/monitoring/tracing/supported-tracing-backends/jaeger.md @@ -175,7 +175,7 @@ That's it! Your Dapr sidecar is now configured for use with Jaeger. To view traces, connect to the Jaeger Service and open the UI: -```bash +```bash kubectl port-forward svc/jaeger-query 16686 ``` diff --git a/daprdocs/content/en/operations/troubleshooting/common_issues.md b/daprdocs/content/en/operations/troubleshooting/common_issues.md index 230c1d135..77d963c80 100644 --- a/daprdocs/content/en/operations/troubleshooting/common_issues.md +++ b/daprdocs/content/en/operations/troubleshooting/common_issues.md @@ -223,6 +223,6 @@ In order for mDNS to function properly, ensure `Micorosft Content Filter` is ina - Type `mdatp system-extension network-filter disable` and hit enter. - Enter your account password. -Microsoft Content Filter is disabled when the output is "Success". +Microsoft Content Filter is disabled when the output is "Success". -> Some organizations will re-enable the filter from time to time. If you repeatedly encounter app-id values missing, first check to see if the filter has been re-enabled before doing more extensive troubleshooting. +> Some organizations will re-enable the filter from time to time. If you repeatedly encounter app-id values missing, first check to see if the filter has been re-enabled before doing more extensive troubleshooting. diff --git a/daprdocs/content/en/reference/arguments-annotations-overview.md b/daprdocs/content/en/reference/arguments-annotations-overview.md index eec7f0c66..1a5dce0d4 100644 --- a/daprdocs/content/en/reference/arguments-annotations-overview.md +++ b/daprdocs/content/en/reference/arguments-annotations-overview.md @@ -12,33 +12,33 @@ This table is meant to help users understand the equivalent options for running | daprd | dapr CLI | CLI shorthand | K8s annotations | Description |----- | ------- | -----------| ----------| ------------ | -| `--allowed-origins` | not supported | | not supported | Allowed HTTP origins (default "*") | -| `--app-id` | `--app-id` | `-i` | `dapr.io/app-id` | The unique ID of the application. Used for service discovery, state encapsulation and the pub/sub consumer ID | -| `--app-port` | `--app-port` | `-p` | `dapr.io/app-port` | This parameter tells Dapr which port your application is listening on | +| `--allowed-origins` | not supported | | not supported | Allowed HTTP origins (default "*") | +| `--app-id` | `--app-id` | `-i` | `dapr.io/app-id` | The unique ID of the application. Used for service discovery, state encapsulation and the pub/sub consumer ID | +| `--app-port` | `--app-port` | `-p` | `dapr.io/app-port` | This parameter tells Dapr which port your application is listening on | | `--app-ssl` | `--app-ssl` | | `dapr.io/app-ssl` | Sets the URI scheme of the app to https and attempts an SSL connection | -| `--components-path` | `--components-path` | `-d` | not supported | Path for components directory. If empty, components will not be loaded. | -| `--config` | `--config` | `-c` | `dapr.io/config` | Tells Dapr which Configuration CRD to use | -| `--control-plane-address` | not supported | | not supported | Address for a Dapr control plane | -| `--dapr-grpc-port` | `--dapr-grpc-port` | | not supported | gRPC port for the Dapr API to listen on (default "50001") | -| `--dapr-http-port` | `--dapr-http-port` | | not supported | The HTTP port for the Dapr API | -|` --dapr-http-max-request-size` | --dapr-http-max-request-size | | `dapr.io/http-max-request-size` | Increasing max size of request body http and grpc servers parameter in MB to handle uploading of big files. Default is `4` MB | -| not supported | `--image` | | not supported -| `--internal-grpc-port` | not supported | | not supported | gRPC port for the Dapr Internal API to listen on | -| `--enable-metrics` | not supported | | configuration spec | Enable prometheus metric (default true) | -| `--enable-mtls` | not supported | | configuration spec | Enables automatic mTLS for daprd to daprd communication channels | -| `--enable-profiling` | `--enable-profiling` | | `dapr.io/enable-profiling` | Enable profiling | -| `--log-as-json` | not supported | | `dapr.io/log-as-json` | Setting this parameter to `true` outputs logs in JSON format. Default is `false` | -| `--log-level` | `--log-level` | | `dapr.io/log-level` | Sets the log level for the Dapr sidecar. Allowed values are `debug`, `info`, `warn`, `error`. Default is `info` | +| `--components-path` | `--components-path` | `-d` | not supported | Path for components directory. If empty, components will not be loaded. | +| `--config` | `--config` | `-c` | `dapr.io/config` | Tells Dapr which Configuration CRD to use | +| `--control-plane-address` | not supported | | not supported | Address for a Dapr control plane | +| `--dapr-grpc-port` | `--dapr-grpc-port` | | not supported | gRPC port for the Dapr API to listen on (default "50001") | +| `--dapr-http-port` | `--dapr-http-port` | | not supported | The HTTP port for the Dapr API | +|` --dapr-http-max-request-size` | --dapr-http-max-request-size | | `dapr.io/http-max-request-size` | Increasing max size of request body http and grpc servers parameter in MB to handle uploading of big files. Default is `4` MB | +| not supported | `--image` | | not supported +| `--internal-grpc-port` | not supported | | not supported | gRPC port for the Dapr Internal API to listen on | +| `--enable-metrics` | not supported | | configuration spec | Enable prometheus metric (default true) | +| `--enable-mtls` | not supported | | configuration spec | Enables automatic mTLS for daprd to daprd communication channels | +| `--enable-profiling` | `--enable-profiling` | | `dapr.io/enable-profiling` | Enable profiling | +| `--log-as-json` | not supported | | `dapr.io/log-as-json` | Setting this parameter to `true` outputs logs in JSON format. Default is `false` | +| `--log-level` | `--log-level` | | `dapr.io/log-level` | Sets the log level for the Dapr sidecar. Allowed values are `debug`, `info`, `warn`, `error`. Default is `info` | | `--app-max-concurrency` | `--app-max-concurrency` | | `dapr.io/app-max-concurrency` | Limit the concurrency of your application. A valid value is any number larger than `0` -| `--metrics-port` | `--metrics-port` | | `dapr.io/metrics-port` | Sets the port for the sidecar metrics server. Default is `9090` | -| `--mode` | not supported | | not supported | Runtime mode for Dapr (default "standalone") | -| `--placement-address` | `--placement-address` | | not supported | Addresses for Dapr Actor Placement servers | -| `--profiling-port` | `--profiling-port` | | not supported | The port for the profile server (default "7777") | -| `--app-protocol` | `--app-protocol` | `-P` | `dapr.io/app-protocol` | Tells Dapr which protocol your application is using. Valid options are `http` and `grpc`. Default is `http` | -| `--sentry-address` | `--sentry-address` | | not supported | Address for the Sentry CA service | -| `--version` | `--version` | `-v` | not supported | Prints the runtime version | -| not supported | not supported | | `dapr.io/enabled` | Setting this paramater to true injects the Dapr sidecar into the pod | -| not supported | not supported | | `dapr.io/api-token-secret` | Tells Dapr which Kubernetes secret to use for token based API authentication. By default this is not set | +| `--metrics-port` | `--metrics-port` | | `dapr.io/metrics-port` | Sets the port for the sidecar metrics server. Default is `9090` | +| `--mode` | not supported | | not supported | Runtime mode for Dapr (default "standalone") | +| `--placement-address` | `--placement-address` | | not supported | Addresses for Dapr Actor Placement servers | +| `--profiling-port` | `--profiling-port` | | not supported | The port for the profile server (default "7777") | +| `--app-protocol` | `--app-protocol` | `-P` | `dapr.io/app-protocol` | Tells Dapr which protocol your application is using. Valid options are `http` and `grpc`. Default is `http` | +| `--sentry-address` | `--sentry-address` | | not supported | Address for the Sentry CA service | +| `--version` | `--version` | `-v` | not supported | Prints the runtime version | +| not supported | not supported | | `dapr.io/enabled` | Setting this paramater to true injects the Dapr sidecar into the pod | +| not supported | not supported | | `dapr.io/api-token-secret` | Tells Dapr which Kubernetes secret to use for token based API authentication. By default this is not set | | not supported | not supported | | `dapr.io/sidecar-cpu-limit` | Maximum amount of CPU that the Dapr sidecar can use. See valid values [here](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/). By default this is not set | not supported | not supported | | `dapr.io/sidecar-memory-limit` | Maximum amount of Memory that the Dapr sidecar can use. See valid values [here](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/). By default this is not set | not supported | not supported | | `dapr.io/sidecar-cpu-request` | Amount of CPU that the Dapr sidecar requests. See valid values [here](https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/quota-memory-cpu-namespace/). By default this is not set diff --git a/daprdocs/content/en/reference/cli/cli-overview.md b/daprdocs/content/en/reference/cli/cli-overview.md index db45856d6..8e19ef8d6 100644 --- a/daprdocs/content/en/reference/cli/cli-overview.md +++ b/daprdocs/content/en/reference/cli/cli-overview.md @@ -52,7 +52,7 @@ Use "dapr [command] --help" for more information about a command. ## Command Reference -You can learn more about each Dapr command from the links below. +You can learn more about each Dapr command from the links below. - [`dapr build-info`]({{< ref dapr-build-info.md >}}) - [`dapr completion`]({{< ref dapr-completion.md >}}) diff --git a/daprdocs/content/en/reference/cli/dapr-invoke.md b/daprdocs/content/en/reference/cli/dapr-invoke.md index 081bc83aa..9a471f769 100644 --- a/daprdocs/content/en/reference/cli/dapr-invoke.md +++ b/daprdocs/content/en/reference/cli/dapr-invoke.md @@ -26,7 +26,7 @@ dapr invoke [flags] | `--help`, `-h` | | | Print this help message | | `--method`, `-m` | | | The method to invoke | | `--data`, `-d` | | | The JSON serialized data string (optional) | -| `--data-file`, `-f` | | | A file containing the JSON serialized data (optional) +| `--data-file`, `-f` | | | A file containing the JSON serialized data (optional) | `--verb`, `-v` | | `POST` | The HTTP verb to use | ## Examples diff --git a/daprdocs/content/en/reference/cli/dapr-upgrade.md b/daprdocs/content/en/reference/cli/dapr-upgrade.md index f9135ca76..6cc434569 100644 --- a/daprdocs/content/en/reference/cli/dapr-upgrade.md +++ b/daprdocs/content/en/reference/cli/dapr-upgrade.md @@ -7,7 +7,7 @@ description: "Detailed information on the upgrade CLI command" ## Description -Upgrade or downgrade Dapr on supported hosting platforms. +Upgrade or downgrade Dapr on supported hosting platforms. {{% alert title="Warning" color="warning" %}} Version steps should be done incrementally, including minor versions as you upgrade or downgrade. diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/_index.md b/daprdocs/content/en/reference/components-reference/supported-bindings/_index.md index 09bb9ddae..f03ddfd04 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/_index.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/_index.md @@ -82,7 +82,7 @@ Table captions: ### Zeebe (Camunda Cloud) -| Name | Input
Binding | Output
Binding | Status | Component version | Since | +| Name | Input
Binding | Output
Binding | Status | Component version | Since | |------|:----------------:|:-----------------:|--------| --------- | ---------- | | [Zeebe Command]({{< ref zeebe-command.md >}}) | | ✅ | Alpha | v1 | 1.2 | | [Zeebe Job Worker]({{< ref zeebe-jobworker.md >}}) | ✅ | | Alpha | v1 | 1.2 | diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/graghql.md b/daprdocs/content/en/reference/components-reference/supported-bindings/graghql.md index 74cf9e368..7c202a297 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/graghql.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/graghql.md @@ -22,7 +22,7 @@ spec: version: v1 metadata: - name: endpoint - value: http://localhost:8080/v1/graphql + value: http://localhost:8080/v1/graphql - name: header:x-hasura-access-key value: adminkey - name: header:Cache-Control diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-command.md b/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-command.md index d8a228d57..7415ffaec 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-command.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-command.md @@ -35,10 +35,10 @@ spec: | Field | Required | Binding support | Details | Example | |-------------------------|:--------:|------------|-----|---------| -| gatewayAddr | Y | Output | Zeebe gateway address | `localhost:26500` | -| gatewayKeepAlive | N | Output | Sets how often keep alive messages should be sent to the gateway. Defaults to 45 seconds | `45s` | -| usePlainTextConnection | N | Output | Whether to use a plain text connection or not | `true,false` | -| caCertificatePath | N | Output | The path to the CA cert | `/path/to/ca-cert` | +| gatewayAddr | Y | Output | Zeebe gateway address | `localhost:26500` | +| gatewayKeepAlive | N | Output | Sets how often keep alive messages should be sent to the gateway. Defaults to 45 seconds | `45s` | +| usePlainTextConnection | N | Output | Whether to use a plain text connection or not | `true,false` | +| caCertificatePath | N | Output | The path to the CA cert | `/path/to/ca-cert` | ## Binding support @@ -59,7 +59,7 @@ This component supports **output binding** with the following operations: ### Output binding -Zeebe uses gRPC under the hood for the Zeebe client we use in this binding. Please consult the [gRPC API reference](https://stage.docs.zeebe.io/reference/grpc.html) for more information. +Zeebe uses gRPC under the hood for the Zeebe client we use in this binding. Please consult the [gRPC API reference](https://stage.docs.zeebe.io/reference/grpc.html) for more information. #### topology @@ -161,7 +161,7 @@ The response values are: - `key` - the unique key identifying the deployment - `processes` - a list of deployed processes - - `bpmnProcessId` - the bpmn process ID, as parsed during deployment; together with the version forms a unique identifier for a specific + - `bpmnProcessId` - the bpmn process ID, as parsed during deployment; together with the version forms a unique identifier for a specific process definition - `version` - the assigned process version - `processDefinitionKey` - the assigned key, which acts as a unique identifier for this process @@ -169,7 +169,7 @@ The response values are: #### create-instance -The `create-instance` operation creates and starts an instance of the specified process. The process definition to use to create the instance can be +The `create-instance` operation creates and starts an instance of the specified process. The process definition to use to create the instance can be specified either using its unique key (as returned by the `deploy-process` operation), or using the BPMN process ID and a version. Note that only processes with none start events can be started through this command. @@ -296,7 +296,7 @@ To perform a `set-variables` operation, invoke the Zeebe command binding with a The data parameters are: -- `elementInstanceKey` - the unique identifier of a particular element; can be the process instance key (as +- `elementInstanceKey` - the unique identifier of a particular element; can be the process instance key (as obtained during instance creation), or a given element, such as a service task (see elementInstanceKey on the job message) - `local` - (optional, default: `false`) if true, the variables will be merged strictly into the local scope (as indicated by elementInstanceKey); this means the variables is not propagated to upper scopes. @@ -369,7 +369,7 @@ The data parameters are: - `messageName` - the name of the message - `correlationKey` - (optional) the correlation key of the message - `timeToLive` - (optional) how long the message should be buffered on the broker -- `messageId` - (optional) the unique ID of the message; can be omitted. only useful to ensure only one message with the given ID will ever +- `messageId` - (optional) the unique ID of the message; can be omitted. only useful to ensure only one message with the given ID will ever be published (during its lifetime) - `variables` - (optional) the message variables as a JSON document; to be valid, the root of the document must be an object, e.g. { "a": "foo" }. [ "foo" ] would not be valid @@ -390,7 +390,7 @@ The response values are: #### activate-jobs -The `activate-jobs` operation iterates through all known partitions round-robin and activates up to the requested maximum and streams them back to +The `activate-jobs` operation iterates through all known partitions round-robin and activates up to the requested maximum and streams them back to the client as they are activated. To perform a `activate-jobs` operation, invoke the Zeebe command binding with a `POST` method, and the following JSON body: @@ -419,7 +419,7 @@ The data parameters are: - `maxJobsToActivate` - the maximum jobs to activate by this request - `timeout` - (optional, default: 5 minutes) a job returned after this call will not be activated by another call until the timeout has been reached - `workerName` - (optional, default: `default`) the name of the worker activating the jobs, mostly used for logging purposes -- `fetchVariables` - (optional) a list of variables to fetch as the job variables; if empty, all visible variables at the time of activation for the +- `fetchVariables` - (optional) a list of variables to fetch as the job variables; if empty, all visible variables at the time of activation for the scope of the job will be returned ##### Response @@ -429,7 +429,7 @@ The binding returns a JSON with the following response: ```json [ { - + } ] ``` @@ -482,8 +482,8 @@ The binding does not return a response body. #### fail-job -The `fail-job` operation marks the job as failed; if the retries argument is positive, then the job will be immediately activatable again, and a -worker could try again to process it. If it is zero or negative however, an incident will be raised, tagged with the given errorMessage, and the +The `fail-job` operation marks the job as failed; if the retries argument is positive, then the job will be immediately activatable again, and a +worker could try again to process it. If it is zero or negative however, an incident will be raised, tagged with the given errorMessage, and the job will not be activatable until the incident is resolved. To perform a `fail-job` operation, invoke the Zeebe command binding with a `POST` method, and the following JSON body: @@ -504,7 +504,7 @@ The data parameters are: - `jobKey` - the unique job identifier, as obtained when activating the job - `retries` - the amount of retries the job should have left -- `errorMessage ` - (optional) an message describing why the job failed this is particularly useful if a job runs out of retries and an +- `errorMessage ` - (optional) an message describing why the job failed this is particularly useful if a job runs out of retries and an incident is raised, as it this message can help explain why an incident was raised ##### Response @@ -513,7 +513,7 @@ The binding does not return a response body. #### update-job-retries -The `update-job-retries` operation updates the number of retries a job has left. This is mostly useful for jobs that have run out of retries, should the +The `update-job-retries` operation updates the number of retries a job has left. This is mostly useful for jobs that have run out of retries, should the underlying problem be solved. To perform a `update-job-retries` operation, invoke the Zeebe command binding with a `POST` method, and the following JSON body: @@ -540,7 +540,7 @@ The binding does not return a response body. #### throw-error -The `throw-error` operation throw an error to indicate that a business error is occurred while processing the job. The error is identified +The `throw-error` operation throw an error to indicate that a business error is occurred while processing the job. The error is identified by an error code and is handled by an error catch event in the process with the same error code. To perform a `throw-error` operation, invoke the Zeebe command binding with a `POST` method, and the following JSON body: diff --git a/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-jobworker.md b/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-jobworker.md index 2904f67c2..a11eb58ef 100644 --- a/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-jobworker.md +++ b/daprdocs/content/en/reference/components-reference/supported-bindings/zeebe-jobworker.md @@ -53,19 +53,19 @@ spec: | Field | Required | Binding support | Details | Example | |-------------------------|:--------:|------------|-----|---------| -| gatewayAddr | Y | Input | Zeebe gateway address | `localhost:26500` | -| gatewayKeepAlive | N | Input | Sets how often keep alive messages should be sent to the gateway. Defaults to 45 seconds | `45s` | -| usePlainTextConnection | N | Input | Whether to use a plain text connection or not | `true,false` | -| caCertificatePath | N | Input | The path to the CA cert | `/path/to/ca-cert` | -| workerName | N | Input | The name of the worker activating the jobs, mostly used for logging purposes | `products-worker` | -| workerTimeout | N | Input | A job returned after this call will not be activated by another call until the timeout has been reached; defaults to 5 minutes | `5m` | -| requestTimeout | N | Input | The request will be completed when at least one job is activated or after the requestTimeout. If the requestTimeout = 0, a default timeout is used. If the requestTimeout < 0, long polling is disabled and the request is completed immediately, even when no job is activated. Defaults to 10 seconds | `30s` | -| jobType | Y | Input | the job type, as defined in the BPMN process (e.g. ``) | `fetch-products` | -| maxJobsActive | N | Input | Set the maximum number of jobs which will be activated for this worker at the same time. Defaults to 32 | `32` | -| concurrency | N | Input | The maximum number of concurrent spawned goroutines to complete jobs. Defaults to 4 | `4` | -| pollInterval | N | Input | Set the maximal interval between polling for new jobs. Defaults to 100 milliseconds | `100ms` | -| pollThreshold | N | Input | Set the threshold of buffered activated jobs before polling for new jobs, i.e. threshold * maxJobsActive. Defaults to 0.3 | `0.3` | -| fetchVariables | N | Input | A list of variables to fetch as the job variables; if empty, all visible variables at the time of activation for the scope of the job will be returned | `productId, productName, productKey` | +| gatewayAddr | Y | Input | Zeebe gateway address | `localhost:26500` | +| gatewayKeepAlive | N | Input | Sets how often keep alive messages should be sent to the gateway. Defaults to 45 seconds | `45s` | +| usePlainTextConnection | N | Input | Whether to use a plain text connection or not | `true,false` | +| caCertificatePath | N | Input | The path to the CA cert | `/path/to/ca-cert` | +| workerName | N | Input | The name of the worker activating the jobs, mostly used for logging purposes | `products-worker` | +| workerTimeout | N | Input | A job returned after this call will not be activated by another call until the timeout has been reached; defaults to 5 minutes | `5m` | +| requestTimeout | N | Input | The request will be completed when at least one job is activated or after the requestTimeout. If the requestTimeout = 0, a default timeout is used. If the requestTimeout < 0, long polling is disabled and the request is completed immediately, even when no job is activated. Defaults to 10 seconds | `30s` | +| jobType | Y | Input | the job type, as defined in the BPMN process (e.g. ``) | `fetch-products` | +| maxJobsActive | N | Input | Set the maximum number of jobs which will be activated for this worker at the same time. Defaults to 32 | `32` | +| concurrency | N | Input | The maximum number of concurrent spawned goroutines to complete jobs. Defaults to 4 | `4` | +| pollInterval | N | Input | Set the maximal interval between polling for new jobs. Defaults to 100 milliseconds | `100ms` | +| pollThreshold | N | Input | Set the threshold of buffered activated jobs before polling for new jobs, i.e. threshold * maxJobsActive. Defaults to 0.3 | `0.3` | +| fetchVariables | N | Input | A list of variables to fetch as the job variables; if empty, all visible variables at the time of activation for the scope of the job will be returned | `productId, productName, productKey` | ## Binding support @@ -75,10 +75,10 @@ This component supports **input** binding interfaces. #### Variables -The Zeebe process engine handles the process state as also process variables which can be passed +The Zeebe process engine handles the process state as also process variables which can be passed on process instantiation or which can be updated or created during process execution. These variables can be passed to a registered job worker by defining the variable names as comma-separated list in -the `fetchVariables` metadata field. The process engine will then pass these variables with its current +the `fetchVariables` metadata field. The process engine will then pass these variables with its current values to the job worker implementation. If the binding will register three variables `productId`, `productName` and `productKey` then the worker will @@ -86,9 +86,9 @@ be called with the following JSON body: ```json { - "productId": "some-product-id", - "productName": "some-product-name", - "productKey": "some-product-key" + "productId": "some-product-id", + "productName": "some-product-name", + "productKey": "some-product-key" } ``` diff --git a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md index 54b042284..f272130d6 100644 --- a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md +++ b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-opa.md @@ -75,7 +75,7 @@ You can prototype and experiment with policies using the [official opa playgroun |--------|---------|---------| | rego | The Rego policy language | See above | | defaultStatus | The status code to return for denied responses | `"https://accounts.google.com"`, `"https://login.salesforce.com"` -| includedHeaders | A comma-separated set of case-insensitive headers to include in the request input. Request headers are not passed to the policy by default. Include to receive incoming request headers in the input | `"x-my-custom-header, x-jwt-header"` +| includedHeaders | A comma-separated set of case-insensitive headers to include in the request input. Request headers are not passed to the policy by default. Include to receive incoming request headers in the input | `"x-my-custom-header, x-jwt-header"` ## Dapr configuration diff --git a/daprdocs/content/en/reference/components-reference/supported-name-resolution/setup-nr-consul.md b/daprdocs/content/en/reference/components-reference/supported-name-resolution/setup-nr-consul.md index 1959ab713..83713aeff 100644 --- a/daprdocs/content/en/reference/components-reference/supported-name-resolution/setup-nr-consul.md +++ b/daprdocs/content/en/reference/components-reference/supported-name-resolution/setup-nr-consul.md @@ -97,7 +97,7 @@ spec: meta: DAPR_METRICS_PORT: "${DAPR_METRICS_PORT}" DAPR_PROFILE_PORT: "${DAPR_PROFILE_PORT}" - daprPortMetaKey: "DAPR_PORT" + daprPortMetaKey: "DAPR_PORT" queryOptions: useCache: true filter: "Checks.ServiceTags contains dapr" diff --git a/daprdocs/content/en/reference/components-reference/supported-secret-stores/kubernetes-secret-store.md b/daprdocs/content/en/reference/components-reference/supported-secret-stores/kubernetes-secret-store.md index 50ac43c90..a081668c9 100644 --- a/daprdocs/content/en/reference/components-reference/supported-secret-stores/kubernetes-secret-store.md +++ b/daprdocs/content/en/reference/components-reference/supported-secret-stores/kubernetes-secret-store.md @@ -8,7 +8,7 @@ aliases: --- ## Default Kubernetes secret store component -When Dapr is deployed to a Kubernetes cluster, a secret store with the name `kubernetes` is automatically provisioned. This pre-provisioned secret store allows you to use the native Kubernetes secret store with no need to author, deploy or maintain a component configuration file for the secret store and is useful for developers looking to simply access secrets stored natively in a Kubernetes cluster. +When Dapr is deployed to a Kubernetes cluster, a secret store with the name `kubernetes` is automatically provisioned. This pre-provisioned secret store allows you to use the native Kubernetes secret store with no need to author, deploy or maintain a component configuration file for the secret store and is useful for developers looking to simply access secrets stored natively in a Kubernetes cluster. A custom component definition file for a Kubernetes secret store can still be configured (See below for details). Using a custom definition decouples referencing the secret store in your code from the hosting platform as the store name is not fixed and can be customized, keeping you code more generic and portable. Additionally, by explicitly defining a Kubernetes secret store component you can connect to a Kubernetes secret store from a local Dapr self-hosted installation. This requires a valid [`kubeconfig`](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/) file. diff --git a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-mongodb.md b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-mongodb.md index d3b4001a6..5e97b5438 100644 --- a/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-mongodb.md +++ b/daprdocs/content/en/reference/components-reference/supported-state-stores/setup-mongodb.md @@ -83,7 +83,7 @@ docker run --name some-mongo -d mongo You can then interact with the server using `localhost:27017`. -If you do not specify a `databaseName` value in your component definition, make sure to create a database named `daprStore`. +If you do not specify a `databaseName` value in your component definition, make sure to create a database named `daprStore`. {{% /codetab %}}