Chef Client 12.7 Released
// Chef Blog
We just released Chef Client 12.7.2 and it is available via the downloads page. Here are some highlights of this release:
Updates to versioning specificationWe recently updated the versioning specification in our release process to facilitate faster releases with lower risk between each release. Soon an automated process will begin updating the "patch" version (the third number in the version).
For consumers of Chef this means that the first future release of chef may not end in a
.0. The first
12.7 release available is the
12.7.2 release. In the future you may use version
12.8.5 without earlier versions of
12.8 having been released first. Those earlier versions may be available in the "current" channel that you can access through the install.sh and install.ps1 scripts.
Zypper Package Multipackage SupportOn SuSE systems, the
zypper_packageprovider), now accepts arrays and will install them with a single zypper command together:
package [ 'git', 'nmap' ]
chocolatey_packageprovider in core Chef. It is named
chocolateyin order to not conflict with the existing resource in the chocolatey cookbook and to comply with existing naming standards for package resources in core Chef.
The API for
chocolatey_package conforms to the
package API in core Chef, rather than being a straight port of the cookbook version, and there are some API differences (e.g. it favors the
:remove action over the
:uninstall action since that is the API standard for core Chef package providers). The
chocolatey_package provider also supports multipackage installations and will execute them in a single statement where possible:
chocolatey_package [ 'googlechrome', 'flashplayerplugin', '7zip', 'git' ]
choco.exebinary must be installed prior to using the resource, so the chocolatey cookbook recipe should still be used to install it.
Chef::ServerAPI. As part of that move,
Chef::RESTis no longer globally required, so if your code uses
Chef::REST, you must ensure that you require it correctly.
Chef::REST; if your code is run inside
chefthen consider using
Chef::ServerAPI, otherwise please investigate ChefAPI.
Chef Solo -r (–recipe-url) changesPassing the
-roption to chef-client results in setting the
Passing the same argument to chef-solo:
chef-client -r 'role[foo]'
Instead invokes the
chef-solo -r 'role[foo]'
--recipe-urlcode, which had the side effect of running an immediate unprompted
rm -rf *in the current working directory of the user. Due to this problem and other issues around this
rm -rf *behavior it has been removed from the
--recipe-urlcode in chef-solo. The use of
-rin chef-solo to mean
--recipe-urlhas also been deprecated.
rm -rf * behavior has been moved to a
--delete-entire-chef-repo option. Users of chef-solo who want the old pre-12.7 behavior of
-r XXX should therefore use
--recipe-url XXX --delete-entire-chef-repo.
Upgrade to Net-SSH 3.0.2We updated from the 2.9 branch of Net-SSH to consume an upstream bug fix. The biggest change here is that they dropped support for Ruby 1.9 (which Chef already dropped support for). Because this is such a low level dependency we found that many other projects had to be updated in lock-step (like Test Kitchen and Berkshelf) for the ChefDK packaging to succeed without dependency conflicts.
Upgrade to Ohai 8.10.0This is an upgrade from version 8.8.1 which contains a handful of minor improvements and bug fixes. See the CHANGELOG for a full list of changes.
Windows Client File Permission Security Fixchef#4500 fixes a permission issue on Windows client SKUs only that could permit local privilege escalation. Thanks to Jared Stroud of SPARSA for the report.
Shared via my feedly reader
Sent from my iPad