oxide-batch-cli
The minimal guarded operator command line for OxideBatch.
This crate ships the oxide-batch binary and the embeddable library behind it.
It is a thin client over the portable operator, explorer, and retention
services: it owns no correctness rule of its own, writes no metadata directly,
and adds no hosted API, identity system, scheduler, or user interface.
Repository state rather than CLI output is authoritative.
Using the binary
oxide-batch execution list --instance 42 --output json
Configuration resolves per value across explicit options, OXIDE_BATCH_
environment variables, a JSON configuration file, and documented defaults.
Secrets are never accepted as command-line arguments.
export OXIDE_BATCH_REPOSITORY_URL__FILE=/run/secrets/oxide-batch-url
oxide-batch config show --output json
Embedding the library
launch and execution restart are guarded against a job's canonical
DefinitionIdentity, which only the application that owns the job can build. A
host application registers its definitions and drives the same command surface:
use ;
let catalog = new.with?;
let mut host = new;
let mut plan = prepare?;
let category =
dispatch.await;
exit;
The shipped binary registers no definitions, so it serves every command a repository alone can answer and reports a guard rejection for those two. It is not a standalone job-definition loader; it cannot discover a job from a crate, manifest file, or database row.
oxide-batch --help
Documentation
- Operator CLI reference — commands, options, configuration keys, output schema, and exit categories.
- Operator CLI and configuration contract — the accepted observable contract this crate implements.
Features
postgres(default) — thePostgreSQLrepository backend and theoxide-batchbinary. Without it the crate is the runtime-neutral command surface only.
License
Apache-2.0. See LICENSE.