CLI commands
deploy
create or update apis
Usage:
cortex deploy [CONFIG_FILE] [flags]
Flags:
-e, --env string environment to use
-f, --force override the in-progress api update
-y, --yes skip prompts
-o, --output string output format: one of pretty|json (default "pretty")
-h, --help help for deployget
get information about apis or jobs
Usage:
cortex get [API_NAME] [JOB_ID] [flags]
Flags:
-e, --env string environment to use
-w, --watch re-run the command every 2 seconds
-o, --output string output format: one of pretty|json (default "pretty")
-v, --verbose show additional information (only applies to pretty output format)
-h, --help help for getlogs
stream logs from a single replica of an api or a single worker for a job
Usage:
cortex logs API_NAME [JOB_ID] [flags]
Flags:
-e, --env string environment to use
-y, --yes skip prompts
-h, --help help for logspatch
update API configuration for a deployed API
Usage:
cortex patch [CONFIG_FILE] [flags]
Flags:
-e, --env string environment to use
-f, --force override the in-progress api update
-o, --output string output format: one of pretty|json (default "pretty")
-h, --help help for patchrefresh
restart all replicas for an api (without downtime)
Usage:
cortex refresh API_NAME [flags]
Flags:
-e, --env string environment to use
-f, --force override the in-progress api update
-o, --output string output format: one of pretty|json (default "pretty")
-h, --help help for refreshdelete
delete any kind of api or stop a batch job
Usage:
cortex delete API_NAME [JOB_ID] [flags]
Flags:
-e, --env string environment to use
-f, --force delete the api without confirmation
-c, --keep-cache keep cached data for the api
-o, --output string output format: one of pretty|json (default "pretty")
-h, --help help for deleteprepare-debug
prepare artifacts to debug containers
Usage:
cortex prepare-debug CONFIG_FILE [API_NAME] [flags]
Flags:
-h, --help help for prepare-debugcluster up
spin up a cluster on aws
Usage:
cortex cluster up CLUSTER_CONFIG_FILE [flags]
Flags:
-e, --configure-env string name of environment to configure (default: the name of your cluster)
-y, --yes skip prompts
-h, --help help for upcluster info
get information about a cluster
Usage:
cortex cluster info [flags]
Flags:
-c, --config string path to a cluster configuration file
-n, --name string name of the cluster
-r, --region string aws region of the cluster
-o, --output string output format: one of pretty|json (default "pretty")
-e, --configure-env string name of environment to configure
-d, --debug save the current cluster state to a file
-y, --yes skip prompts
-h, --help help for infocluster scale
update the min/max instances for a nodegroup
Usage:
cortex cluster scale [flags]
Flags:
-n, --name string name of the cluster
-r, --region string aws region of the cluster
--node-group string name of the node group to scale
--min-instances int minimum number of instances
--max-instances int maximum number of instances
-y, --yes skip prompts
-h, --help help for scalecluster down
spin down a cluster
Usage:
cortex cluster down [flags]
Flags:
-c, --config string path to a cluster configuration file
-n, --name string name of the cluster
-r, --region string aws region of the cluster
-y, --yes skip prompts
--keep-aws-resources skip deletion of resources that cortex provisioned on aws (bucket contents, ebs volumes, log group)
-h, --help help for downcluster export
download the code and configuration for APIs
Usage:
cortex cluster export [API_NAME] [API_ID] [flags]
Flags:
-c, --config string path to a cluster configuration file
-n, --name string name of the cluster
-r, --region string aws region of the cluster
-h, --help help for exportenv configure
configure an environment
Usage:
cortex env configure [ENVIRONMENT_NAME] [flags]
Flags:
-o, --operator-endpoint string set the operator endpoint without prompting
-h, --help help for configureenv list
list all configured environments
Usage:
cortex env list [flags]
Flags:
-o, --output string output format: one of pretty|json (default "pretty")
-h, --help help for listenv default
set the default environment
Usage:
cortex env default [ENVIRONMENT_NAME] [flags]
Flags:
-h, --help help for defaultenv rename
rename an environment
Usage:
cortex env rename EXISTING_NAME NEW_NAME [flags]
Flags:
-h, --help help for renameenv delete
delete an environment configuration
Usage:
cortex env delete [ENVIRONMENT_NAME] [flags]
Flags:
-h, --help help for deleteversion
print the cli and cluster versions
Usage:
cortex version [flags]
Flags:
-e, --env string environment to use
-h, --help help for versioncompletion
generate shell completion scripts
to enable cortex shell completion:
bash:
add this to ~/.bash_profile (mac) or ~/.bashrc (linux):
source <(cortex completion bash)
note: bash-completion must be installed on your system; example installation instructions:
mac:
1) install bash completion:
brew install bash-completion
2) add this to your ~/.bash_profile:
source $(brew --prefix)/etc/bash_completion
3) log out and back in, or close your terminal window and reopen it
ubuntu:
1) install bash completion:
apt update && apt install -y bash-completion # you may need sudo
2) open ~/.bashrc and uncomment the bash completion section, or add this:
if [ -f /etc/bash_completion ] && ! shopt -oq posix; then . /etc/bash_completion; fi
3) log out and back in, or close your terminal window and reopen it
zsh:
option 1:
add this to ~/.zshrc:
source <(cortex completion zsh)
if that failed, you can try adding this line (above the source command you just added):
autoload -Uz compinit && compinit
option 2:
create a _cortex file in your fpath, for example:
cortex completion zsh > /usr/local/share/zsh/site-functions/_cortex
Note: this will also add the "cx" alias for cortex for convenience
Usage:
cortex completion SHELL [flags]
Flags:
-h, --help help for completionLast updated