Documentation CLI 0.1.1 · development llms.txt

coldctl connector registry

Pin connector registry trust.

ImplementedLocal trust configuration

Syntax

USAGE

coldctl connector registry [OPTIONS] --url <URL> --root <ROOT> --root-sha256 <ROOT_SHA256>

Arguments & options

Option	Description / default
`--data-dir <PATH>`	Override the OS application data directory
`--url <URL>`	HTTPS registry base URL. Use the verified release registry URL or your trusted registry.
`--root <ROOT>`	Path to the independently verified public TUF root.json.
`--root-sha256 <ROOT_SHA256>`	Independently verified SHA-256 fingerprint of the trusted root file.
`-h, --help`	Print help

Examples

Replace configuration names, paths and JOB_ID with values from your installation. Examples are not executed by this page.

CLI

coldctl connector registry --url https://github.com/coldctl/coldctl/releases/latest/download/ --root root.json --root-sha256 VERIFIED_FINGERPRINT

Operational notes

Use an independently verified TUF root and approved signed packages. Installation and activation are separate from source configuration; incomplete jobs retain exact connector pins.

Verify the fingerprint independently. Never bootstrap trust solely from the downloaded bundle.

Output, placeholders & global flags

View exact CLI help

HELP OUTPUT

Pin a registry's independently verified TUF root. Never trusts keys from a downloaded bundle

Usage: coldctl connector registry [OPTIONS] --url <URL> --root <ROOT> --root-sha256 <ROOT_SHA256>

Options:
      --data-dir <PATH>            Override the OS application data directory
      --url <URL>                  
      --root <ROOT>                
      --root-sha256 <ROOT_SHA256>  
  -h, --help                       Print help