Search documentation
karat

+

K

apollo-cli label delete [Experimental]

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

Remove a label from an Apollo resource

Remove a label applied to an Apollo resource.

Arguments: the kind of Apollo resource (see "Supported resource types" below) the identifier of the resource — format depends on the resource type (also below)

The label is identified by its label ID.

Example: apollo-cli label delete product-release com.palantir.product:foo:1.0.0
--label-id release-quality

If you want to remove a label from a resource in an enrollment you are not a member of the primary org for, set the spaceID using the global '--space-id' flag.

Supported resource types: product-release identifier: maven coordinate (e.g. com.palantir.product:foo:1.0.0)

Copied!
1 apollo-cli label delete <resource-type> <resource-id> [flags]

Flags

FlagUse
--dry-runPrint the operations that would be performed
-h, --helpHelp for delete
--label-idID of the label to remove

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

See also