feat(sbx-gits): el seed NO activa la extensión forgejo por defecto (SEED_FORGEJO_EXT=0) — se separa del borrado único (R143) #804

Merged
pi-landing merged 1 commit from plane/HOMELAB-2626-r143-forgejo-apagado into live 2026-11-04 07:04:30 +00:00
Collaborator

Pedido R143: el borrado único debe traer el emulador 8/8 y #801, pero no activar la extensión forgejo vieja (su candado exige dos modelos y rechazaría el T9 de E1).

  • statefulset.yaml (sbx-gits): env SEED_FORGEJO_EXT="0" en el initContainer seed-pi-agent; el bloque 1b queda detrás de if [ "$SEED_FORGEJO" = "1" ] (SEED_FORGEJO=${SEED_FORGEJO_EXT:-0}). Apagado: no copia, imprime SEED-FORGEJO: apagado (SEED_FORGEJO_EXT=0), sin SEED-MISSING/SEED-INVARIANT/exit 1; si extensions/forgejo ya existe en el volumen → rm -rf + SEED-FORGEJO: eliminado (apagado) (no se queda a medias) y se excluye del recuento BEFORE para que el paso 3a no lo cuente como perdido. Encendido: comportamiento actual (rm+copy fresco + verificación). FORGEJO_API_KEY se queda (no se usa sin la extensión). sbx-lab y sbx-sendrast intactos.
  • README §11: está APAGADA por defecto, por qué (candado dos-modelos de forgejo_merge_pr que rechaza la clase peligrosa de E1 hasta que overseer-gits lo cambie — HOMELAB-2518) y que encenderla = SEED_FORGEJO_EXT a "1" + recrear el pod (OnDelete).
  • epic-test: sección 14[R143] con invariante (valor presente, gate, apagado sin SEED-MISSING, limpieza de restos, README nombra HOMELAB-2518) + 3 mutaciones rojas + caso APAGADO ejecutado de verdad (rc=0, avisa, borra árbol previo, SEED-STATUS present).
  • Render: kubectl kustomize de sbx-gits sin flags rc=0; sbx-lab y sbx-sendrast byte-idénticos a live. epic-test 343 checks (los 3 rojos locales son el acoplamiento H1a/H10 del staging, ajenos: esta rama no toca sbx-common).

Sin merge hasta el OK del supervisor.

Pedido R143: el borrado único debe traer el emulador 8/8 y #801, pero **no** activar la extensión forgejo vieja (su candado exige dos modelos y rechazaría el T9 de E1). - `statefulset.yaml` (sbx-gits): env `SEED_FORGEJO_EXT="0"` en el initContainer `seed-pi-agent`; el bloque 1b queda detrás de `if [ "$SEED_FORGEJO" = "1" ]` (`SEED_FORGEJO=${SEED_FORGEJO_EXT:-0}`). Apagado: no copia, imprime `SEED-FORGEJO: apagado (SEED_FORGEJO_EXT=0)`, **sin** SEED-MISSING/SEED-INVARIANT/exit 1; si `extensions/forgejo` ya existe en el volumen → `rm -rf` + `SEED-FORGEJO: eliminado (apagado)` (no se queda a medias) y se excluye del recuento `BEFORE` para que el paso 3a no lo cuente como perdido. Encendido: comportamiento actual (rm+copy fresco + verificación). `FORGEJO_API_KEY` se queda (no se usa sin la extensión). sbx-lab y sbx-sendrast intactos. - README §11: está APAGADA por defecto, por qué (candado dos-modelos de `forgejo_merge_pr` que rechaza la clase peligrosa de E1 hasta que overseer-gits lo cambie — HOMELAB-2518) y que encenderla = `SEED_FORGEJO_EXT` a `"1"` + recrear el pod (OnDelete). - epic-test: sección `14[R143]` con invariante (valor presente, gate, apagado sin SEED-MISSING, limpieza de restos, README nombra HOMELAB-2518) + 3 mutaciones rojas + caso APAGADO **ejecutado** de verdad (rc=0, avisa, borra árbol previo, SEED-STATUS present). - Render: `kubectl kustomize` de sbx-gits sin flags rc=0; sbx-lab y sbx-sendrast **byte-idénticos** a live. epic-test 343 checks (los 3 rojos locales son el acoplamiento H1a/H10 del staging, ajenos: esta rama no toca sbx-common). **Sin merge hasta el OK del supervisor.**
R143: el seed de sbx-gits NO activa la extension forgejo por defecto (SEED_FORGEJO_EXT=0; apagado no falla el seed y limpia restos; encender = un valor) — se separa del borrado unico (HOMELAB-2626)
All checks were successful
0/0 projects applied successfully.
CI Review / receiver-test (pull_request) Successful in 19s
CI Review / runner-manifest-test (pull_request) Successful in 21s
CI Review / helm-validate (pull_request) Successful in 31s
CI Review / alert-receiver-test (pull_request) Successful in 34s
Lint & Validate / shellcheck (pull_request) Successful in 16s
Lint & Validate / yaml-lint (pull_request) Successful in 30s
CI Review / record-sql-test (pull_request) Successful in 3m37s
Lint & Validate / terraform-validate (pull_request) Successful in 4m34s
CI Review / cockpit-test (pull_request) Successful in 9m23s
CI Review / cockpit-e2e (pull_request) Successful in 9m23s
CI Review / dispatcher-test (pull_request) Successful in 10m48s
fe6da091ea
pi-landing force-pushed plane/HOMELAB-2626-r143-forgejo-apagado from fe6da091ea
All checks were successful
0/0 projects applied successfully.
CI Review / receiver-test (pull_request) Successful in 19s
CI Review / runner-manifest-test (pull_request) Successful in 21s
CI Review / helm-validate (pull_request) Successful in 31s
CI Review / alert-receiver-test (pull_request) Successful in 34s
Lint & Validate / shellcheck (pull_request) Successful in 16s
Lint & Validate / yaml-lint (pull_request) Successful in 30s
CI Review / record-sql-test (pull_request) Successful in 3m37s
Lint & Validate / terraform-validate (pull_request) Successful in 4m34s
CI Review / cockpit-test (pull_request) Successful in 9m23s
CI Review / cockpit-e2e (pull_request) Successful in 9m23s
CI Review / dispatcher-test (pull_request) Successful in 10m48s
to 0903703e8b
All checks were successful
CI Review / runner-manifest-test (pull_request) Successful in 17s
CI Review / receiver-test (pull_request) Successful in 12s
CI Review / helm-validate (pull_request) Successful in 23s
CI Review / alert-receiver-test (pull_request) Successful in 30s
Lint & Validate / yaml-lint (pull_request) Successful in 24s
Lint & Validate / shellcheck (pull_request) Successful in 11s
CI Review / record-sql-test (pull_request) Successful in 1m36s
Lint & Validate / terraform-validate (pull_request) Successful in 2m35s
CI Review / cockpit-test (pull_request) Successful in 3m44s
CI Review / dispatcher-test (pull_request) Successful in 4m55s
CI Review / cockpit-e2e (pull_request) Successful in 5m8s
2026-11-04 06:56:34 +00:00
Compare
pi-landing deleted branch plane/HOMELAB-2626-r143-forgejo-apagado 2026-11-04 07:04:30 +00:00
Sign in to join this conversation.
No reviewers
No labels
operator-review
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
Homelab/infra-core!804
No description provided.