• Apollo
    • Search documentation
    karat

    +

    K

    ReferenceApollo CLIapollo-cli release-channel export [Experimental]

    apollo-cli release-channel export [Experimental]

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

    Export all product releases from a release channel to a YAML file

    Export all product releases from a specified release channel to a YAML file.

    This command fetches all products in the space, then for each product queries releases on the specified release channel. The output file contains Maven coordinates that can be used with 'apollo-cli release-channel add -f' or 'apollo-cli release-channel import' to add releases to another release channel.

    Example usage:

    Export releases from MY_CHANNEL to releases.yaml

    apollo-cli release-channel export MY_CHANNEL -o releases.yaml

    Export to a specific directory

    apollo-cli release-channel export STABLE -o output/stable-releases.yaml

    Export only the latest version of each product

    apollo-cli release-channel export MY_CHANNEL -o releases.yaml --latest

    Output file format (YAML):

    • com.example:foo:1.0.0
    • com.example:bar:2.3.4
    Copied!
    1
apollo-cli release-channel export <release-channel> [flags]

    Flags

    FlagUse
    -h, --helpHelp for export
    -l, --latestExport only the latest version for each product
    -o, --outputOutput file path

    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
    -e, --environmentEnvironment ID (including suffix) to use for environment-scoped commands
    --http-timeoutTimeout in minutes for all apollo requests
    -k, --insecure-skip-verifySkip verification of server certificate
    --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