[DBM] Clarify secret_refresh_interval default behavior on resolution failure - #39184
Draft
aldrickdev wants to merge 1 commit into
Draft
[DBM] Clarify secret_refresh_interval default behavior on resolution failure#39184aldrickdev wants to merge 1 commit into
aldrickdev wants to merge 1 commit into
Conversation
Contributor
Preview links (active after the
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Added a callout next to the
secret_refresh_intervalconfiguration option in the Agent secrets management page clarifying that its default value of0disables automatic refresh, so a secret that fails to resolve at Agent startup (for example, due to a transient network or auth error against a secrets backend like Azure Key Vault) is not retried automatically and stays unresolved until the Agent is restarted. The callout recommends setting a non-zero interval (for example,3600) if backend calls can be transiently unreliable.Why
With the default
secret_refresh_interval: 0, a transient secret backend failure at Agent startup causes secrets resolved via that backend to fail silently and persistently until a manual restart, and this behavior wasn't called out in the secrets management docs.Docs preview
https://docs.datadoghq.com/agent/configuration/secrets-management/