feat: tap-writer runner + tap-bump token provisioning #195
No reviewers
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/infrastructure!195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/tap-writer-runner"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Stand up a dedicated, DinD-free Forgejo runner for cross-repo homebrew formula bumps.
Companion PR: coilyco-flight-deck/ward#47 - the ward release job that targets
runs-on: tap-writer. Apply this runner (and provision the token) before merging that one.What
deploy/forgejo-runner-tap-writer.yml- host-executoract_runner, labeltap-writer, no DinD. Token from SSM/forgejo/tap-bump-tokenreaches git only via a credential helper (never job env / Actions secret).scripts/provision-tap-bump-token.sh- mint awrite:repositoryForgejo token, store at SSM (no overwrite). Run on a machine with Forgejo + AWS creds + coily.docs/FEATURES.md- runner entry.Run order (on a cluster-access machine)
FORGEJO_USER=<u> FORGEJO_PASS=<p> ./scripts/provision-tap-bump-token.shsudo k3s kubectl apply -f deploy/forgejo-runner-tap-writer.ymltap-writer:hostand picks up a job. If the image gates the host executor, fall back to adocker://node:20-bookwormlabel.closes #194
🤖 Generated with Claude Code