edgectl init

Generate a minimal edge daemon configuration file

Synopsis

Generate a minimal valid edge daemon configuration file.

The generated config uses safe defaults for all required fields.
You MUST replace the placeholder TLS paths (cert_file, key_file, ca_file)
with your actual certificate paths before starting edged.

Fleet salt is randomly generated. Keep it secret — it is used for beacon
HMAC privacy (not for transport authorization; mTLS governs that).

Peer format:   <peer-id>@<host>:<port>
Example:       --peer peer-alpha@10.0.0.1:7300

Examples:
  # Write default config to ./edge.yaml
  edgectl init

  # Specify output path and domain ID
  edgectl init --output /etc/edge/edge.yaml --domain-id my-edge-node

  # Include static peers
  edgectl init --peer peer-alpha@10.0.0.1:7300 --peer peer-beta@10.0.0.2:7300

  # Preview without writing
  edgectl init --dry-run

Usage

edgectl init [flags]

Options

      --data-dir string    local segment storage root (default "/var/lib/edge")
      --domain-id string   edge domain identifier (default: hostname)
      --dry-run            print generated config to stdout without writing a file
      --listen string      mTLS listener address (default ":7300")
  -o, --output string      output file path (use "-" for stdout) (default "edge.yaml")
      --peer stringArray   static relay peer in <peer-id>@<host>:<port> format (repeatable)
      --state-dir string   OS-survival state root (default "/data/autonomyops")

Options inherited from parent commands

      --socket string   path to the edged control socket (default "/run/edged/ctl.sock")