adapter: metrics, held-item actions, adapter-job release and durable rebind record

Abierto
#2,725 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
prometheus, rust

Línea de trabajo

Start with crates/registry-adapter-job/src/main.rs and hold_guidance, then review release/scripts/release_roster.py and the rebind-identity command. The issue groups several independent efforts, including operator authority and audit design, deployment proofs, parallel ingestion, and durable storage. Agree on one scoped item before estimating completion.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Operating gaps in Registry Adapter and the adapter-job ingestion host, found while comparing it with general integration platforms.

  • Metrics. Neither the facade nor adapter-job serves Prometheus metrics. The other runtimes do.
  • Act on held items. adapter-job holds an item and gives value-free guidance, but by design offers no mutation that releases, accepts, acknowledges or reconciles held work (crates/registry-adapter-job/src/main.rs, hold_guidance). Decide which of release, retry and accept an operator may perform, under which authority, and how each is audited.
  • Release adapter-job with an image. It stays source-build only (release/scripts/release_roster.py), while the facade and adapterctl ship from 0.46.0.
  • Real-server proof for the packs. Run the Kobo pack against a controlled deployment and commit the run record, then ODK and OpenCRVS.
  • Parallel ingestion passes for large sources.
  • Keep a durable record of rebind-identity. The command moves a job's stored item-identity binding. It prints an audit receipt and one line on standard error, but the job store keeps no record of who rebound what and when.
Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
9 h 48 min
PR fusionados (30 d)
151

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de registrystack/registry-stack

Todos los issues de registrystack/registry-stack

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.