Skip to content

Cani alpha add metadata

cani alpha add metadata

Create metadata definitions (roles, statuses, tags) in the local inventory.

Synopsis

Create metadata definitions in the local inventory.

Metadata definitions are stored under providerMetadata in the datastore and are used during export to create the corresponding objects in Nautobot.

Use a subcommand to create a specific metadata type: cani alpha add metadata role cani alpha add metadata status cani alpha add metadata tag

Options

      --color string            Color (hex, e.g. aa1409)
      --content-types strings   Content types (e.g. dcim.device,dcim.rack)
      --description string      Description
  -h, --help                    help for metadata

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