[DOCS-XXXXX] Rewrite Set Up in the Datadog Agent, add Execution Policies enrollment - #39047
Draft
irving-santiago wants to merge 1 commit into
Draft
Conversation
This was referenced Aug 10, 2026
Author
1 task
This was referenced Aug 10, 2026
Contributor
Preview links (active after the
|
Contributor
|
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
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 does this PR do? What is the motivation?
Fixes DOCS-XXXXX
Rewrites "Set Up in the Datadog Agent" (formerly "Use Private Actions") to cover Execution Policies enrollment alongside Connections: Fleet Automation vs. manual installation per platform tab, real "Update the runner" tabs, a "Manage the runner" section, and Debugging. Removes "Available actions by runner type" (moves to the new Reference page in a later slice in this stack).
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Claude Code carried this page's content over from a pre-drafted, QA-verified draft, ran Vale, and renamed the page title/nav entry to match the new structure.
Additional notes
Flagging for reviewer: the owned/ownerless Fleet-Automation-vs-Manual framing would benefit from a product sanity check. Also, the previous page's "Connect a runner" and "Use a private action" sections aren't present in the new draft — worth confirming that's intentional.