Configuration overview

Mon, 01 Jan 0001 00:00:00 +0000

Consuming application configuration is a common task when writing applications. Frequently, configuration stores are used to manage this configuration data. A configuration item is often dynamic in nature and tightly coupled to the needs of the application that consumes it.

For example, application configuration can include:

Names of secrets
Different identifiers
Partition or consumer IDs
Names of databases to connect to, etc

Usually, configuration items are stored as key/value items in a state store or database. Developers or operators can change application configuration at runtime in the configuration store. Once changes are made, a service is notified to load the new configuration.

How-To: Manage configuration from a store

Mon, 01 Jan 0001 00:00:00 +0000

This example uses the Redis configuration store component to demonstrate how to retrieve a configuration item.

Note

If you haven’t already, try out the configuration quickstart for a quick walk-through on how to use the configuration API.

Disabling configuration initialization endpoint

If your application does not use the configuration building block, the automatic HTTP call to the /dapr/config endpoint during initialization can be disabled to reduce log noise. Use the --disable-init-endpoints config flag with dapr run, or the dapr.io/disable-init-endpoints: "config" annotation in Kubernetes. Learn more about disabling initialization endpoints.

Create a configuration item in store

Create a configuration item in a supported configuration store. This can be a simple key-value item, with any key of your choice. As mentioned earlier, this example uses the Redis configuration store component.

Configuration on Dapr Docs

Configuration overview

How-To: Manage configuration from a store

Note

Disabling configuration initialization endpoint

Create a configuration item in store