-It is worth noting that this configuration API should not be confused with the [Dapr sidecar and control plane configuration]({{
+
{{% alert title="Note" color="primary" %}}
-This API is currently in `Alpha` state and only available on gRPC. An HTTP1.1 supported version with this URL syntax `/v1.0/configuration` will be available before the API is certified into `Stable` state.
+ If you haven't already, [try out the configuration quickstart]({{< ref configuration-quickstart.md >}}) for a quick walk-through on how to use the configuration API.
{{% /alert %}}
-
## Create a configuration item in store
@@ -68,7 +69,7 @@ spec:
## Retrieve Configuration Items
### Get configuration items using Dapr SDKs
-{{< tabs Dotnet Java Python>}}
+{{< tabs ".NET" Java Python>}}
{{% codetab %}}
diff --git a/daprdocs/content/en/developing-applications/building-blocks/observability/tracing-overview.md b/daprdocs/content/en/developing-applications/building-blocks/observability/tracing-overview.md
index eb758b335..38ac85d25 100644
--- a/daprdocs/content/en/developing-applications/building-blocks/observability/tracing-overview.md
+++ b/daprdocs/content/en/developing-applications/building-blocks/observability/tracing-overview.md
@@ -18,7 +18,7 @@ There are two scenarios for how tracing is used:
1. Dapr generates the trace context and you propagate the trace context to another service.
2. You generate the trace context and Dapr propagates the trace context to a service.
-### Propogating sequential service calls
+### Propagating sequential service calls
Dapr takes care of creating the trace headers. However, when there are more than two services, you're responsible for propagating the trace headers between them. Let's go through the scenarios with examples:
@@ -45,7 +45,7 @@ There are no helper methods exposed in Dapr SDKs to propagate and retrieve trace
4. Pub/sub messages
Dapr generates the trace headers in the published message topic. These trace headers are propagated to any services listening on that topic.
-### Propogating multiple different service calls
+### Propagating multiple different service calls
In the following scenarios, Dapr does some of the work for you and you need to either create or propagate trace headers.
@@ -115,4 +115,4 @@ In the gRPC API calls, trace context is passed through `grpc-trace-bin` header.
- [Observability concepts]({{< ref observability-concept.md >}})
- [W3C Trace Context for distributed tracing]({{< ref w3c-tracing-overview >}})
- [W3C Trace Context specification](https://www.w3.org/TR/trace-context/)
-- [Observability quickstart](https://github.com/dapr/quickstarts/tree/master/tutorials/observability)
\ No newline at end of file
+- [Observability quickstart](https://github.com/dapr/quickstarts/tree/master/tutorials/observability)
diff --git a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-state-query-api.md b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-state-query-api.md
index 209eda9d0..6b321d34d 100644
--- a/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-state-query-api.md
+++ b/daprdocs/content/en/developing-applications/building-blocks/state-management/howto-state-query-api.md
@@ -16,7 +16,7 @@ Even though the state store is a key/value store, the `value` might be a JSON do
## Querying the state
-Submit query requests via HTTP POST/PUT or gRPC. The body of the request is the JSON map with 3 _optional_ entries:
+Submit query requests via HTTP POST/PUT or gRPC. The body of the request is the JSON map with 3 entries:
- `filter`
- `sort`
diff --git a/daprdocs/content/en/getting-started/install-dapr-cli.md b/daprdocs/content/en/getting-started/install-dapr-cli.md
index 258ff34e0..4c8d39880 100644
--- a/daprdocs/content/en/getting-started/install-dapr-cli.md
+++ b/daprdocs/content/en/getting-started/install-dapr-cli.md
@@ -188,6 +188,7 @@ Available Commands:
stop Stop Dapr instances and their associated apps. . Supported platforms: Self-hosted
uninstall Uninstall Dapr runtime. Supported platforms: Kubernetes and self-hosted
upgrade Upgrades a Dapr control plane installation in a cluster. Supported platforms: Kubernetes
+ version Print the Dapr runtime and CLI version
Flags:
-h, --help help for dapr
diff --git a/daprdocs/content/en/getting-started/quickstarts/_index.md b/daprdocs/content/en/getting-started/quickstarts/_index.md
index 67380fa87..727b9a17b 100644
--- a/daprdocs/content/en/getting-started/quickstarts/_index.md
+++ b/daprdocs/content/en/getting-started/quickstarts/_index.md
@@ -27,4 +27,5 @@ Hit the ground running with our Dapr quickstarts, complete with code samples aim
| [State Management]({{< ref statemanagement-quickstart.md >}}) | Store a service's data as key/value pairs in supported state stores. |
| [Bindings]({{< ref bindings-quickstart.md >}}) | Work with external systems using input bindings to respond to events and output bindings to call operations. |
| [Secrets Management]({{< ref secrets-quickstart.md >}}) | Securely fetch secrets. |
+| [Configuration]({{< ref configuration-quickstart.md >}}) | Get configuration items and subscribe for configuration updates. |
| [Resiliency]({{< ref resiliency >}}) | Define and apply fault-tolerance policies to your Dapr API requests. |
diff --git a/daprdocs/content/en/getting-started/quickstarts/bindings-quickstart.md b/daprdocs/content/en/getting-started/quickstarts/bindings-quickstart.md
index 4eef26f5c..b34f3985e 100644
--- a/daprdocs/content/en/getting-started/quickstarts/bindings-quickstart.md
+++ b/daprdocs/content/en/getting-started/quickstarts/bindings-quickstart.md
@@ -46,7 +46,7 @@ Run the [PostgreSQL instance](https://www.postgresql.org/) locally in a Docker c
In a terminal window, from the root of the Quickstarts clone directory, navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following command to set up the container:
@@ -73,7 +73,7 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS
In a new terminal window, navigate to the SDK directory.
```bash
-cd quickstarts/bindings/python/sdk/batch
+cd bindings/python/sdk/batch
```
Install the dependencies:
@@ -137,7 +137,7 @@ Your output binding's `print` statement output:
In a new terminal, verify the same data has been inserted into the database. Navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following to start the interactive Postgres CLI:
@@ -253,7 +253,7 @@ Run the [PostgreSQL instance](https://www.postgresql.org/) locally in a Docker c
In a terminal window, from the root of the Quickstarts clone directory, navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following command to set up the container:
@@ -280,7 +280,7 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS
In a new terminal window, navigate to the SDK directory.
```bash
-cd quickstarts/bindings/javascript/sdk/batch
+cd bindings/javascript/sdk/batch
```
Install the dependencies:
@@ -339,7 +339,7 @@ Your output binding's `print` statement output:
In a new terminal, verify the same data has been inserted into the database. Navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following to start the interactive Postgres CLI:
@@ -455,7 +455,7 @@ Run the [PostgreSQL instance](https://www.postgresql.org/) locally in a Docker c
In a terminal window, from the root of the Quickstarts clone directory, navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following command to set up the container:
@@ -482,7 +482,7 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS
In a new terminal window, navigate to the SDK directory.
```bash
-cd quickstarts/bindings/csharp/sdk/batch
+cd bindings/csharp/sdk/batch
```
Install the dependencies:
@@ -543,7 +543,7 @@ Your output binding's `print` statement output:
In a new terminal, verify the same data has been inserted into the database. Navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following to start the interactive Postgres CLI:
@@ -662,7 +662,7 @@ Run the [PostgreSQL instance](https://www.postgresql.org/) locally in a Docker c
In a terminal window, from the root of the Quickstarts clone directory, navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following command to set up the container:
@@ -689,7 +689,7 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS
In a new terminal window, navigate to the SDK directory.
```bash
-cd quickstarts/bindings/java/sdk/batch
+cd bindings/java/sdk/batch
```
Install the dependencies:
@@ -753,7 +753,7 @@ Your output binding's `print` statement output:
In a new terminal, verify the same data has been inserted into the database. Navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following to start the interactive Postgres CLI:
@@ -869,7 +869,7 @@ Run the [PostgreSQL instance](https://www.postgresql.org/) locally in a Docker c
In a terminal window, from the root of the Quickstarts clone directory, navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following command to set up the container:
@@ -896,7 +896,7 @@ CONTAINER ID IMAGE COMMAND CREATED STATUS
In a new terminal window, navigate to the SDK directory.
```bash
-cd quickstarts/bindings/go/sdk/batch
+cd bindings/go/sdk/batch
```
Install the dependencies:
@@ -965,7 +965,7 @@ Your output binding's `print` statement output:
In a new terminal, verify the same data has been inserted into the database. Navigate to the `bindings/db` directory.
```bash
-cd quickstarts/bindings/db
+cd bindings/db
```
Run the following to start the interactive Postgres CLI:
diff --git a/daprdocs/content/en/getting-started/quickstarts/configuration-quickstart.md b/daprdocs/content/en/getting-started/quickstarts/configuration-quickstart.md
new file mode 100644
index 000000000..e457612a1
--- /dev/null
+++ b/daprdocs/content/en/getting-started/quickstarts/configuration-quickstart.md
@@ -0,0 +1,639 @@
+---
+type: docs
+title: "Quickstart: Configuration"
+linkTitle: Configuration
+weight: 76
+description: Get started with Dapr's Configuration building block
+---
+
+Let's take a look at Dapr's [Configuration building block]({{< ref configuration-api-overview.md >}}). A configuration item is often dynamic in nature and tightly coupled to the needs of the application that consumes it. Configuration items are key/value pairs containing configuration data, such as:
+- App ids
+- Partition keys
+- Database names, etc
+
+In this quickstart, you'll run an `order-processor` microservice that utilizes the Configuration API. The service:
+1. Gets configuration items from the configuration store.
+1. Subscribes for configuration updates.
+
+
+
+Select your preferred language-specific Dapr SDK before proceeding with the Quickstart.
+
+{{< tabs "Python" "JavaScript" ".NET" "Java" "Go" >}}
+
+{{% codetab %}}
+
+### Pre-requisites
+
+For this example, you will need:
+
+- [Dapr CLI and initialized environment](https://docs.dapr.io/getting-started).
+- [Python 3.7+ installed](https://www.python.org/downloads/).
+
+- [Docker Desktop](https://www.docker.com/products/docker-desktop)
+
+
+### Step 1: Set up the environment
+
+Clone the [sample provided in the Quickstarts repo](https://github.com/dapr/quickstarts/tree/master/configuration).
+
+```bash
+git clone https://github.com/dapr/quickstarts.git
+```
+
+Once cloned, open a new terminal and run the following command to set values for configuration items `orderId1` and `orderId2`.
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "101" orderId2 "102"
+```
+
+### Step 2: Run the `order-processor` service
+
+From the root of the Quickstarts clone directory, navigate to the `order-processor` directory.
+
+```bash
+cd configuration/python/sdk/order-processor
+```
+
+Install the dependencies:
+
+```bash
+pip3 install -r requirements.txt
+```
+
+Run the `order-processor` service alongside a Dapr sidecar.
+
+```bash
+dapr run --app-id order-processor --components-path ../../../components/ --app-port 6001 -- python3 app.py
+```
+
+> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
+
+The expected output:
+
+```
+== APP == Configuration for orderId1 : value: "101"
+== APP ==
+== APP == Configuration for orderId2 : value: "102"
+== APP ==
+== APP == App unsubscribed from config changes
+```
+
+### (Optional) Step 3: Update configuration item values
+
+Once the app has unsubscribed, try updating the configuration item values. Change the `orderId1` and `orderId2` values using the following command:
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "103" orderId2 "104"
+```
+
+Run the `order-processor` service again:
+
+```bash
+dapr run --app-id order-processor --components-path ../../../components/ --app-port 6001 -- python3 app.py
+```
+
+> **Note**: Since Python3.exe is not defined in Windows, you may need to use `python app.py` instead of `python3 app.py`.
+
+The app will return the updated configuration values:
+
+```
+== APP == Configuration for orderId1 : value: "103"
+== APP ==
+== APP == Configuration for orderId2 : value: "104"
+== APP ==
+```
+
+### The `order-processor` service
+
+The `order-processor` service includes code for:
+- Getting the configuration items from the config store
+- Subscribing to configuration updates (which you made in the CLI earlier)
+- Unsubscribing from configuration updates and exiting the app after 20 seconds of inactivity.
+
+Get configuration items:
+
+```python
+# Get config items from the config store
+for config_item in CONFIGURATION_ITEMS:
+ config = client.get_configuration(store_name=DAPR_CONFIGURATION_STORE, keys=[config_item], config_metadata={})
+ print(f"Configuration for {config_item} : {config.items[config_item]}", flush=True)
+```
+
+Subscribe to configuration updates:
+
+```python
+# Subscribe for configuration changes
+configuration = await client.subscribe_configuration(DAPR_CONFIGURATION_STORE, CONFIGURATION_ITEMS)
+```
+
+Unsubscribe from configuration updates and exit the application:
+
+```python
+# Unsubscribe from configuration updates
+unsubscribed = True
+for config_item in CONFIGURATION_ITEMS:
+ unsub_item = client.unsubscribe_configuration(DAPR_CONFIGURATION_STORE, config_item)
+ #...
+if unsubscribed == True:
+ print("App unsubscribed from config changes", flush=True)
+```
+
+
+{{% /codetab %}}
+
+
+
+{{% codetab %}}
+
+### Pre-requisites
+
+For this example, you will need:
+
+- [Dapr CLI and initialized environment](https://docs.dapr.io/getting-started).
+- [Python 3.7+ installed](https://www.python.org/downloads/).
+
+- [Docker Desktop](https://www.docker.com/products/docker-desktop)
+
+
+### Step 1: Set up the environment
+
+Clone the [sample provided in the Quickstarts repo](https://github.com/dapr/quickstarts/tree/master/configuration).
+
+```bash
+git clone https://github.com/dapr/quickstarts.git
+```
+
+Once cloned, open a new terminal and run the following command to set values for configuration items `orderId1` and `orderId2`.
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "101" orderId2 "102"
+```
+
+### Step 2: Run the `order-processor` service
+
+From the root of the Quickstarts clone directory, navigate to the `order-processor` directory.
+
+```bash
+cd configuration/javascript/sdk/order-processor
+```
+
+Install the dependencies:
+
+```bash
+npm install
+```
+
+Run the `order-processor` service alongside a Dapr sidecar.
+
+```bash
+dapr run --app-id order-processor --components-path ../../../components/ --app-protocol grpc --dapr-grpc-port 3500 -- node index.js
+```
+
+The expected output:
+
+```
+== APP == Configuration for orderId1: {"key":"orderId1","value":"101","version":"","metadata":{}}
+== APP == Configuration for orderId2: {"key":"orderId2","value":"102","version":"","metadata":{}}
+== APP == App unsubscribed to config changes
+```
+
+### (Optional) Step 3: Update configuration item values
+
+Once the app has unsubscribed, try updating the configuration item values. Change the `orderId1` and `orderId2` values using the following command:
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "103" orderId2 "104"
+```
+
+Run the `order-processor` service again:
+
+```bash
+dapr run --app-id order-processor --components-path ../../../components/ --app-protocol grpc --dapr-grpc-port 3500 -- node index.js
+```
+
+The app will return the updated configuration values:
+
+```
+== APP == Configuration for orderId1: {"key":"orderId1","value":"103","version":"","metadata":{}}
+== APP == Configuration for orderId2: {"key":"orderId2","value":"104","version":"","metadata":{}}
+```
+
+### The `order-processor` service
+
+The `order-processor` service includes code for:
+- Getting the configuration items from the config store
+- Subscribing to configuration updates (which you made in the CLI earlier)
+- Unsubscribing from configuration updates and exiting the app after 20 seconds of inactivity.
+
+Get configuration items:
+
+```javascript
+// Get config items from the config store
+//...
+ const config = await client.configuration.get(DAPR_CONFIGURATION_STORE, CONFIGURATION_ITEMS);
+ Object.keys(config.items).forEach((key) => {
+ console.log("Configuration for " + key + ":", JSON.stringify(config.items[key]));
+ });
+```
+
+Subscribe to configuration updates:
+
+```javascript
+// Subscribe to config updates
+try {
+ const stream = await client.configuration.subscribeWithKeys(
+ DAPR_CONFIGURATION_STORE,
+ CONFIGURATION_ITEMS,
+ (config) => {
+ console.log("Configuration update", JSON.stringify(config.items));
+ }
+ );
+```
+
+Unsubscribe from configuration updates and exit the application:
+
+```javascript
+// Unsubscribe to config updates and exit app after 20 seconds
+setTimeout(() => {
+ stream.stop();
+ console.log("App unsubscribed to config changes");
+ process.exit(0);
+},
+```
+
+{{% /codetab %}}
+
+
+{{% codetab %}}
+
+### Pre-requisites
+
+For this example, you will need:
+
+- [Dapr CLI and initialized environment](https://docs.dapr.io/getting-started).
+- [.NET SDK or .NET 6 SDK installed](https://dotnet.microsoft.com/download).
+
+- [Docker Desktop](https://www.docker.com/products/docker-desktop)
+
+
+### Step 1: Set up the environment
+
+Clone the [sample provided in the Quickstarts repo](https://github.com/dapr/quickstarts/tree/master/configuration).
+
+```bash
+git clone https://github.com/dapr/quickstarts.git
+```
+
+Once cloned, open a new terminal and run the following command to set values for configuration items `orderId1` and `orderId2`.
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "101" orderId2 "102"
+```
+
+### Step 2: Run the `order-processor` service
+
+From the root of the Quickstarts clone directory, navigate to the `order-processor` directory.
+
+```bash
+cd configuration/csharp/sdk/order-processor
+```
+
+Recall NuGet packages:
+
+```bash
+dotnet restore
+dotnet build
+```
+
+Run the `order-processor` service alongside a Dapr sidecar.
+
+```bash
+dapr run --app-id order-processor-http --components-path ../../../components/ --app-port 7001 -- dotnet run --project .
+```
+
+The expected output:
+
+```
+== APP == Configuration for orderId1: {"Value":"101","Version":"","Metadata":{}}
+== APP == Configuration for orderId2: {"Value":"102","Version":"","Metadata":{}}
+== APP == App unsubscribed from config changes
+```
+
+### (Optional) Step 3: Update configuration item values
+
+Once the app has unsubscribed, try updating the configuration item values. Change the `orderId1` and `orderId2` values using the following command:
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "103" orderId2 "104"
+```
+
+Run the `order-processor` service again:
+
+```bash
+dapr run --app-id order-processor-http --components-path ../../../components/ --app-port 7001 -- dotnet run --project .
+```
+
+The app will return the updated configuration values:
+
+```
+== APP == Configuration for orderId1: {"Value":"103","Version":"","Metadata":{}}
+== APP == Configuration for orderId2: {"Value":"104","Version":"","Metadata":{}}
+```
+
+### The `order-processor` service
+
+The `order-processor` service includes code for:
+- Getting the configuration items from the config store
+- Subscribing to configuration updates (which you made in the CLI earlier)
+- Unsubscribing from configuration updates and exiting the app after 20 seconds of inactivity.
+
+Get configuration items:
+
+```csharp
+// Get config from configuration store
+GetConfigurationResponse config = await client.GetConfiguration(DAPR_CONFIGURATION_STORE, CONFIGURATION_ITEMS);
+foreach (var item in config.Items)
+{
+ var cfg = System.Text.Json.JsonSerializer.Serialize(item.Value);
+ Console.WriteLine("Configuration for " + item.Key + ": " + cfg);
+}
+```
+
+Subscribe to configuration updates:
+
+```csharp
+// Subscribe to config updates
+SubscribeConfigurationResponse subscribe = await client.SubscribeConfiguration(DAPR_CONFIGURATION_STORE, CONFIGURATION_ITEMS);
+```
+
+Unsubscribe from configuration updates and exit the application:
+
+```csharp
+// Unsubscribe to config updates and exit the app
+try
+{
+ client.UnsubscribeConfiguration(DAPR_CONFIGURATION_STORE, subscriptionId);
+ Console.WriteLine("App unsubscribed from config changes");
+ Environment.Exit(0);
+}
+```
+
+{{% /codetab %}}
+
+
+{{% codetab %}}
+
+### Pre-requisites
+
+For this example, you will need:
+
+- [Dapr CLI and initialized environment](https://docs.dapr.io/getting-started).
+- Java JDK 11 (or greater):
+ - [Oracle JDK](https://www.oracle.com/technetwork/java/javase/downloads/index.html#JDK11), or
+ - OpenJDK
+- [Apache Maven](https://maven.apache.org/install.html), version 3.x.
+
+- [Docker Desktop](https://www.docker.com/products/docker-desktop)
+
+
+### Step 1: Set up the environment
+
+Clone the [sample provided in the Quickstarts repo](https://github.com/dapr/quickstarts/tree/master/configuration).
+
+```bash
+git clone https://github.com/dapr/quickstarts.git
+```
+
+Once cloned, open a new terminal and run the following command to set values for configuration items `orderId1` and `orderId2`.
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "101" orderId2 "102"
+```
+
+### Step 2: Run the `order-processor` service
+
+From the root of the Quickstarts clone directory, navigate to the `order-processor` directory.
+
+```bash
+cd configuration/java/sdk/order-processor
+```
+
+Install the dependencies:
+
+```bash
+mvn clean install
+```
+
+Run the `order-processor` service alongside a Dapr sidecar.
+
+```bash
+dapr run --app-id order-processor --components-path ../../../components -- java -jar target/OrderProcessingService-0.0.1-SNAPSHOT.jar
+```
+
+The expected output:
+
+```
+== APP == Configuration for orderId1: {'value':'101'}
+== APP == Configuration for orderId2: {'value':'102'}
+== APP == App unsubscribed to config changes
+```
+
+### (Optional) Step 3: Update configuration item values
+
+Once the app has unsubscribed, try updating the configuration item values. Change the `orderId1` and `orderId2` values using the following command:
+
+```bash
+docker exec dapr_redis redis-cli MSET orderId1 "103" orderId2 "104"
+```
+
+Run the `order-processor` service again:
+
+```bash
+dapr run --app-id order-processor --components-path ../../../components -- java -jar target/OrderProcessingService-0.0.1-SNAPSHOT.jar
+```
+
+The app will return the updated configuration values:
+
+```
+== APP == Configuration for orderId1: {'value':'103'}
+== APP == Configuration for orderId2: {'value':'104'}
+```
+
+### The `order-processor` service
+
+The `order-processor` service includes code for:
+- Getting the configuration items from the config store
+- Subscribing to configuration updates (which you made in the CLI earlier)
+- Unsubscribing from configuration updates and exiting the app after 20 seconds of inactivity.
+
+Get configuration items:
+
+```java
+// Get config items from the config store
+try (DaprPreviewClient client = (new DaprClientBuilder()).buildPreviewClient()) {
+ for (String configurationItem : CONFIGURATION_ITEMS) {
+ ConfigurationItem item = client.getConfiguration(DAPR_CONFIGURATON_STORE, configurationItem).block();
+ System.out.println("Configuration for " + configurationItem + ": {'value':'" + item.getValue() + "'}");
+ }
+```
+
+Subscribe to configuration updates:
+
+```java
+// Subscribe for config changes
+Flux
+ {{ end }}
+
+ {{ end }}
{{ end }}{{ end }}Table captions:
-+
Status: Component - certification status
Status: component certification status
-+
Since: defines from which Dapr Runtime version, the component is in the current status
Since: the version of the Dapr Runtime in which the component first moved to the current status
-diff --git a/daprdocs/layouts/partials/components/locks.html b/daprdocs/layouts/partials/components/locks.html index 4039e5eb0..109ba9ec8 100644 --- a/daprdocs/layouts/partials/components/locks.html +++ b/daprdocs/layouts/partials/components/locks.html @@ -13,8 +13,7 @@+
Component version: defines the version of the component
Component version: the version of the component
+ {{ end }}
{{ end }}
+ {{ end }}
+
+ {{ end }}
+
+ {{ end }}
+
+ {{ end }}
+
+ {{ end }}
+
+ {{ end }}
{{ end }}{{ end }}{{ end }}{{ end }}{{ end }}{{ end }}