- Notifications
You must be signed in to change notification settings - Fork4
Key vault secret refresh#175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
…ScriptProvider into zhiyuanliang/startup-timeout
…re/AppConfiguration-JavaScriptProvider into zhiyuanliang/secret-refresh
…re/AppConfiguration-JavaScriptProvider into zhiyuanliang/secret-refresh
…re/AppConfiguration-JavaScriptProvider into zhiyuanliang/secret-refresh
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
…e/AppConfiguration-JavaScriptProvider into zhiyuanliang/secret-refresh
…ScriptProvider into zhiyuanliang/secret-refresh
…ScriptProvider into zhiyuanliang/secret-refresh
…ScriptProvider into zhiyuanliang/secret-refresh
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
d59f8cf intomainUh oh!
There was an error while loading.Please reload this page.
jimmyca15 commentedJul 10, 2025
🥳 🎉 |
Uh oh!
There was an error while loading.Please reload this page.
Why this PR?
Usage:
Allow periodic reload of key vault secrets. In this case, even if there is no change on App Configuration key-values. This feature is targeted on the scenario where user is using latest version of a secret. In this case, the key vault reference url will not change, but the secret value will change if user rotates their secret.
Secret cache
Secret with version will be cached after the initial load and whenever a secret reference of that secret is resolved, the value will always be served from the cache.
Secret with no version (which means latest), will be cached after the initial load, and it will be served from cache if the secret refresh interval is configured and not expired. Otherwise, the provider will reload it from the Key Vault.
reference:#249