The Kubernetes-native platform (v2).
The Package manager for Kubernetes.
The Kubernetes-native Service Broker.
The Drycc Workflow command-line interface (CLI), or client, allows you to interact with Drycc Workflow.
Install the latest
drycc client for Linux or Mac OS X with:
$ curl -sSL https://raw.githubusercontent.com/drycc/workflow-cli/master/install-v2.sh | bash -s v2.20.0
The installer puts
drycc in your current directory, but you should move it
somewhere in your $PATH:
$ ln -fs $PWD/drycc /usr/local/bin/drycc
The Drycc client comes with comprehensive documentation for every command.
drycc help to explore the commands available to you:
$ drycc help The Drycc command-line client issues API calls to a Drycc controller. Usage: drycc <command> [<args>...] Auth commands:: register register a new user with a controller login login to a controller logout logout from the current controller Subcommands, use `drycc help [subcommand]` to learn more:: ...
To get help on subcommands, use
drycc help [subcommand]:
$ drycc help apps Valid commands for apps: apps:create create a new application apps:list list accessible applications apps:info view info about an application apps:open open the application in a browser apps:logs view aggregated application logs apps:run run a command in an ephemeral app container apps:destroy destroy an application Use `drycc help [command]` to learn more
The CLI reads from the default
client profile, which is located on your
Easily switch between multiple Drycc Workflow installations or users by setting
$DRYCC_PROFILE environment variable or by using the
There are two ways to set the
$ DRYCC_PROFILE=production drycc login drycc.production.com ... Configuration saved to /home/testuser/.drycc/production.json $ DRYCC_PROFILE=~/config.json drycc login drycc.example.com ... Configuration saved to /home/testuser/config.json
The configuration flag works identically to and overrides
$ drycc whoami -c ~/config.json You are drycc at drycc.example.com
If your workstation uses a proxy to reach the network where the cluster lies,
https_proxy environment variable to enable proxy support:
$ export http_proxy="http://proxyip:port" $ export https_proxy="http://proxyip:port"
Configuring a proxy is generally not necessary for local Minikube clusters.
Plugins allow developers to extend the functionality of the Drycc Client, adding new commands or features.
If an unknown command is specified, the client will attempt to execute the command as a dash-separated command. In this case,
drycc resource:command will execute
drycc-resource with the argument list
command. In full form:
$ # these two are identical $ drycc accounts:list $ drycc-accounts list
Any flags after the command will also be sent to the plugin as an argument:
$ # these two are identical $ drycc accounts:list --debug $ drycc-accounts list --debug
But flags preceding the command will not:
$ # these two are identical $ drycc --debug accounts:list $ drycc-accounts list