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

Ouverte
#2,733 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
rust
Domaine
api, backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
2
Forks
0
Merge moyen
9 h 48 min
PR mergées (30 j)
151

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de registrystack/registry-stack

Toutes les issues de registrystack/registry-stack

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.