plugin-fleet
| Version | 2026.193.1200 |
| Repo | box/github.com/opencharly/plugin-fleet:v2026.250.0829 |
| Plugin | yes — see the plugin reference |
The charly deploy … deployment CLI, externalized into a COMPILED-IN
command:deploy plugin (F8) mirroring candy/plugin-vm. charly deploy add
/ del / show / export / import / reset / path / status /
from-box dispatch IN-PROC via Invoke(OpRun) (runDeployCommand →
kong-parse the DeployCmd tree), so the handlers run in charly’s OWN process
and inherit charly’s real stdio/TTY natively. Each leaf FORWARDS its parsed
flags to the host over four generic host-build seams — HostBuild deploy-add /
deploy-del / deploy-from-box (the deploy dispatch) and deploy-config (the
show/export/import/reset/status config-management ops) — where the host runs
the existing deploy orchestration VERBATIM: the config loader + deploy ledger,
the InstallPlan compiler, and the deploy-dispatch kernel (ResolveTarget →
the plugin-side deploy dispatcher over the executor reverse channel) all STAY
core. path
resolves plugin-side via kit.DefaultDeployConfigPath (no seam). command:deploy
is COMPILED-IN; its grammar is prescanned into the CLI.
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
check |
the command:deploy plugin ships a buildable Go module the host compiles into charly; the full charly deploy add/del deploy dispatch is exercised by the Go e2e + the live R10 roster |