akka optimize use-cases label
Name a use-case in the working set
Synopsis
Labels are drafts until a freeze fixes them. A use-case already frozen into a manifest cannot be relabelled.
Two use-cases in the working set may not share a label. Reusing a label from an earlier manifest is allowed, and is how the same use-case keeps its name across freezes.
akka optimize use-cases label ID LABEL [flags]
Options inherited from parent commands
--cache-file string location of cache file (default "~/.akka/cache.yaml")
--config string location of config file (default "~/.akka/config.yaml")
--context string configuration context to use
--disable-prompt Disable all interactive prompts when running akka commands. If input is required, defaults will be used, or an error will be raised.
This is equivalent to setting the environment variable AKKA_DISABLE_PROMPTS to true.
--force Skip the confirmation prompt
--jq string Filter the JSON output with a jq expression
--json string Output JSON with only these fields; --json= lists the fields a command offers
--no-color Print without color, as NO_COLOR does
-o, --output string set output format to one of [text,json,json-compact,go-template=] (default "text")
--page-mode string the mode for paging, either paged, buffered or auto. (default "auto")
-q, --quiet set quiet output (helpful when used as part of a script)
--region string Region to use if the project has more than one region
--timeout duration client command timeout (default 10s)
--trainer-url string Trainer service URL (default http://localhost:9001, or TRAINER_URL)
--url string Optimize service URL (default http://localhost:9010, or OPTIMIZE_URL)
--use-grpc-web use grpc-web when talking to Akka APIs. This is useful when behind corporate firewalls that decrypt traffic but don't support HTTP/2.
--verbose set verbose output
SEE ALSO
-
akka optimize use-cases - Discovered use-cases, and the manifests frozen from them