scheduling: let a source system publish bookable windows under a source profile

未关闭
#2,732 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
活跃
技术栈
openapi, postgresql, rust

调研方向

Read crates/registry-scheduling/src/source_busy.rs and the scheduling documentation and security page linked in the issue to understand the existing source-busy flow and operator publishing rules. Then map the proposed preview/apply behavior, source ownership, revision handling, and profile limits to the acceptance criteria. Done means the PostgreSQL suite covers the listed cases and the OpenAPI document, clients, applicable CLI catalogue, security page, and repository guidance are updated.

由索引模型根据 Issue 内容生成。

描述

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

Use case

Many institutions already hold the schedule in another system: a registry of training sessions or exam sittings, a programme's distribution days, a register of public activities, a staff roster. That system should be able to publish bookable windows without an operator re-keying them and without holding the operator's credential.

Current evidence

  • Windows are environment records that only an operator publishes. records apply replaces the whole document.
  • Source-busy already lets a configured source subtract supply through /v1/source-busy/{preview,apply} (source_busy.rs). Nothing equivalent adds supply.
  • The Scheduling security page does not describe busy sources as a trust boundary.

Proposed behaviour

  • /v1/source-windows/preview and /v1/source-windows/apply, mirroring source-busy: a configured source profile, a bounded snapshot under expectedRevision, and preview before apply.
  • Per profile, the operator declares the source identity, the offerings and locations it may publish for, a horizon, and maximum units per window and in total. Anything outside is refused.
  • A snapshot is keyed by the source's own record reference. One source record, such as one activity or one session series, publishes and replaces only its own windows. The source record's revision is the expected revision, so replays and out-of-order deliveries are safe.
  • Source-published windows are marked as source-owned. Operator records apply neither overwrites nor deletes them, and a source cannot touch operator windows.
  • Shrinking or removing a window below its live bookings is refused, unless the snapshot withdraws it explicitly under #2730.
  • Published windows are distinct sessions, so callers book them by window (#2731).

Acceptance criteria

  • A source publishes, replaces and withdraws its own windows within its profile.
  • The route refuses windows outside the profile's offerings, locations, horizon or units, and refuses a stale revision.
  • Replaying a snapshot is idempotent.
  • Operator records and source windows do not overwrite each other.
  • A PostgreSQL suite covers the above. The OpenAPI document, clients and, if schedulingctl gains commands, the CLI catalogue are regenerated.
  • The Scheduling security page adds source-published supply and busy sources to its trust boundaries. The repository guidance's "operator-anchored supply" sentence is updated in the same change.

Delivery

Implemented in one PR with #2731 and the Coordinator operation that follows this issue.

主要语言
Rust
星标
2
派生
0
平均合并
9 小时 48 分钟
30 天内合并 PR
151

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

registrystack/registry-stack 的其他 Issue

查看 registrystack/registry-stack 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。