scheduling: let a source system publish bookable windows under a source profile
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
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- openapi, postgresql, rust
- Área
- backend-api-design, databases, security
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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 applyreplaces 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/previewand/v1/source-windows/apply, mirroring source-busy: a configured source profile, a bounded snapshot underexpectedRevision, 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 applyneither 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
schedulingctlgains 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.
- Lenguaje dominante
- Rust
- Estrellas
- 2
- Forks
- 0
- Merge medio
- 9 h 48 min
- PR fusionados (30 d)
- 151
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de registrystack/registry-stack
-
area:breg enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
registrystack/registry-stack#2765 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
registrystack/registry-stack#2761 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
registrystack/registry-stack#2743 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
registrystack/registry-stack#2706 ·
Los mantenedores suelen responder en 1 día
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
registrystack/registry-stack#2704 ·
Los mantenedores suelen responder en 1 día
Todos los issues de registrystack/registry-stack
Issues similares
-
[Bug] 建议把黑白主题设置同步到启动页面Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
stackabletech/airflow-operator#898 ·
Los mantenedores suelen responder en 1 día
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Posiblemente ocupada @zyl71 la tomó hoy. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100