diff options
author | Noah Kantrowitz <noah@coderanger.net> | 2018-06-14 19:40:06 -0700 |
---|---|---|
committer | Noah Kantrowitz <noah@coderanger.net> | 2018-06-14 19:40:06 -0700 |
commit | 69848a846c75a2e6fcb0dfd87727256c8f1f5b14 (patch) | |
tree | e2e2056cceffb8a18d062d9c3a661bef11e66f95 /RELEASE_NOTES.md | |
parent | 67530a948eba39ea809ed2e869cec2436f389c89 (diff) | |
download | chef-69848a846c75a2e6fcb0dfd87727256c8f1f5b14.tar.gz |
Add release notes.
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r-- | RELEASE_NOTES.md | 36 |
1 files changed, 36 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index d9747c80df..c7597cf3d2 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -1,5 +1,41 @@ This file holds "in progress" release notes for the current release under development and is intended for consumption by the Chef Documentation team. Please see <https://docs.chef.io/release_notes.html> for the official Chef release notes. +## Silencing deprecation warnings + +While deprecation warnings have been great for the Chef community to ensure +cookbooks are kept up-to-date and to prepare for major version upgrades, sometimes +you just can't fix a deprecation right now. This is often compounded by the +recommendation to enable `treat_deprecation_warnings_as_errors` mode in your +Test Kitchen integration tests, which doesn't understand the difference between +deprecations from community cookbooks and those from your own code. + +Two new options are provided for silencing deprecation warnings: `silence_deprecation_warnings` +and inline `chef:silence_deprecation` comments. + +The `silence_deprecation_warnings` configuration value can be set in your +`client.rb` or `solo.rb` config file, either to `true` to silence all deprecation +warnings or to an array of deprecations to silence. You can specify which to +silence either by the deprecation key name (e.g. `"internal_api"`), the numeric +deprecation ID (e.g. `25` or `"CHEF-25"`), or by specifying the filename and +line number where the deprecation is being raised from (e.g. `"default.rb:67"`). + +An example of setting the `silence_deprecation_warnings` option in your `client.rb` +or `solo.rb`: + +```ruby +silence_deprecation_warnings %w{deploy_resource chef-23 recipes/install.rb:22} +``` + +You can also silence deprecations using a comment on the line that is raising +the warning: + +```ruby +erl_call 'something' do # chef:silence_deprecation +``` + +We advise caution in the use of this feature, as excessive or prolonged silencing +can lead to difficulty upgrading when the next major release of Chef comes out. + # Chef Client Release Notes 14.2: ## `ssh-agent` support for user keys |