• Apollo
    • Search documentation
    karat

    +

    K

    ReferenceApollo CLIapollo-cli release-channel remove [Experimental]

    apollo-cli release-channel remove [Experimental]

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

    Remove one or more ProductReleases from a ReleaseChannel

    Remove one or more ProductReleases from a ReleaseChannel.

    Provide Maven coordinates with repeatable --maven-coordinate flags, a YAML list using --maven-coordinates-file, or both. Inputs are merged and deduplicated. After updating memberships, the command prints the Maven coordinates it submitted. With --dry-run, it prints the coordinates it would submit.

    Examples: apollo-cli release-channel remove CHANNEL_1
    --maven-coordinate com.palantir.product:foo:1.0.0
    --maven-coordinate com.palantir.product:bar:2.0.0
    --rationale "Remove ProductReleases from CHANNEL_1"

    apollo-cli release-channel remove CHANNEL_1
    --maven-coordinates-file releases.yml
    --rationale "Remove ProductReleases from CHANNEL_1"
    --dry-run

    Copied!
    1
apollo-cli release-channel remove <channel-name> [flags]

    Flags

    FlagUse
    --dry-runPrint the operations that would be performed
    -h, --helpHelp for remove
    --maven-coordinateMaven coordinate of a ProductRelease to remove from the ReleaseChannel (can be specified multiple times)
    -f, --maven-coordinates-fileFile containing a list of maven coordinates (yaml format)
    --rationaleHuman-readable reason for removing ProductReleases from the ReleaseChannel

    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
    -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
    --sso-callback-portLocal loopback port for the SSO OAuth callback; 0 selects an available ephemeral port

    See also