How-To: Enable preview features

Preview features in Dapr are considered experimental when they are first released. These preview features require explicit opt-in in order to be used. The opt-in is specified in Dapr’s configuration.

Preview features are enabled on a per application basis by setting configuration when running an application instance.

The current list of preview features can be found here.

Preview features are specified in the configuration. Here is an example of a full configuration that contains multiple features:

To enable preview features when running Dapr locally, either update the default configuration or specify a separate config file using dapr run.

The default Dapr config is created when you run , and is located at:

• Windows: %USERPROFILE%\.dapr\config.yaml
• Linux/macOS: ~/.dapr/config.yaml

In Kubernetes mode, the configuration must be provided via a configuration component. Using the same configuration as above, apply it via kubectl:

This configuration component can then be referenced in any application by modifying the application’s configuration to reference that specific configuration component via the element. For example: