diff options
| author | John Keiser <john@johnkeiser.com> | 2016-08-08 12:01:57 -0700 |
|---|---|---|
| committer | John Keiser <john@johnkeiser.com> | 2016-08-08 12:58:56 -0700 |
| commit | bacc818e165cb619f10eba79ec2058dfe0651e65 (patch) | |
| tree | 88389f011733ee2fbf42daf0ab1c787fdeb02d09 | |
| parent | 1c1a1bc67eef7544af0bbe7dc57a32a1bed754e9 (diff) | |
| download | chef-jk/changelog.tar.gz | |
Clear DOC_CHANGES (empty for 12.13)jk/changelog
| -rw-r--r-- | DOC_CHANGES.md | 13 |
1 files changed, 1 insertions, 12 deletions
diff --git a/DOC_CHANGES.md b/DOC_CHANGES.md index 069cdc62b4..fadd382cbb 100644 --- a/DOC_CHANGES.md +++ b/DOC_CHANGES.md @@ -6,15 +6,4 @@ Example Doc Change: Description of the required change. --> -## Doc changes for Chef 12.11 - -### RFC 062 Exit Status Support - -Starting with Chef Client 12.11, there is support for the consistent, standard exit codes as defined in [Chef RFC 062](https://github.com/chef/chef-rfc/blob/master/rfc062-exit-status.md). - -With no additional configuration when Chef Client exits with a non-standard exit code a deprecation warning will be issued advising users of the upcoming change in behavior. - -To enable the standardized exit code behavior, there is a new setting in client.rb. The `exit_status` setting, when set to `:enabled` will enforce standarized exit codes. In a future release, this will become the default behavior. - -If you need to maintain the previous exit code behavior to support your current workflow, you can disable this (and the deprecation warnings) by setting `exit_status` to `:disabled`. - +## Doc changes for Chef 12.13 |