diff options
| author | Steven Murawski <steven.murawski@gmail.com> | 2017-04-06 10:45:31 -0500 |
|---|---|---|
| committer | Thom May <thom@chef.io> | 2017-04-06 22:28:53 +0100 |
| commit | 35c858d12b7e1fecbfd6069019d69b6c5631f826 (patch) | |
| tree | 4ee1311b47a42160ce31b800de4f389615bd94bd /RELEASE_NOTES.md | |
| parent | 29d2b81df0dc87c1d0f1557ffc110e7eec68d45c (diff) | |
| download | chef-35c858d12b7e1fecbfd6069019d69b6c5631f826.tar.gz | |
exit status behavior change for Chef 13
Signed-off-by: Steven Murawski <steven.murawski@gmail.com>
Diffstat (limited to 'RELEASE_NOTES.md')
| -rw-r--r-- | RELEASE_NOTES.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index f8b841c76e..e01bfc9097 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -378,3 +378,9 @@ fix more problems than it solves, but may causes issues for some use cases. ### Default guard clauses (`not_if`/`only_if`) do not change the PATH or other env vars The implementation switched to `shell_out_with_systems_locale` to match `execute` resource, etc. + +### Chef Client will now exit using the RFC062 defined exit codes + +Chef Client will only exit with exit codes defined in RFC 062. This allows other tooling to respond to how a Chef run completes. Attempting to exit Chef Client with an unsupported exit code (either via `Chef::Application.fatal!` or `Chef::Application.exit!`) will result in an exit code of 1 (GENERIC_FAILURE) and a warning in the event log. + +When Chef Client is running as a forked process on unix systems, the standardized exit codes are used by the child process. To actually have Chef Client return the standard exit code, `client_fork false` will need to be set in Chef Client's configuration file. |