docs: align scheduling review references
This commit is contained in:
@@ -141,9 +141,13 @@ and the Python client (`App` schedule methods) share these operations:
|
||||
|
||||
## Hypothetically used as follows
|
||||
|
||||
EXECUTABLE example (runs in CI as
|
||||
`tests/examples/test_scheduled_deployment_example.py`; run it with
|
||||
`uv run pytest -q tests/examples/test_scheduled_deployment_example.py`):
|
||||
The complete runnable setup is covered by
|
||||
[`tests/examples/test_scheduled_deployment_example.py`](../tests/examples/test_scheduled_deployment_example.py)
|
||||
(run it with `uv run pytest -q tests/examples/test_scheduled_deployment_example.py`).
|
||||
The abbreviated sequence below is illustrative rather than executable as
|
||||
written because it elides setup details:
|
||||
|
||||
ILLUSTRATIVE example (the runnable test above contains the complete setup):
|
||||
|
||||
```python
|
||||
server = build_local_static_workflow_server(root, schedules=True)
|
||||
@@ -168,8 +172,7 @@ page = await server.api.schedules.list_schedule_occurrences(
|
||||
await service.stop()
|
||||
```
|
||||
|
||||
ILLUSTRATIVE example (not executed; shows a cron week with an operator
|
||||
pause — same calls, longer horizons):
|
||||
Longer-horizon operator example (also illustrative and not executed):
|
||||
|
||||
```python
|
||||
# Monday: an hourly report, latest-wins catch-up, at most two at once.
|
||||
|
||||
Reference in New Issue
Block a user