Add octo-sts trust policy for datadog-api-spec merge-dependents - #659
Merged
MintsInc merged 1 commit intoJul 20, 2026
Merged
Conversation
MintsInc
marked this pull request as ready for review
July 20, 2026 12:08
nogates
approved these changes
Jul 20, 2026
MintsInc
deleted the
ulysse.mavrocordatos/AAWF-1384/octo-sts-merge-dependents-policy
branch
July 20, 2026 12:19
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
2 participants
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.
Context
datadog-api-spec generates pup's CLI commands from the OpenAPI spec and pushes them here as PRs. When a spec PR also regenerates the Rust client (
datadog-api-client, pinned inCargo.tomlby commitrev), pup must be repointed at the new Rust commit before/at merge. datadog-api-spec's merge queue now runs apipeline merge-dependentsstep (in.github/workflows/merge-queue.yml) that, after the Rust client merges, rewrites pup'sCargo.tomlrevand merges pup's generated PR. That step authenticates to pup with an octo-sts token, which requires a trust policy in this repo.This is the merge-time sibling of the existing
.github/chainguard/datadog-api-spec.ci-cd.generate.sts.yaml. That policy trusts the PR-time generation workflow (ci-cd.ymlonpull_request); this one trusts the merge-queue workflow (merge-queue.ymlonpushto the MergeQueue working branch). They must be separate because the event and workflow differ.Changes
Adds one octo-sts trust policy:
.github/chainguard/datadog-api-spec.merge-queue.merge-dependents.sts.yaml, grantingcontents: writeandpull_requests: writeto themerge-queue.ymlworkflow running onmq-working-branch-*refs in DataDog/datadog-api-spec.Required for datadog-api-spec's pup generation merge step to authenticate and land the repointed Cargo.toml.