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

Aberta
#2,725 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
25/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
prometheus, rust

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Rust
Estrelas
2
Forks
0
Merge médio
9h 48min
PRs com merge (30d)
151

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de registrystack/registry-stack

Todas as issues de registrystack/registry-stack

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.