Skip to content

[DBM] Clarify secret_refresh_interval default behavior on resolution failure #39184

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
aldrickdev wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

[DBM] Clarify secret_refresh_interval default behavior on resolution failure #39184

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions hugo/content/en/agent/configuration/secrets-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1830,6 +1830,10 @@ Set a refresh interval:
secret_refresh_interval: 3600 # refresh every hour
```

<div class="alert alert-info">
<code>secret_refresh_interval</code> defaults to <code>0</code>, which disables automatic refresh. If a secret fails to resolve at Agent startup—for example, because of a transient network or authentication error against your secrets backend, such as Azure Key Vault when using managed identity—it is not retried automatically and remains unresolved until the Agent is restarted. If calls to your secrets backend can be transiently unreliable, set <code>secret_refresh_interval</code> to a non-zero value (for example, <code>3600</code>) so failed resolutions are retried automatically.
</div>

Or, trigger a refresh manually:
```shell
datadog-agent secret refresh
Expand Down
Loading