autonomy registry package

Generate a Zarf package definition from a catalog (single-tarball offline transport)

Synopsis

Generates a Zarf package definition (zarf.yaml) that bakes a catalog's source
images into a single offline tarball — "seed a disconnected site from a USB
stick". ADK generates the DEFINITION only (bring your own Zarf runtime); it does
not pull images or build the tarball. Operator flow:

  autonomy registry package --catalog ./site-a.yaml --out ./zarf --name site-a --version 1.0.0
  zarf package create ./zarf                       # bakes the images into a tarball
  # carry zarf-package-*.tar.zst across the air gap, then on the edge host:
  zarf package deploy zarf-package-*.tar.zst       # pushes into the edge registry

The generated 'images' are the catalog's SOURCE (from) refs — what Zarf pulls
and bakes; Zarf rewrites them to the destination registry at deploy time. The
catalog file is the same schema as 'registry seed-catalog'.

Usage

autonomy registry package --catalog <file.yaml> [flags]

Examples

autonomy registry package --catalog ./site-a.yaml --out ./zarf
  autonomy registry package --catalog ./site-a.yaml --name site-a --version 1.2.3

Options

      --catalog string       path to the catalog YAML (same schema as seed-catalog); required
      --description string   Zarf package metadata.description
      --name string          Zarf package metadata.name (default: adk-bundles; sanitized to a Zarf-legal name)
      --out string           directory for the generated zarf.yaml (default ".")
      --version string       Zarf package metadata.version (default: 0.0.0)

See also

• autonomy registry — Seed and govern OCI registries for edge / air-gapped deployments