Azure / Azure/AppConfiguration

Not all KeyValueSelectors get refreshed after sentinel key changed

Open
#953 5 comments 0 reactions 1 assignee Claimed by @amerjusupovic View on GitHub
.NET Config Provider question
Dominant language
No language data
Stars
263
Forks
82
Avg merge
3d 15h
Merged PRs (30d)
6

Description

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](https://github.com/user-attachments/assets/b47af5b7-f3ad-4ff1-add2-ec75d89b7303)

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.