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

オープン
#2,733 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
rust
領域
api, backend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
Rust
スター
2
フォーク
0
平均マージ
9時間 48分
マージ済み PR(30日)
151

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

registrystack/registry-stack のほかの issue

registrystack/registry-stack の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。