feat(privateactionrunner): add mutating setConfig and generateFlare actions#53756
Draft
louis-cqrl wants to merge 1 commit into
Draft
Conversation
…ctions
Add the two mutating actions to the com.datadoghq.agent bundle:
- setConfig: POST /agent/config/{key} to change a runtime-settable
configuration value on the local agent.
- generateFlare: POST /agent/flare to build a flare archive on the agent
host, returning its local path.
generateFlare currently only creates the archive on the agent host; uploading
it to a Datadog support case is a planned follow-up. Confirmation gating for
these consequential actions is enforced at the MCP tool layer (see the
corresponding dd-source change), not in the bundle.
This was referenced Jul 16, 2026
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 does this PR do?
Adds the two mutating actions to the
com.datadoghq.agentPAR bundle:setConfig—POST /agent/config/{key}to change a runtime-settable configuration value on the local Agent.generateFlare—POST /agent/flareto build a flare archive on the Agent host, returning its local path.Both propagate the task context to their IPC request (the flare endpoint drops its server-side deadline, so an unbounded request could otherwise hang the runner on timeout/shutdown).
Motivation
Completes the
com.datadoghq.agentbundle with the write actions. Confirmation gating for these consequential actions is enforced at the MCP tool layer (dd-source PR 7), not in the bundle — the bundle just executes.Describe how you validated your changes
bazel build //pkg/privateactionrunner/bundles/agent:agent //pkg/privateactionrunner/bundles:bundlespasses; pre-pushgo-linter/go-testpass.Additional Notes
Stacked series (merge in order). datadog-agent: (1) RC-state endpoint → (2) read-only bundle → (3)
getRemoteConfigState→ (4) this PR. Based on branchlouis-cqrl/agent-par-bundle-remoteconfig(PR 3).Known follow-up:
generateFlarecurrently only creates the archive on the Agent host; uploading it to a Datadog support case is out of scope here (needs either an Agent-side send endpoint or upload support in the runner).Full stacked series (merge in order)
datadog-agent (Go execution layer):
com.datadoghq.agentbundle, read-only actionsgetRemoteConfigStateactionsetConfig/generateFlareactionsdd-source (catalog + MCP tools + authz):
5. ddoghq/dd-source#22260 —
com.datadoghq.agentprivate bundle manifest6. ddoghq/dd-source#22261 — read-only MCP tools
7. ddoghq/dd-source#22262 — confirm-gated mutating MCP tools
8. ddoghq/dd-source#22263 — MCP OBO allow-list (optional hardening)
Cross-repo: land datadog-agent #53753–#53756 and dd-source #22260, and ship an agent build containing them, before the dd-source MCP tools (#22261–#22262) work end-to-end.