Skip to content

plugin-egress

Version 2026.181.0001
Repo superproject
Plugin yes — see the plugin reference

EGRESS VALIDATION plugin (M16) — gates the config artifacts charly WRITES to a system (cloud-init user-data/meta/net, k8s manifests + kustomization, traefik routes, install-ledger records, the Containerfile + systemd/supervisord units, the libvirt domain XML) against a CUE schema BEFORE the bytes hit disk. The validation logic + the egress CUE schemas (incl. the vendored cloud-config) live here; charly’s in-core ValidateEgress* functions are a thin shim that Invokes this plugin’s OpValidate. Compiled-in (the build/deploy hot paths call it many times).

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 egress validation plugin ships a buildable Go module the host compiles in