diff options
author | tyler-ball <tyleraball@gmail.com> | 2016-02-10 23:19:55 -0700 |
---|---|---|
committer | tyler-ball <tyleraball@gmail.com> | 2016-02-11 08:07:07 -0700 |
commit | 23e77045931cf1fbfdf6bddc5ca3d534cb3233a8 (patch) | |
tree | 6fb483ed850b764072bea0eef934b948054a13ee /RELEASE_NOTES.md | |
parent | d22efaa11063e1a4dc54b71db2cf917b6b7fa140 (diff) | |
download | chef-23e77045931cf1fbfdf6bddc5ca3d534cb3233a8.tar.gz |
12.7.2 release prep, removing some unstable acceptance tests so we can get a successful release pipeline run
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r-- | RELEASE_NOTES.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 16ac30c6e3..4c7d3d1c0d 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -41,6 +41,10 @@ EMEA customers in particular, and those customers who need reliable UTF-8 suppor extremely bad UTF-8 handling bug in them which corrupted all UTF-8 data in the node. In 12.7.0 that bug was fixed, along with another fix to make resource and audit reporting more reliable when fed non-UTF-8 (e.g. Latin-1/ISO-8859-1) characters. +## Deleting folders with Chef Solo and the recipe_url config + +Providing the `:recipe_url` config to Chef Solo would attempt to `rm -rf` the existing local Chef repo. This was a dangerous folder delete that trolled a few people so we removed the behavior. If you would like to keep this behavior you can provide the `:delete_entire_chef_repo` configuration and it will continue attempting to destroy the existing local Chef repo. This configuration only applies if you are using `:recipe_url` + ## Chef::REST We recently completed moving our internal API calls from `Chef::REST` to |