ump_workflow.cli

module ump-workflow

ump-workflow: inspect, check, run and serve a bundle from the terminal.

Exit codes: 0 ok (inspect read it; check found the input usable; run answered from the saved state or a refit); 1 fallback (check: the input is not available; run: the answers are the labelled Tier D summary); 2 usage error; 3 the bundle was refused (BUNDLE_TAMPERED, BUNDLE_INVALID), the data file could not be read or parsed as CSV, or the -o file could not be written (the answers are still printed). Errors go to stderr as one line, never a traceback.

serve (needs the serve extra) serves one bundle as an app on UMP’s adapter contract until stopped: from a local folder, or --artifact <model_id> fetched through core and trusted only as far as its approval vouches. There is no flag that trusts code by hand. The port is bound before anything is fetched or registered, so a busy port registers nothing; a bundle fetched without --dest is rebuilt in a temp folder removed when the server stops (Ctrl-C or SIGTERM, which kill, scripts/stop.sh, docker stop and Cloud Run send). Exit codes: 0 after a clean stop (SIGTERM included), 2 usage (including the extra not installed or a port outside 0 to 65535), 3 the port could not be bound, or the bundle was refused or could not be fetched.

Functions

main

function

def main(argv: list[str] | None = None) -> int

Source: packages/ump-workflow/src/ump_workflow/cli.py, line 236

Constants

Name	Type	Value	Description
SERVE_DEFAULT_PORT		8210	Proposed default port of ump-workflow serve (one app per bundle; a second one takes --port).