Skip to content

Conversation

zhiyuanliang-ms
Copy link
Member

@zhiyuanliang-ms zhiyuanliang-ms commented Aug 29, 2025

This bug is found due to the discussion here.

Corner case:

If there are a secret reference and a normal configuration setting with the same key (but different labels), the expected behavior is that if the normal configuration setting is loaded later, it should override the secret value. However, the current implementation will let the secret value to override it when secret refresh is enabled.

The fix is to dedupe the configuration settings with the same key in advance (before processing all configuration settings). In this case, if a secret reference is overrided by a normal key value it will not be stored in cache for the following secret refresh operation.

@zhiyuanliang-ms zhiyuanliang-ms force-pushed the zhiyuanliang/secret-refresh-bug-fix branch from ab8e567 to a7087cf Compare August 29, 2025 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant