Not all KeyValueSelectors get refreshed after sentinel key changed

Open
#953 5 comments 0 reactions 1 assignee View on GitHub

@amerjusupovic is already working on this.

Since Aug 30, 2024.

Assessment

This issue has not been assessed yet.

Description

.NET Config Provider question

Followed https://learn.microsoft.com/en-us/azure/azure-app-configuration/enable-dynamic-configuration-aspnet-core We are using poll model for dynamic configuration

As the screenshot shows, we set three sentinel keys service:testService:sentinel, shared:testService:sentinel and shared:config:sentinel, and set RefreshAll as true for all sentinel keys.
Three KeyValueSelectors are shared:testService:*, service:testService:* and shared:config:*
Suppose any sentinel value change should trigger the service instance refresh all registered configurations.

image

But we noticed when we update configuration values and sentinel values, some KeyValueSelectors get refreshed but some are not. Service still retrieving the old values even 2 days later. We have to restart the service to ensure all configurations are refreshed.

Suppose all selected configuration values should be refreshed in minutes, could you please confirm if the case is normal? How should we ensure selected configuration values get refreshed after configuration change?

SDK version: 6.1.1

Dominant language
No language data
Stars
263
Forks
82
Avg merge
3d 15h
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/AppConfiguration

All issues in Azure/AppConfiguration

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.