fix(devenv): single-source the dogfood runner-id so mint and runner never drift (RIG-2660) - #582
Open
rigel-mintaka wants to merge 1 commit into
Open
fix(devenv): single-source the dogfood runner-id so mint and runner never drift (RIG-2660)#582rigel-mintaka wants to merge 1 commit into
rigel-mintaka wants to merge 1 commit into
Conversation
…ever drift (RIG-2660) The dogfood loop minted the runner token with a hardcoded runner-id and launched compass-runner with the same literal in two separate places. The runner's Enroll cross-checks the token subject against its --runner-id, so any drift between the two copies is rejected unauthenticated at enroll — and a deployment overlay that overrides one but not the other silently breaks enrollment on every DB recreate (the live mattfw box runs a different runner-id and needs a manual re-mint each recreate). Introduce one dogfoodRunnerID binding in the let block (mirroring dogfoodDSN) that both the mint task and the runner process reference, so they move in lockstep and an overlay overrides the subject in exactly one place. Refs RIG-2660 Co-authored-by: Matt Wilkinson <matt@rigel.build>
|
Compass engineering docs preview: https://compass-rig-2660-runnerid-si.compass-eng-docs.pages.dev Deployed from |
This was referenced Aug 24, 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.
This PR is part of a stack containing 3 PRs:
mainThe dogfood loop minted the runner token with a hardcoded runner-id and launched compass-runner with the same literal in two separate places. The runner's Enroll cross-checks the token subject against its --runner-id, so any drift between the two copies is rejected unauthenticated at enroll — and a deployment overlay that overrides one but not the other silently breaks enrollment on every DB recreate (the live mattfw box runs a different runner-id and needs a manual re-mint each recreate).
Introduce one dogfoodRunnerID binding in the let block (mirroring dogfoodDSN) that both the mint task and the runner process reference, so they move in lockstep and an overlay overrides the subject in exactly one place.
Refs RIG-2660
Co-authored-by: Matt Wilkinson matt@rigel.build