-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[CONTP-1179] docs(agent_secrets): Add autodiscovery to secrets management docs #33624
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
[CONTP-1179] docs(agent_secrets): Add autodiscovery to secrets management docs #33624
Conversation
Preview links (active after the
|
|
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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 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?
There was a problem hiding this comment.
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!
iadjivon
left a comment
There was a problem hiding this 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!
iadjivon
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All set! ![]()
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
7.76release candidate published.Merge readiness:
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