dataforge/fn_registry
1
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases Wiki Activity

docs(flows): DoD obligatorio con user-facing surface + abrir issues 0100-0103 (taxonomia, frontmatter migration, dev_console, work dashboard)

Browse Source 
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Egutierrez
2026-05-17 00:07:03 +02:00
parent 212875ed0d
commit 5d2a14e50a
77 changed files with 4062 additions and 311 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dev/flows/0006-metabase-versioning.md
+29
View File
@@ -72,6 +72,35 @@ Probar flujo INVERSO al tipico: extraer estado de un servicio interno (Metabase)
- 1 run/dia en data_factory.
- 7 commits en metabase_registry repo (1 semana baseline).
## Definition of Done
Ver `README.md` seccion DoD + user-facing.
### Generico
- [ ] **Repetibilidad**: cron diario 02:00 corre 7 dias consecutivos sin error.
- [ ] **Observabilidad**: `data_factory.runs` + 1 commit en repo `metabase_registry` por dia (o `NO_CHANGES`).
- [ ] **Error-path**: token Metabase expirado → healthcheck pre-pull falla con mensaje claro, no silencio.
- [ ] **Idempotencia**: NO_CHANGES no genera commit vacio en git.
- [ ] **Secrets**: token Metabase en `pass metabase/api-token`.
- [ ] **Docs**: `## Notas` con onboarding + rollback procedure.
- [ ] **Registry-first**: pull/diff/push reusan funciones registry.
- [ ] **INDEX + status**: `status: done` + INDEX + movido.
### User-facing
- [ ] **User-facing**: usuario navega a `https://gitea.../dataforge/metabase_registry/commits/master` → ve commits diarios con diff YAML de dashboards/cards.
- [ ] **User-facing repeat**: misma URL manana muestra commit nuevo (o `NO_CHANGES` skip); rollback con click derecho en commit → restore.
- [ ] **User-facing onboarding**: parrafo en `## Notas`: "Para auditar cambios Metabase: abrir Gitea repo `dataforge/metabase_registry`. Rollback: revertir commit en Gitea → push trigger DAG manual → Metabase restaurado. Matrix bot diario en `#fn-registry-ops` a las 09:00."
- [ ] **User-facing latencia**: cambio manual en Metabase → commit visible al dia siguiente 02:00.
### Custom
- [ ] Rollback E2E probado: revertir commit → siguiente run aplica YAML viejo → Metabase restaura dashboard.
- [ ] Diff YAML estable: keys ordenadas, no churn aleatorio.
- [ ] Dashboards eliminados → commit `DELETED:`, no tombstone huerfano.
- [ ] Backup adicional a vault (no solo git).
## Notas
- Riesgo: si Metabase token expira, el DAG falla silenciosamente. Anadir healthcheck pre-pull.