Bolt should exit with code 1 when erroring unless we receive invalid input #2998
Labels
Bug
Bug reports and fixes.
Comments
lucywyman
added a commit
to lucywyman/bolt
that referenced
this issue
Aug 26, 2021
Previously, Bolt would exit with code 1 for any CLI parsing errors and code 2 for any other errors raised while executing Bolt, which is [backwards from industry standards](https://tldp.org/LDP/abs/html/exitcodes.html). This modifies Bolt to exit with 1 whenever it is not successful. It'd be great to eventually exit with 2 whenever we raise `Bolt::CLIError`, but Ruby doesn't seem to have a way to set the exit code when raising errors and any larger changes seem like more work than they're worth. !bug * **Return exit code 1 instead of 2 when Bolt errors** ([puppetlabs#2998](puppetlabs#2998)) Bolt will now exit with code 1 instead of 2 whenever a Bolt operation fails.
beechtom
added a commit
that referenced
this issue
Sep 1, 2021
(GH-2998) Exit with code 1 when Bolt errors
|
Closed by #2999 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
We currently will always exit with code 2 when Bolt errors, when exit code 2 is intended to be used when the command can't be parsed, or for things like permissions issues rather than errors from Bolt itself. Bolt errors should result in exit code 1.
The text was updated successfully, but these errors were encountered: