autonomy registry seed-catalog

Seed many bundles into a destination registry in one pass (air-gapped catalog)

Synopsis

Seeds every bundle listed in a catalog file, composing 'registry seed' per
entry. Each entry is replicated, verified (fail-closed), and written to its own
subdirectory under --out (with its own seed-manifest.json + seed.lock); a
catalog-seed-manifest.json roll-up records every entry's immutable result.

Catalog file (YAML):
  version: 1
  entries:
    - from: registry.upstream.example.com/robot-behavior:v1
      to:   localhost:5000/robot-behavior:v1
      copy_policy: true
      pub_key: ./cosign.pub
    - from: registry.upstream.example.com/nav-stack:v2
      to:   localhost:5000/nav-stack:v2
      pub_key: ./cosign.pub

Registry-wide options (--allow-insecure-registry, --skip-verify, --keep-going,
--out) are flags; the file carries only the per-bundle entries. Default is
fail-fast (stop on the first entry that fails); --keep-going attempts every
entry and still exits non-zero if any failed.

Usage

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

Examples

autonomy registry seed-catalog --catalog ./site-a.yaml --out ./seed
  autonomy registry seed-catalog --catalog ./dev.yaml \
      --allow-insecure-registry --skip-verify --keep-going

Options

      --allow-insecure-registry   permit plain-HTTP registries (e.g. localhost)
      --catalog string            path to the catalog YAML; required
      --keep-going                attempt every entry and report failures (still exits non-zero if any failed)
      --out string                directory for catalog-seed-manifest.json + per-entry subdirs (default ".")
      --skip-verify               bypass destination verification for all entries (fail-open; dev only)

See also

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