feat(acl): add tag:tag-authority as reconciler owner tag (TIN-2639) - #19
Merged
Conversation
The TIN-2639 scoped OAuth client failed its Phase-4 bounded write (HTTP 400: cannot write tag:dollhouse) because no policy-defined tag owns the tags the lab reconciler manages. Per the rotation runbook's tag-authority gate, define tag:tag-authority (admin-owned) and grant it ownership of the exact 14-tag union the reconciler can write after the 2026-07-27 inventory-to-live trim: dollhouse, dev, k8s, k8s-operator, qa, rj-gateway, services, setec, staging, tsidp, subnet-router, switch, tinyland-lab-moonlight, tinyland-lab-sunshine. Ceremony follow-up (operator): re-mint the OAuth client with tag:tag-authority (client tags are fixed at creation), re-run Phase-3 proof, one idempotent bumble write ([dollhouse] -> [dollhouse]) with audit-log verification, then Phase-5 revoke of the legacy tskey-api-* before 2026-07-31.
|
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.
Why
The TIN-2639 scoped OAuth client failed its Phase-4 bounded write (HTTP 400: cannot write
tag:dollhouse) because no policy-defined tag owns the tags the lab reconciler manages. The rotation runbook's Tag Authority Gate prescribes exactly this: "grant the exact final tag set, or a policy-defined owner tag that owns that complete set" — after reconciling inventory to live (the lab desired-tags trim PR, in flight under the same 2026-07-27 ruling).What
constants.dhall: definetag_authority = "tag:tag-authority"fragments/core.dhall: admin-owned tagOwners entry for it, plus ownership of the exact 14-tag union the reconciler can write post-trim (dollhouse, dev, k8s, k8s-operator, qa, rj-gateway, services, setec, staging, tsidp, subnet-router, switch, tinyland-lab-moonlight, tinyland-lab-sunshine — read live 2026-07-27)just check+just buildpass; rendered policy verified: 14 tagOwners entries carrytag:tag-authority.Merge semantics + ceremony
Merging auto-applies the policy via cd.yml (the repo's reviewed flow). Then the attended ceremony: re-mint the OAuth client with
tag:tag-authority(client tags are fixed at creation) → Phase-3 strict proof → one idempotent bumble write ([dollhouse]→[dollhouse]) with audit-log verification → Phase-5 revoke of the legacytskey-api-*before 2026-07-31. Stop line: if the write isn't green by 07-30 EOD, extend the legacy token instead — never revoke first.