• Apollo
    • Search documentation
    karat

    +

    K

    ReferenceApollo CLIapollo-cli release-channel diff [Experimental]

    apollo-cli release-channel diff [Experimental]

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

    Compare releases between two release channels for products in an environment

    Compare two release channels and show product releases that exist on the source channel but NOT on the target channel, limited to products used in a specific environment.

    This is useful for identifying which releases need to be promoted from one channel to another.

    Example usage:

    Compare DEV channel with STABLE channel for products in an environment

    apollo-cli release-channel diff -e apollo-env-123 -s DEV -t STABLE

    Output as JSON

    apollo-cli release-channel diff -e apollo-env-123 -s DEV -t STABLE -o json

    Show all products including those already up to date

    apollo-cli release-channel diff -e apollo-env-123 -s DEV -t STABLE --all

    Copied!
    1
apollo-cli release-channel diff [flags]

    Flags

    FlagUse
    --allShow all items including those with no changes
    -e, --environmentEnvironment
    -h, --helpHelp for diff
    -s, --source-channelSource release channel to compare from
    -t, --target-channelTarget release channel to compare against

    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", "service-user", or "sso" (default "auto"). If "auto" is specified, the mode is picked from what is configured: "static" if "apollo-token" is set, "service-user" if "apollo-client-id" and "apollo-client-secret" are both set, otherwise "sso" (interactive browser login). Errors if both a bearer token AND (client id OR client secret) 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. If "sso" is specified, an interactive browser-based SSO login against Multipass is used (supports hardware keys like YubiKey); the resulting token is cached per profile and refreshed silently. The login flow is triggered automatically the first time a command needs a token and no valid cached token exists.
    --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
    --space-idSpace ID to use for certain space-scoped commands

    See also