Documentation
¶
Overview ¶
Command zarf_package_deploy answers Ansible as the zarf_package_deploy module.
It is the second entry point the colonel_byte.zarf collection invokes, and it is the same shape as cmd/zarf/init: take over standard output, read the module's JSON parameters, render the zarf command line, run the installed zarf, follow the deployment, and write one JSON object. Everything it does is in internal/zarfmod.
Deploy exists beside init because neither is enough on its own. A cluster whose init package disables k3s local-storage has no StorageClass for zarf's registry to claim, so the registry cannot be initialised until a storage provider has been deployed, and the provider cannot be deployed until the cluster has been initialised far enough to hold it. The playbook in test/e2e/zarf/testdata walks that around: a seed-only init, the provider, then the rest of init. It is modeled on the uds-bundle at https://github.com/colonel-byte/uds-bundles/blob/main/upstream/init-local-path/uds-bundle.yaml.
Source Files