Skip to content

Conversation

@Mathew-Estafanous
Copy link
Contributor

@Mathew-Estafanous Mathew-Estafanous commented Dec 30, 2025

What does this PR do? What is the motivation?

With the addition of secrets refresh support for autodiscovery checks, we'd like to surface this new option for customers on the Agent secrets management documentation.

The API/APP key refresh section was turned into a subsection of a more general "secrets refresh" section.

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

@Mathew-Estafanous Mathew-Estafanous self-assigned this Dec 30, 2025
@github-actions
Copy link
Contributor

Preview links (active after the build_preview check completes)

Modified Files

@Mathew-Estafanous Mathew-Estafanous marked this pull request as ready for review December 30, 2025 21:15
@Mathew-Estafanous Mathew-Estafanous requested a review from a team as a code owner December 30, 2025 21:15
@git-thuerk-done git-thuerk-done added the editorial review Waiting on a more in-depth review label Dec 30, 2025
@git-thuerk-done
Copy link
Contributor

Thanks! I have created DOCS card for someone on our team to review this further

## Refreshing API/APP keys at runtime
## Refreshing secrets at runtime

Starting in Agent v7.67, configure the Agent to refresh resolved secrets without requiring a restart.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Starting in Agent v7.67, configure the Agent to refresh resolved secrets without requiring a restart.
Starting in Agent v7.67, you can configure the Agent to refresh resolved secrets without requiring a restart.

}
```

Now the Agent can trigger secrets refresh at either the interval set in `secret_refresh_interval` or manually with `datadog-agent secret refresh`.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Now the Agent can trigger secrets refresh at either the interval set in `secret_refresh_interval` or manually with `datadog-agent secret refresh`.
The Agent can then trigger secrets refresh at either the interval set in `secret_refresh_interval` or manually with `datadog-agent secret refresh`.

Does this keep the meaning?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that's good. thank you!

Copy link
Contributor

@iadjivon iadjivon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi there, thanks for this PR. I added some small suggestion. Let me know if you have any questions!

Copy link
Contributor

@iadjivon iadjivon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All set! :shipit:

@Mathew-Estafanous Mathew-Estafanous requested review from a team and iadjivon January 6, 2026 20:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

editorial review Waiting on a more in-depth review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants