Skip to content

cub component create

cub component create

Create a component

Synopsis

Create a Component entity, which decides which ChangeWorkflows promotions and releases of its Variants may use, whether one is required, and whether changes to the configuration of the Variants' Units have to be made in a ChangeSet or under a ChangeOrder.

ChangeWorkflows are addressed as / or by UUID.

Examples:

  # Create a component
  cub component create my-app

  # Create a component that requires one of two ChangeWorkflows to promote and release
  cub component create my-app --require-change-workflow \
    --allowed-change-workflow platform/standard-rollout \
    --allowed-change-workflow platform/hotfix

  # Create a component whose variants' units change only in a ChangeSet or under a ChangeOrder
  cub component create my-app --require-change-tracking

  # Create a component from a JSON definition
  cub component create my-app --from-stdin < component.json
cub component create <name> [flags]

Options

      --allow-exists                      Allow creation of resources that already exist
      --allowed-change-workflow strings   ChangeWorkflow, as <space>/<slug> or UUID, that promotions, releases, and changesets opened on the variants' units may use (can be repeated or comma-separated)
      --annotation strings                annotations in key=value format; can separate by commas and/or use multiple instances of the flag
      --backing-unit-space string         space, by slug or UUID, for the backing Units --with-backing-units creates; required with it, since a Component is in no space of its own
      --delete-gate strings               delete gates in key[=true] format; can separate by commas and/or use multiple instances of the flag
      --display-name string               friendly name for the entity, which need not be unique or URL-safe; an entity without one is shown by its slug
      --dry-run                           report what the command would write, and write nothing
      --filename string                   Read the ConfigHub entity's fields, as YAML or JSON, from file, URL (https://), or stdin (-), as --from-stdin does; mutually exclusive with --from-stdin
      --from-stdin                        Read the ConfigHub entity's fields, as YAML or JSON, from stdin; merged with command arguments on create, and merged with command arguments and existing entity on update. A field the entity does not have, or one only the server sets, is refused; cub <entity> explain lists the fields
  -h, --help                              help for create
      --hidden-reason string              hide the entity, giving the reason as a name such as Archived: lists and bulk operations leave it out unless --include-hidden names the reason (use '-' to clear, which shows the entity again)
      --label strings                     labels in key=value format; can separate by commas and/or use multiple instances of the flag
  -o, --output string                     Output format. One of: json, yaml, name, wide, mutations, jq=<expr>, yq=<expr>, custom-columns=<spec>
      --permission strings                permission in format Action:UserIDOrUsername, Action:group:GroupSlugOrID for a group you belong to, or Action:serviceaccount:ServiceAccountSlugOrID (e.g., Manage:user@example.com, View:group:platform, View:serviceaccount:deploy-bot, can be repeated)
      --quiet                             No default output.
      --require-change-tracking           require changes to the configuration of the variants' units to be made in a changeset open on the unit or under a change order
      --require-change-workflow           require a ChangeWorkflow to promote and release, and to open a changeset on the variants' units
      --set stringArray                   set a field of the Component by its path, as <path>=<value> (repeatable). A path is field names separated by dots; a list element is addressed as ?<key>=<value> or by position, as in Stages.?Name=prod.WhereSpace, and is added if it is not there. A list of plain values separates them with ';'; an object or a list of objects is given as YAML or JSON. A reference is given as it is elsewhere, by slug, <space>/<slug> or ID. With --patch, only a path with no list element in it
      --unset stringArray                 clear a field of the Component by its path, or remove the list element the path ends at (repeatable)
      --verbose                           Detailed output, additive with default output
      --with-backing-units                give each Component the bulk operation writes a backing Unit if it has none: a ConfigHub/YAML Unit holding its configuration, kept in step with it

Options inherited from parent commands

      --context string   The context to use for this command
      --debug            Debug output

SEE ALSO