Why do I get 'sentinel key is not provided in metadata' error when using Azure App Configuration as dapr config store component?

Question

I have a question concerning the dapr config store component.

I'm trying to use the config store component in an Azure container app. I have it configured in a bicep file like so:

resource daprConfigComponent 'Microsoft.App/managedEnvironments/daprComponents@2022-11-01-preview' = {
  name: 'configstore' 
  parent: environment
  properties: {
    componentType: 'configuration.azure.appconfig'
    version: 'v1'
    metadata: [
      {
        name: 'connectionString'
        value: '<connection-string-here>'
      }
    ]
    scopes: [
      'nativevoice'
    ]
  }
}

It seems to be working fine and daprd gives no errors, however when I run my container app it gives the following error:

Grpc.Core.RpcException: Status(StatusCode="InvalidArgument", Detail="failed to subscribe [orderId1 orderId2] from Configuration store configstore: azure appconfig error: sentinel key is not provided in metadata")

It seems that dapr doesn't work with Azure app configuration despite the fact I followed this documentation: https://docs.dapr.io/reference/components-reference/supported-configuration-stores/azure-appconfig-configuration-store/.

Anyone have any idea on how to fix this?

Bret Boss · Accepted Answer · 2023-05-31 01:49:08Z

0

If you are using AddStreamingDaprConfigurationStore then you'll need to add metadata with a key of "sentinelKey" and a value of whatever configuration key you want to trigger a reload of configuration values.

Example:

var configMeta = new Dictionary<string, string>() { ["sentinelKey"] = reloadConfigKey };
manager.AddStreamingDaprConfigurationStore(configStore, configKeys, daprClient, timeout, configMeta);

Source: https://github.com/dapr/components-contrib/blob/master/configuration/azure/appconfig/appconfig.go#L248

edited May 31, 2023 at 1:49

answered May 31, 2023 at 1:47

Bret Boss

443 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Blit · Accepted Answer · 2023-06-06 11:35:15Z

0

@Brett Boss answer resolved the issue, I had to add sentinelKey to the metadata. I use the .NET Dapr SDK so for me it looked like this:

Dapr.Client.SubscribeConfigurationResponse subscribe = await _daprClient.SubscribeConfiguration(
            DAPR_CONFIGURATION_STORE, 
            CONFIGURATION_KEYS, 
            new Dictionary<string, string>
            {
                { "sentinelKey", "reloadConfigKey"}
            }, stoppingToken);

edited Jun 6, 2023 at 11:35

answered Jun 6, 2023 at 11:34

Blit

556 bronze badges

1 Comment

Rom Eh Over a year ago

Good answer. To improve the answer, a link to the .NET Dapr SDK would have been great.

Collectives™ on Stack Overflow

Why do I get 'sentinel key is not provided in metadata' error when using Azure App Configuration as dapr config store component?

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related