Skip to content

Cani alpha add prefix

cani alpha add prefix

Add an IP prefix (subnet) to the inventory.

Synopsis

Add an IP prefix to the inventory in CIDR notation.

Examples: cani alpha add prefix 10.0.0.0/16 --type container --role infrastructure cani alpha add prefix 10.0.1.0/24 --type network --role management --vlan "Management" cani alpha add prefix 10.0.1.128/25 --type pool --role dhcp-pool

cani alpha add prefix <cidr> [flags]

Options

      --description string   Prefix description
  -h, --help                 help for prefix
      --location string      Location UUID or name
      --role string          Prefix role (e.g. management, bmc, infrastructure)
      --type string          Prefix type: container, network, or pool
      --vlan string          Associated VLAN name or UUID
      --vrf string           VRF name

Options inherited from parent commands

  -y, --accept                  Automatically accept recommended values.
  -a, --auto                    Automatically recommend values for parent hardware
      --config string           config file (default "/home/runner/.cani/cani.yml")
      --datastore string        datastore type (json, postgres) (default "json")
      --datastore-path string   override path to the datastore file (for testing)
      --debug                   enable debug mode
  -L, --list-supported-types    List supported hardware types.
      --metadata stringArray    Provider metadata key=value pairs (repeatable)
      --pad-width int           Zero-pad width for sequential names (0 = auto).
  -p, --parent string           Parent item UUID. (default "00000000-0000-0000-0000-000000000000")
      --prefix string           Name prefix for sequential naming (used with --qty).
  -q, --qty int                 Quantity of items to add. (default 1)
      --serial string           Serial number
      --start int               Starting number for sequential names (used with --prefix). (default 1)
      --status string           Status (Active, Available, Connected, Decommissioned, Decommissioning, Deprecated, Deprovisioning, Down, End-of-Life, Extended Support, Failed, Inventory, Maintenance, Offline, Planned, Primary, Provisioning, Reserved, Retired, Secondary, Staging, or any custom status)
      --strict                  require a resolved device type (slug) for all devices (default true)
      --tag stringArray         Tag(s) to apply to the item (repeatable)
      --types-dirs strings      local directories with additional hardware types
      --types-repo-clone        clone types repos that are not yet cached locally
      --types-repo-pull         pull latest changes from types repos on startup
      --types-repos strings     git repo URLs with additional hardware types

SEE ALSO