Expand description
The POST /v1/tasks entry point — see task::TaskApplication.
TaskApplication — the POST /v1/tasks entry point.
Input: BlueprintRef (Inline / Id) plus a TaskSpec. Output:
(CapToken, TaskId, version). Once the Blueprint is resolved, the
engine-side operations (bind + attach + start_task) are
delegated to [TaskLaunchService].
Structs§
- Task
Application - The
POST /v1/tasksApplication— resolves aBlueprintRefand runs it to completion throughTaskLaunchService. - Task
Application Input - Input to
TaskApplication::handle— thePOST /v1/tasksrequest body once decoded. - Task
Application Output - Result of a successful
TaskApplication::handlecall.
Enums§
- Blueprint
Ref - How a task entry says the Blueprint should be resolved.
- Task
Application Error - Failure modes of
TaskApplication::handleandTaskApplication::resolve. - Version
Selector - How to pick a generation — a
versioninside the store.