Pre-prod validation: staging environment for infra changes #37
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#37
Läser in…
Hänvisa till i nytt ärende
Ingen beskrivning angiven.
Ta bort grenen "%!s()"
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?
Give infra changes a production-like place to prove themselves before they touch prod. The 2026-07-18 outage (caddy #94, ~4 min down) is the motivating case:
ansible-playbook --checkreported the change clean, but it can't actually start containers, so it missed aNoNewPrivileges+DropCapability=ALLinteraction with a file-capability binary that crash-looped Caddy on the real apply.Decided — ADR 0030 (accepted 2026-07-18)
Phased, cost-tiered. Trunk-based, single
main(branch-protected on CI-green — configured; review soft), directory-scoped environments, not Gitflow.always-tagged play asserts core services active + endpoints serve +.promfiles readable; halt+alert, fix-forward.Full rationale:
bitborg-docs/decisions/0030-environments-and-promotion.md.The now-scoped slice (Tier 0 + Tier 2) is complete. Tier 1 remains deferred by design.
Tasks
supernaut refererade till detta ärende2026-07-18 21:24:12 +00:00
Shipping the delivered tiers. Tier 0 and Tier 2 are done. Tier 1 is deferred until there is traffic that justifies a standing staging environment.
The Tier 1 tasks (bitborg/bitborg-infra#103, #105, #106) stay in the infra backlog. Reopen this or file a new epic when they are picked up.