zato from-config

Overview

Runs commands from a file previously created by running any other command with the –store-config switch. That is, it’s possible to store a command’s input parameters and replay them later on using the from-config command.

From the command’s which is being exeucted point of view, there is no difference whether it’s run directly or using the from-config mechanism. For instance, both of the methods below result in exactly the same action being performed (dropping all ODB objects, in this case).

$ zato delete odb postgresql localhost 5432 zato1 zatodb1 --odb_password mysecret
OK
$
$ cat ./zato.2013_01_10_21_37_18_387928.config
# 2013_01_10_21_37_18_387928 - zato1@dev3
command=delete_odb
odb_db_name=zatodb1
odb_host=localhost
odb_password=mysecret
odb_port=5432
odb_type=postgresql
odb_user=zato1
$ zato from-config ./zato.2013_01_10_21_37_18_387928.config
OK
$

The command will complain if any required parameters are missing in the config file. If there's password missing, it will be prompted for. In short, it will be as though the underlying command was invoked directly.

Subcommands

  • (None)

Command-specific parameters

Name Description Example value
path Path to a Zato config file created using the --store-config switch ./zato. 2013_01_10_21_37_18_387928. config

Usage

$ zato from-config [-h] [--store-log] [--verbose] [--store-config]
    path
$ zato from-config ./zato.2013_01_10_21_37_18_387928.config
OK
$

Changelog

Version Notes
1.0 Added initially