pub struct FleetRun {Show 14 fields
pub id: FleetRunId,
pub name: String,
pub status: FleetRunStatus,
pub target: Option<FleetRuntimeTarget>,
pub workflow: Option<FleetWorkflowDescriptor>,
pub roles: Vec<String>,
pub max_workers: Option<usize>,
pub task_specs: Vec<FleetTaskSpec>,
pub worker_specs: Vec<FleetWorkerSpec>,
pub labels: BTreeMap<String, String>,
pub security_policy: Option<FleetSecurityPolicy>,
pub created_at: String,
pub updated_at: Option<String>,
pub completed_at: Option<String>,
}Expand description
Top-level fleet run handle.
Fields§
§id: FleetRunId§name: String§status: FleetRunStatus§target: Option<FleetRuntimeTarget>Explicit execution target selected by the managed client.
Older CLI-created runs predate target selection and therefore omit
this field. Runtime API creation always persists it and currently
accepts only FleetRuntimeTarget::ThisComputer.
workflow: Option<FleetWorkflowDescriptor>Named Workflow descriptor that owns this Fleet run.
The durable task specs below remain the executable source of truth; this descriptor keeps the product identity and scheduling policy inspectable without smuggling them through labels.
roles: Vec<String>Canonical named roles declared for the run.
max_workers: Option<usize>Maximum number of workers the manager may drive concurrently.
Older ledgers omit this field; callers fall back to the persisted worker roster when resuming those runs.
task_specs: Vec<FleetTaskSpec>§worker_specs: Vec<FleetWorkerSpec>§labels: BTreeMap<String, String>§security_policy: Option<FleetSecurityPolicy>Legacy replay-only execution policy from pre-0.9.11 ledgers.
New Fleet runs reject this field: Fleet selects identity, while the Runtime owns trust, secrets, approvals, sandboxing, and tool authority.
created_at: String§updated_at: Option<String>§completed_at: Option<String>