Skip to content

plugin-fleet

Placement compiled-in (in-process)
Source github.com/opencharly/plugin-fleet/candy/plugin-fleet
Version 2026.193.1200
Candy plugin-fleet

This plugin is listed in charly/charly.yml’s compiled_plugins:, so its providers are compiled into the charly binary and register in-process.

The reserved words this plugin serves:

  • deploy — command class

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.


See also the candy reference for this candy’s install surface.