Repository navigation
Mint Vault token before copying Mergify backport labels - #8076
fr4nc1sc0-r4m0n wants to merge 4 commits into
Conversation
GITHUB_TOKEN label writes do not retrigger pull_request labeled workflows, so oblt-aw automerge never starts on merge-ready backports.
|
This pull request does not have a backport label. Could you fix it @fr4nc1sc0-r4m0n? 🙏
|
There was a problem hiding this comment.
🔵 Needs a closer look
The prerequisite Vault TokenPolicy deployment and downstream workflow triggering remain unverified.
No open issues 🎉
What changed in this PR
Updates Mergify backport label copying to use an ephemeral GitHub token so copied labels can trigger downstream automerge workflows.
Changes:
- Grants OIDC permission to mint a token through Vault.
- Passes the minted token to the labels-copier action.
| File | Description |
|---|---|
.github/workflows/mergify-labels-copier.yml |
Adds token creation and uses it when copying backport labels. |
Review effort: Balanced
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
Mint inside labels-copier instead of a separate create-token step.
Label writes use the Vault token from TokenPolicy; only id-token: write is needed for OIDC.
|
Dropped unused |

Motivation
Mergify backports of Observability Agentic Workflow sync PRs get
oblt-aw/ai/merge-readyfrom this labels copier, but the label is applied withGITHUB_TOKEN. GitHub does not start newlabeledworkflow runs from that actor, so automerge never wakes.Summary
use-ephemeral-token: trueonelastic/oblt-actions/mergify/labels-copier@v1so the action mints a Vault token and copies labels with itid-token: writefor OIDCDepends on: elastic/oblt-actions#1171 merged and released on
@v1, plus a catalog-info TokenPolicy for this workflow path, or mint will fail closed.Validation
mergify/bp/PR that copies merge-readylabeledactor is the Vault app (notgithub-actions[bot])labeledeventRelated issue: elastic/oblt-aw#2336