jetstan-cli 0.1.0

Engineer-facing CLI for Jetstan fleet operations. Standalone PyPI package (own console script: `jetstan`) that talks to the Control Plane over HTTP - never to PostgreSQL or MQTT directly. Also home to jetstan_deploy.py, the working release tool (relocated here from scripts/), which remains independent of the `jetstan` command surface.

jetstan-cli

Engineer-facing CLI for Jetstan fleet operations. Installs its own console script, jetstan, independently of jetstan-agent — this is a standalone PyPI package, not a submodule of the OTA agent.

jetstan talks to the Control Plane (cloud-logics) over HTTP only. It never talks to PostgreSQL or MQTT directly (see the repo root TECHNICAL.md for the full architecture).

Phase 2.1 status

Exactly three commands exist:

jetstan --help
jetstan --version
jetstan health

Nothing else. jetstan_cli/commands/*.py are documented placeholders for future subcommands (publish, deployment-group, deployment, release) — not wired into the CLI yet, since the Control Plane has no business logic to back them.

jetstan_deploy.py, the working release tool relocated here from the old top-level scripts/, is unrelated to the jetstan command and still runs via python -m jetstan_cli.jetstan_deploy.

Installing

cd jetstan-cli
pip install -e .

Or, once published:

pip install jetstan-cli

Either way, this registers the jetstan console script.

Configuration

jetstan health needs to know where the Control Plane is. Set JETSTAN_API — there is no hardcoded default:

cp .env.example .env
# edit .env: JETSTAN_API=http://127.0.0.1:8123

jetstan_cli/config.py reads this from the environment (or from jetstan-cli/.env for local development, the same convention every other package in this repo already uses).

Usage

jetstan --help
jetstan --version

jetstan health
# ✓ Control Plane Healthy      (exit code 0)
# or
# ✗ Control Plane Unreachable  (exit code 1)

Testing

pip install -e ".[dev]"
pytest