docs: make client schedule mapping explicit
This commit is contained in:
@@ -355,9 +355,11 @@ Administration is available through the `WorkflowApi` schedule methods,
|
|||||||
`workflow.schedules.*` RPC, and Python client. The API/transport operations
|
`workflow.schedules.*` RPC, and Python client. The API/transport operations
|
||||||
are `create_schedule`, `get_schedule`, `list_schedules`, `update_schedule`,
|
are `create_schedule`, `get_schedule`, `list_schedules`, `update_schedule`,
|
||||||
`pause_schedule`, `resume_schedule`, `delete_schedule`, and paginated
|
`pause_schedule`, `resume_schedule`, `delete_schedule`, and paginated
|
||||||
`list_schedule_occurrences`; the Python facade maps them to the names listed
|
`list_schedule_occurrences`; the Python facade names these operations
|
||||||
above. Creation validates the trigger, the deployment, the binding shapes, and
|
`create_schedule`, `schedule`, `schedules`, `update_schedule`,
|
||||||
a sample-occurrence
|
`pause_schedule`, `resume_schedule`, `delete_schedule`, and
|
||||||
|
`schedule_occurrences`. Creation validates the trigger, the deployment, the
|
||||||
|
binding shapes, and a sample-occurrence
|
||||||
resolution against the pinned root schema, and starts the consumed
|
resolution against the pinned root schema, and starts the consumed
|
||||||
watermark at creation (no pre-creation backfill). Updates are
|
watermark at creation (no pre-creation backfill). Updates are
|
||||||
revision-checked; pause/resume/delete mirror the poll-loop transitions;
|
revision-checked; pause/resume/delete mirror the poll-loop transitions;
|
||||||
|
|||||||
Reference in New Issue
Block a user