bitborg/bitborg-infra
Bevaka
2
0
Avgrena
Du har redan avgrenat bitborg-infra
 0
Kod Ärenden 64 Ändringsförfrågningar 3 Projekt 1 Utgåvor Paket Wiki Aktiviteter Actions

refactor(backup): name archives bitborg-*, accept gitborg-* until 2026-10-31 #518

Sammanfogat
supernaut sammanfogade 3 incheckningar från feat/465-bitborg-archive-names in i main 2026-10-02 13:14:29 +00:00
Konversation 0 Incheckningar 3 Ändrade filer 6 +35 -19
supernaut kommenterad 2026-10-02 13:07:19 +00:00
Ägare
Kopiera länk

What

Name new daily archives bitborg-<TS>.tar.age instead of gitborg-<TS>.tar.age, with a dual-match transition.

  • backup_archive_prefixes: [bitborg, gitborg] in group_vars/all/vars.yml. The first entry is what the backup writes; every entry is what consumers match. Remove gitborg after 2026-10-31, when no gitborg-* archive is left in retention.
  • bitborg-backup.sh: archive and .partial names from the first prefix; .partial sweep, local prune and off-site rclone delete --include match every prefix (.tar.age and legacy .tar.enc).
  • bitborg-backup-verify.sh: newest by mtime over every prefix.
  • bitborg-backup-drill.py: lists every prefix and picks the newest by the embedded timestamp. The old max(names) would have ranked gitborg- above bitborg- and restored a stale archive.
  • Runbook: restore steps and the #465 lifecycle XML use bitborg-. A locked bucket is switched to only after this is applied, so it never holds a gitborg-* archive and needs no legacy rule. Cleanup due 2026-10-31 noted.

Host paths, the OS user, volumes and unit names are unchanged (legacy pins, separate migration).

Verification

--syntax-check, ansible-lint 0/0, rendered templates pass bash -n and py_compile, shellcheck info only (pre-existing). Local test: with gitborg-20261001… (older) and bitborg-20261002… (newer), verify, prune and the drill all select the bitborg- archive; a plain name sort picks the stale one.

Apply

Tags backup,backup-drill: redeploys the backup, verify and drill scripts, no unit changes, no restarts. The next 03:30 run writes the first bitborg- archive.

Refs #465

## What Name new daily archives `bitborg-<TS>.tar.age` instead of `gitborg-<TS>.tar.age`, with a dual-match transition. - `backup_archive_prefixes: [bitborg, gitborg]` in `group_vars/all/vars.yml`. The first entry is what the backup writes; every entry is what consumers match. Remove `gitborg` after 2026-10-31, when no `gitborg-*` archive is left in retention. - `bitborg-backup.sh`: archive and `.partial` names from the first prefix; `.partial` sweep, local prune and off-site `rclone delete --include` match every prefix (`.tar.age` and legacy `.tar.enc`). - `bitborg-backup-verify.sh`: newest by mtime over every prefix. - `bitborg-backup-drill.py`: lists every prefix and picks the newest by the embedded timestamp. The old `max(names)` would have ranked `gitborg-` above `bitborg-` and restored a stale archive. - Runbook: restore steps and the #465 lifecycle XML use `bitborg-`. A locked bucket is switched to only after this is applied, so it never holds a `gitborg-*` archive and needs no legacy rule. Cleanup due 2026-10-31 noted. Host paths, the OS user, volumes and unit names are unchanged (legacy pins, separate migration). ## Verification `--syntax-check`, ansible-lint 0/0, rendered templates pass `bash -n` and `py_compile`, shellcheck info only (pre-existing). Local test: with `gitborg-20261001…` (older) and `bitborg-20261002…` (newer), verify, prune and the drill all select the `bitborg-` archive; a plain name sort picks the stale one. ## Apply Tags `backup,backup-drill`: redeploys the backup, verify and drill scripts, no unit changes, no restarts. The next 03:30 run writes the first `bitborg-` archive. Refs #465
supernaut lade till 3 incheckningar 2026-10-02 13:07:19 +00:00 
Producers write bitborg-<TS>.tar.age. Consumers (partial sweep, local and
off-site prune, verify, drill) match bitborg-* and gitborg-* through
backup_archive_prefixes. The drill picks the newest by embedded timestamp.

Refs #465
A locked bucket is switched to only after the rename is applied, so it never receives a gitborg-* archive.

Refs #465
Merge remote-tracking branch 'origin/main' into feat/465-bitborg-archive-names
Alla kontroller lyckades
ci / ci (pull_request) Successful in 2m8s
Detaljer
0c42bc68f2
supernaut sammanfogade incheckning d1f53f533b till main 2026-10-02 13:14:29 +00:00
supernaut tog bort grenen feat/465-bitborg-archive-names 2026-10-02 13:14:30 +00:00
Logga in för att delta i denna konversation.
Granskare
Inga granskare
Etiketter
Rensa etiketter
  
area/backups
Backup & restore

  
area/ci
Actions / runners

  
area/control-panel
Logged-in self-service area

  
area/identity
Kanidm / OIDC / entitlements

  
area/infra
Infrastructure (OpenTofu/Ansible/host)

  
area/observability
Monitoring / logs / analytics

  
area/payments
Billing / payment providers

  
area/security
Security & compliance (incl. ISO 27001)

  
area/storage
Volumes / data / LFS

  
area/web
Public web portal (gitborg-web)

  
blocked
Evaluated and specified, but waiting on an external dependency

  
needs-info
Waiting on the reporter for more information

  
needs-triage
Not yet evaluated

  
ready-for-implementation
Fully specified, ready to be picked up

  
type
bug
 Something is broken

  
type
chore
 Maintenance / housekeeping

  
type
docs
 Documentation

  
type
epic
 High-level roadmap item

  
type
feature
 New capability

  
type
task
 Concrete unit of work

  
wontfix
Will not be actioned

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
Milstolpe
Rensa milstolpe
Inga objekt
Ingen milstolpe
Projekt
Rensa projekt
Inga objekt
Inget projekt
Tilldelade
Rensa tilldelade
Inga tilldelade
1 deltagare
Notiser
Förfallodatum
Förfallodatumet är ogiltigt eller utanför gränserna. Använd formatet "åååå-mm-dd".

Inget förfallodatum satt.

Beroenden

Inga beroenden satta

Referens
bitborg/bitborg-infra!518
Ingen beskrivning angiven.