coordinator: add scheduling.publish-windows/v1 so a workflow can turn a record into bookable windows

Aperta
#2,733 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
api, backend

Direzione di ricerca

Start with the operation catalogue in crates/registry-coordinator/src/operations.rs and the coordinator flow described in docs/site/src/content/docs/explanation/how-coordinator-works.mdx; the issue also depends on #2732. Trace how Scheduling operations are previewed and applied, then review the linked work for publishing windows. Done means the native journey covers create, update, withdrawal and replay, refusals surface their problem code, and operation schemas and contracts are regenerated.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:coordinator area:scheduling criticality:p2 enhancement triage:needs-implementation

Use case

The common composition is a registry record event, then a reviewed mapping, then published bookable windows. For example, a training session, exam sitting or public activity is recorded in BReg and becomes bookable. Adopters should be able to wire that with configuration and one mapping Function, not a bespoke service.

Current evidence

  • Coordinator accepts the signed BReg record event and runs reviewed Functions. Its operation catalogue has Scheduling reads and booking operations, but no supply write.
  • Coordinator has no dynamic fan-out. Publishing one snapshot per record event needs none.

Proposed behaviour

  • scheduling.publish-windows/v1, with preview and apply, calling #2732 under Coordinator's own Scheduling credential and the source profile the operator configured for it.
  • Idempotent by the source record's revision. One call per record event.
  • An example project: BReg record event, then a Rhai mapping Function that turns the record into a window snapshot (including bounded expansion of recurring sessions), then scheduling.publish-windows/v1.

Acceptance criteria

  • In a native journey, creating, updating and withdrawing a BReg record publishes, replaces and withdraws its windows.
  • Replay after a Coordinator restart publishes once.
  • A Scheduling refusal surfaces as a Run failure with the product's problem code.
  • Operation schemas and contracts are regenerated.

Delivery

Implemented in one PR with #2731 and #2732.

Lingua principale
Rust
Stelle
2
Fork
0
Merge medio
9h 48m
PR unite (30g)
151

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di registrystack/registry-stack

Tutte le issue di registrystack/registry-stack

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.