• Apollo
    • Search documentation
    karat

    +

    K

    ReferenceApollo CLIapollo-cli product promotion append [Experimental]

    apollo-cli product promotion append [Experimental]

    This command is Experimental. To enable this command, run the apollo-cli configure command and enable V2 experimental commands.

    Append promotion pipeline stages from a template

    Append promotion pipeline stages to a product's existing pipeline from a YAML template file.

    This command merges template stages into the existing pipeline with conflict detection:

    • Stages are identified by their source and target release channels
    • Conflicting stages (same source->target) prompt for override confirmation
    • Non-conflicting stages are appended to the existing pipeline

    MODES: Single product: apollo-cli product promotion append --file stages.yaml Bulk (environment): apollo-cli product promotion append --environment --file stages.yaml

    CONFLICT RESOLUTION: --dry-run Preview changes without applying (shows "would override" for conflicts) --override Auto-override all conflicts without prompting (default) Interactive prompt for each conflict

    Example template file (stages.yaml): stages: - sourceReleaseChannel: BETA targetReleaseChannel: RELEASE type: zeroCanary zeroCanary: soakTimeInMinutes: 1440 productLabelConditions: - labelId: "security.palantir.build/approved" possibleLabelValues: ["true"]

    Example:

    Append stages to a single product's pipeline

    apollo-cli product promotion append com.example --file stages.yaml

    Preview changes without applying (dry run)

    apollo-cli product promotion append com.example --file stages.yaml --dry-run

    Append stages to all products in an environment

    apollo-cli product promotion append --environment my-env-id --file stages.yaml

    Auto-override conflicts without prompting

    apollo-cli product promotion append --environment my-env-id --file stages.yaml --override

    Copied!
    1
apollo-cli product promotion append [product-id] [flags]

    Flags

    FlagUse
    --dry-runPrint the operations that would be performed
    -e, --environmentEnvironment
    -f, --fileA single input file
    -h, --helpHelp for append
    --overrideOverride conflicts without prompting
    --space-idSpace ID

    Flags inherited from parent commands

    FlagUse
    --apollo-client-idClient ID to use for generating Bearer Token
    --apollo-client-secretClient secret to use for generating Bearer Token
    --apollo-tokenBearer Token to use for authenticated endpoints
    --apollo-token-providerSpecifies how the Bearer Token used for authenticated Apollo endpoint calls is provided. Valid values are "auto", "static", or "service-user" (default "auto"). If "auto" is specified, will use either the Bearer Token provided by "apollo-token" or a Bearer Token obtained by using "apollo-client-id" and "apollo-client-secret" to generate a token from Multipass depending on which values are set (but will error if both values are set). If "static" is specified, the token provided by "apollo-token" is used. If "service-user" is specified, "apollo-client-id" and "apollo-client-secret" are used to generate a token from Multipass.
    --apollo-urlBase URL for Apollo that is used to derive the API endpoints
    --debugEnable debug level logging
    --http-timeoutTimeout in minutes for all apollo requests
    -k, --insecure-skip-verifySkip verification of server certificate
    -o, --outputOutput format (json,yaml,pretty)
    --profileUse a specific profile from your configuration file
    --quietDo not print log output to stderr

    See also