0.7.0 - Breaking changes

Breaking changes

qDup now defaults to abort on non-zero sh exit codes, replacing the -x option that previously enabled the abort on non-zero exit behavior. Use -ix or --ignore-exit-code to disable exit code checking and use the previous default behavior. You can also use the long form sh definition to add ignore-exit-code: true to commands that you know could have a non-zero exit code:

- sh:
    command: rm server.log
    ignore-exit-code: true

New Features:

The add-prompt command now supports an is-shell option. This boolean option tells qDup if the prompt still supports shell commands (e.g. echo and pwd) for checking the exit code and checking the current working directory. Previously, qDup would assume all custom prompts from add-prompt did not support shell commands. The add-prompt would normally indicate we were entering a command line (e.g. hyperfoil's cli.sh) but it could also be used to connect to a container that does support a full shell (e.g. podman exec -it /bin/bash)
The executable jar will now return 1 if the run aborts, the yaml is invalid, or the command line arguments are invalid.

Fixes:

• fix issue where ctrlC on a command would cause qDup to consider it a non-zero exit value
• fix issue where a ssh connection would close and be re-opened twice during abort