Deprovision the unused tap-writer Forgejo runner #573

Open
opened 2026-07-22 07:07:00 +00:00 by coilyco-ops · 0 comments
Owner

The dedicated tap-writer Forgejo Actions lane is no longer used. Ward now bumps the Homebrew tap from its ordinary runs-on: docker release job with the explicit TAP_WRITE_TOKEN secret. A workspace-wide search found no runs-on: tap-writer consumer.

Acceptance criteria:

  • Remove deploy/forgejo-runner-tap-writer.yml and scripts/provision-tap-bump-token.sh.
  • Remove current-feature, token-inventory, runner-TTL, and troubleshooting references. Preserve clearly historical changelog references.
  • Delete the live forgejo-runner-tap-writer StatefulSet, its ExternalSecret and generated Secret, and the retained data-forgejo-runner-tap-writer-0 PVC.
  • Remove the stale runner registration from Forgejo after the pod is gone.
  • Revoke the tap-bump Forgejo PAT and delete /forgejo/tap-bump-token from SSM without exposing its value.
  • Verify no workflow still selects the tap-writer label and the normal ward release tap bump remains green.
  • Run pre-commit run --all-files, commit with closes #<issue>, and push canonical main.

Live Kubernetes, Forgejo admin, and SSM deletion steps require an attended operator-capable run.

The dedicated `tap-writer` Forgejo Actions lane is no longer used. Ward now bumps the Homebrew tap from its ordinary `runs-on: docker` release job with the explicit `TAP_WRITE_TOKEN` secret. A workspace-wide search found no `runs-on: tap-writer` consumer. Acceptance criteria: * Remove `deploy/forgejo-runner-tap-writer.yml` and `scripts/provision-tap-bump-token.sh`. * Remove current-feature, token-inventory, runner-TTL, and troubleshooting references. Preserve clearly historical changelog references. * Delete the live `forgejo-runner-tap-writer` StatefulSet, its ExternalSecret and generated Secret, and the retained `data-forgejo-runner-tap-writer-0` PVC. * Remove the stale runner registration from Forgejo after the pod is gone. * Revoke the `tap-bump` Forgejo PAT and delete `/forgejo/tap-bump-token` from SSM without exposing its value. * Verify no workflow still selects the `tap-writer` label and the normal ward release tap bump remains green. * Run `pre-commit run --all-files`, commit with `closes #<issue>`, and push canonical main. Live Kubernetes, Forgejo admin, and SSM deletion steps require an attended operator-capable run.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/infrastructure#573
No description provided.