plugin-pod
| Placement | compiled-in (in-process) |
| Source | github.com/opencharly/charly/candy/plugin-pod |
| Version | 2026.201.0000 |
| Candy | plugin-pod |
This plugin is listed in charly/charly.yml’s compiled_plugins:, so its providers are compiled into the charly binary and register in-process.
Providers
Section titled “Providers”The reserved words this plugin serves:
config— command classcp— command classlogs— command classremove— command classrestart— command classservice— command classshell— command classstart— command classstop— command classupdate— command classvolume— command class
What it does
Section titled “What it does”The charly start/stop/restart/config/shell/service/logs/remove/cp/
volume pod-lifecycle CLI — a COMMAND-class charly plugin (github.com/opencharly/sdk),
the CLI sibling of candy/plugin-deploy-pod (which keeps deploy:pod out-of-process,
untouched — mirroring the candy/plugin-vm / candy/plugin-deploy-vm split). Each command
word is INDEPENDENT (no shared parent). charly restart is pure sdk/kit + sdk/deploykit
logic (deploykit.RestartPodService) with zero host coupling. The registry-bound commands
(start/stop/…) forward their authored flags, as sdk/spec wire requests, to a per-command
HostBuild seam — the host reconstructs the original core orchestration struct and runs
its Run() logic VERBATIM (mirroring candy/plugin-bundle’s deploy-add/deploy-del seams),
because the provider REGISTRY (ResolveTarget, the plugin loader) is a core Mechanism a
plugin cannot import or hold. COMPILED-IN, it dispatches IN-PROC via Invoke(OpRun), so the
handlers run in charly’s own process and inherit real stdio/TTY natively. Placement of
THIS candy is independent of candy/plugin-deploy-pod’s placement.
See also the candy reference for this candy’s install surface.