-
Notifications
You must be signed in to change notification settings - Fork 3
CLI
<PRODIGY_HOME>/prodigy-cli/target/bin/prodigy script handles commands to operate Prodigy deployment. There are two ways of execution of prodigy script as the following synopses.
One liner (for including into your own operational scripts):
$ prodigy [options] [command] [parameters]
REPL:
$ prodigy [options]
prodigy script takes options of -v or --verbose to print verbose logs and --config <path> to specify the configuration file to load.
There are some commands available to pass the script as below.
Deploys new control plane stack with the specified profile.
deploy <profile>
core profile is reserved and not allowed to specify.
Prints all existing profile configurations, or changes the default and current profile to the specified one.
configure
If no options are passed, it prints all existing profile configurations.
configure --default <profile>
If --default option is passed, it changes the default and current profile to the specified one.
Schedules a new fault entry of the specified fault name and parameters.
inject <fault-name> [json-params]
json-params must be a string of valid JSON object like {"param1" : "hello", "param2" : 2}.
Unschedules existing fault entry of the specified fault id.
eject <fault-id>
Prints general status of all existing fault entries, or detail status of the specified one.
status
If no arguments are passed, it prints general status of all existing fault entries.
status <fault-id>
If fault-id is passed, it prints detail status of the fault of the specified id.
Adds fault classes to the Prodigy deployment.
push <fault-jar>
fault-jar must be the path to JAR file which includes fault classes to add.
Prints the name and class of all existing fault classes.
faults
Prints help content of the specified command.
help <command>
Prints available commands.
hint
Exits from the current REPL session.
exit