docs(adr): 0033 runner-controller extraction + 0034 pull-based infra deploy (proposed) #45
Inga granskare
Etiketter
Inga etiketter
area/backups
area/ci
area/control-panel
area/identity
area/infra
area/observability
area/payments
area/security
area/storage
area/web
blocked
needs-info
needs-triage
ready-for-implementation
type
bug
type
chore
type
docs
type
epic
type
feature
type
task
wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
Inga beroenden satta
Referens
bitborg/bitborg-docs!45
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "docs/adr-0033-0034-runner-extraction-infra-deploy"
Borttagning av en gren är permanent. Även om den borttagna grenen kan fortsätta existera en kort tid innan den faktiskt tas bort, kan det INTE ångras i de flesta fall. Vill du fortsätta?
Two proposed ADRs seeding the #38 self-deploy plan (decisions locked with the maintainer):
gitborg/runner-controller, semver images to the Forgejo registry, infra pins + Renovate-updates; bake the runner cloud-init template into the image; slim the consumer role and fix the #63 pull-on-tag-change gap in the same change; no:latest/AutoUpdate for the destructive daemon; gapless bootstrap. Unblocks bitborg-infra#38, implements bitborg-infra#201.deploy/ok; a host-side timer runsansible-playbook site.ymllocally with vault + SSH staying on-host; OpenTofu stays manual with only a plan-only drift check; health gate + fix-forward from 0030.Both are Status: Proposed — they record the agreed direction; implementation is bitborg-infra#201 (0033) then #38 (0034).