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

Abierto
#2,733 0 comentarios 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
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
api, backend

Línea de trabajo

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.

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

Descripción

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.

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.