Skip to main content

Module jobs

Module jobs 

Source
Expand description

Jobs capability: poll long-running jobs. One shared JobDto renders as JSON for agents (GET /api/jobs/<uuid>) and the progress page (GET /jobs/<uuid>) polls that same JSON. The job mechanism itself lives in crate::jobs.

Structs§

JobDto
A job as exposed over the API/UI (uuid handle, no internal serial id).

Functions§

api_job
Polls a job by its uuid (the agent twin of the progress page). Token-gated (Actor): jobs carry admin attribution (actor) + operational params, so — like the human /jobs/<uuid> (require_admin) and /api/audit — they are not public (X-10’s sibling read-twin gap).
api_jobs
Lists recent jobs across every background-task capability (import / extend / activate / …) — the fleet-wide pending check the observability mandate requires. ?active=true narrows to the non-terminal (queued/running) jobs; ?limit= caps the page (default 50, max 200). Most-recent first; each carries health + duration_seconds.
job_page
The human progress page; it polls GET /api/jobs/<uuid> (vanilla fetch, no JS framework — D11). Signed-in admins only (unauthenticated → sign-in page); the polled JSON twin is the agent surface.
jobs_page
The human jobs dashboard (HTML twin of api_jobs): recent background jobs with their health, duration and progress — the at-a-glance observability screen. ?active=true shows only pending.
routes
The route set for the jobs capability.