Currently CLI batch files do not fail if a command is valid (i.e. command exists), but fails on the server side. For example, a `cache drop` operation on a non-existant cachce will result in a stderr message being displayed but the batch will succeed and the cli returns with a zero exit code.

It should be possible for a user to configure this behaviour using a mechanism similar to bash's `set -e` option.