Zato administrators use both the web admin and the command line interface (CLI) to manage Zato environments. These two methods don’t overlap, both have their distinct responsibilites.
While the web admin has been created with the goal of aiding in running an already existing environment, the CLI has been created with the goal of preparing Zato environments or otherwise addressing situations that need access to an operating system Zato components are installed on.
Commands offered by the CLI always need an actual access to the file system via, for instance, ssh. They can’t be issued remotely through the web admin.
All commands are run using a single executable called zato.
|zato ca||Certificate Authority (CA) management|
|zato check-config||Sanity checks against a component’s config (currently limited to servers only)|
|zato component-version||Shows a Zato component’s version|
|zato create||Creates a Zato object|
|zato decrypt||Decrypts secrets using a Zato component’s private key|
|zato delete||Deletes a Zato component|
|zato encrypt||Encrypts secrets using a Zato component’s public key|
|zato info||Shows information on a Zato component|
|zato from-config||Runs commands from a config file|
|zato quickstart||Quickly sets up a working Zato environment|
|zato service||Service management|
|zato start||Starts a Zato component|
|zato stop||Stops a Zato component|
|zato update||Updates parts of a Zato component|
Each Zato command can make use of the following options:
|-h, –help||Displays given command’s help message|
|–store-log||Stores a command execution log in the directory the command has been run in.|
|–verbose||Displays verbose information during the command’s execution|
|–store-config||Outputs the command’s input parameters to a config file in the directory the command has been run in. The file can be later used with the from-config command.|
All the input parameters stored by the –store-config option are in plain text, including passwords and any other secrets.