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.
Chef 15 release notes will be added here as development progresses.
windows_task now supports the Start When Available option with a new start_when_available property.
The locale resource now allows setting all possible LC_* environmental variables.
The directory resource now property supports passing deny_rights :write on Windows nodes.
The windows_service resource has been improved to prevent accidently reverting a service back to default settings in a subsequent definition.
This example will no longer result in the MyApp service reverting to default RunAsUser:
windows_service 'MyApp' do
run_as_user 'MyAppsUser'
run_as_password 'MyAppsUserPassword'
startup_type :automatic
delayed_start true
action [:configure, :start]
end
...
windows_service 'MyApp' do
startup_type :automatic
action [:configure, :start]
endChef now ships with Ruby 2.6.3. This new version of Ruby improves performance and includes many new features to make more advanced Chef usage easier. See https://www.rubyguides.com/2018/11/ruby-2-6-new-features/ for a list of some of the new functionality.
The knife cookbook site command has been deprecated in favor of the knife supermarket command. Under the hood they are both actually the same codebase, but running knife cookbook site will now product a warning message. In Chef 16 we will remove the knife cookbook site command entirely.
The LC_ALL property in the locale resource has been deprecated as the usage of this environmental variable is not recommended by distribution maintainers.
Knife bootstrap has been updated, and Windows bootstrap has been merged into core Chef's knife bootstrap. This marks the deprecation of the knife-windows plugin's bootstrap behavior.
This change also addresses CVE-2015-8559: The knife bootstrap command in chef leaks the validator.pem private RSA key to /var/log/messages.
Important: knife bootstrap works with all supported versions of Chef client. Older versions may continue to work as far back as 12.20
In order to accomodate a combined bootstrap that supports both SSH and WinRM,
CLI flags have been added, removed, or changed. Using the changed options will
result in deprecation warnings, but knife bootstrap will accept those options
unless otherwise noted.
Using removed options will cause the command to fail.
| Flag | Description |
|---|---|
| --max-wait SECONDS | Maximum time to wait for initial connection to be established. |
| --winrm-basic-auth-only | Perform only Basic Authentication to the target WinRM node. |
| --connection-protocol PROTOCOL | Connection protocol to use. Valid values are 'winrm' and 'ssh'. Default is 'ssh'. |
| --connection-user | user to authenticate as, regardless of protocol |
| --connection-password | Password to authenticate as, regardless of protocol |
| --connection-port | port to connect to, regardless of protocol |
| Flag | New Option | Notes |
|---|---|---|
| --[no-]host-key-verify | --[no-]ssh-verify-host-key | |
| --forward-agent | --ssh-forward-agent | |
| --session-timeout MINUTES | --session-timeout SECONDS | New for ssh, existing for winrm. The unit has changed from MINUTES to SECONDS for consistency with other timeouts. |
| --ssh-password | --connection-password | |
| --ssh-port | --connection-port | knife[:ssh_port] config setting remains available. |
| --ssh-user | --connection-user | knife[:ssh_user] config setting remains available. |
| --ssl-peer-fingerprint | --winrm-ssl-peer-fingerprint | |
| --winrm-authentication-protocol=PROTO | --winrm-auth-method=AUTH-METHOD | Valid values: plaintext, kerberos, ssl, negotiate |
| --winrm-password | --connection-password | |
| --winrm-port | --connection-port | knife[:winrm_port] config setting remains available. |
| --winrm-ssl-verify-mode MODE | --winrm-no-verify-cert | [1] Mode is not accepted. When flag is present, SSL cert will not be verified. Same as original mode of 'verify_none'. |
| --winrm-transport TRANSPORT | --winrm-ssl | [1] Use this flag if the target host is accepts WinRM connections over SSL. |
| --winrm-user | --connection-user | knife[:winrm_user] config setting remains available. |
- These flags do not have an automatic mapping of old flag -> new flag. The new flag must be used.
| Flag | Notes |
|---|---|
| --kerberos-keytab-file | This option existed but was not implemented. |
| --winrm-codepage | This was used under knife-windows because bootstrapping was performed over a cmd shell. It is now invoked from powershell, so this option is no longer used. |
| --winrm-shell | This option was ignored for bootstrap. |
| --prerelease | Chef now releases all development builds to our current channel and does not perform pre-release gem releases. |
| --install-as-service | Installing Chef client as a service is not supported |
Instead of specifying protocol with -o, it's also possible to prefix
the target hostname with the protocol in URL format. For example:
knife bootstrap example.com -o ssh
knife bootstrap ssh://example.com
knife bootstrap example.com -o winrm
knife bootstrap winrm://example.com
Chef's Audit mode was introduced in 2015 as a beta that needed to be enabled via client.rb. Its functionality has been superceded by InSpec and has been removed.
We now append powershell_script user flags to the default flags, rather than the other way around, making user flags override the defaults. This is the correct behavior, but it may cause scripts to execute differently than in previous Chef releases.
The intent of this change is that on upgrading packages the /opt/chef directory is removed of any chef_gem installed gem versions and other
modifications to /opt/chef that might be preserved and cause issues on upgrades. Due to technical details with rpm script execution order
the way this was implemented was that a pre-installation script wipes /opt/chef before every install (done consistently this way on
every package manager).
Users who are properly managing customizations to /opt/chef through Chef recipes won't be affected, because their customizations will still be installed by the new chef-client package.
You'll see a warning that the /opt/chef directory will be removed during the package installation process.
We reversed the default behavior to allow_downgrade true for our package providers. To override this setting to prevent downgrades, use the allow_downgrade false flag. This behavior change will mostly affect users of the rpm and zypper package providers.
package "foo" do
version "1.2.3"
end
That code should now be read as asserting that the package foo must be version 1.2.3 after that resource is run.
package "foo" do
allow_downgrade false
version "1.2.3"
end
That code is now what is necessary to specify that foo must be version 1.2.3 or higher. Note that the yum provider supports syntax like package "foo > 1.2.3" which should be used and is preferred over using allow_downgrade.
Writing a nil to a precedence level in the node object now acts like any other value and can be used to override values back to nil.
For example:
chef (15.0.53)> node.default["foo"] = "bar"
=> "bar"
chef (15.0.53)> node.override["foo"] = nil
=> nil
chef (15.0.53)> node["foo"]
=> nil
In prior versions of chef-client the nil set in the override level would be completely ignored and the value of node["foo"] would have
been "bar".
The Chef config http_disable_auth_on_redirect has been changed from false to true. In Chef 16 this config option will be removed altogether and Chef will always disable auth on redirect.
The knife cookbook test command has been removed. This command would often report non-functional cookbook as functional and has been superseded by functionality in other testing tools such as cookstyle, foodcritic, and chefspec.
The ohai resource contained a non-functional ohai_name property, which has been removed.
The knife status --hide-healthy flag has been removed. Users should run knife status --hide-by-mins MINS instead.
Previously if a user provided multiple cookbook path's to Chef Solo that contained cookbooks with the same name, Chef would combine these into a single cookbook. This merging of two cookbooks often caused unexpected outcomes and has been removed.
The route resource contained multiple unused properties that have been removed. If you previously set networking, networking_ipv6, hostname, domainname, or domain they would be ignored. In Chef 15 setting these properties will throw an error.
Support for the FreeBSD pkg package system in the freebsd_package resource has been removed. FreeBSD 10 replaced the pkg system with pkg-ng system so this only impacts users of EOL FreeBSD releases.
The legacy require_recipe method in recipes has been removed. This method was replaced with include_recipe in the Chef 10 era, and a FoodCritic rule has been warning to update cookbooks for multiple years.
In Chef 14 many of the more obscure shell_out methods used in LWRPs and custom resources were combined into the standard shell_out and shell_out! methods. The legacy methods were infrequently and Chef 14/Foodcritic both contained deprecation warnings for these methods. The following methods will now throw an error: shell_out_compact, shell_out_compact!, shell_out_compact_timeout, shell_out_compact_timeout!, shell_out_with_systems_locale, shell_out_with_systems_locale!,
The knife bootstrap --identity_file flag has been removed. This flag was deprecated in Chef 12 and users should now use the --ssh-identity-file flag instead.
The knife user command no longer supports open source Chef Server version prior to 12.
Chef no longer processes attributes in the metadata.rb file. Attributes could be defined in the metadata.rb file as a form of documentation, which would be shown when running knife cookbook show COOKBOOK_NAME, but these attributes often became out of sync with attributes in the actual attributes files. Chef 15 will no longer show these attributes when running knife cookbook show COOKBOOK_NAME and will instead throw a warning message upon upload. Foodcritic has warned against the use of attributes in the metadata.rb file since April 2017.
Chef 15 includes a bugfix for incorrect node attribute behavior with a rare usage of arrays that may impact users that depended on the incorrect behavior.
Previous setting an attribute like this:
node.default["foo"] = []
node.default["foo"] << { "bar" => "baz }
Would result in a Hash instead of a VividMash inserted into the AttrArray, so that:
node.default["foo"][0]["bar"] # gives the correct result
node.default["foo"][0][:bar] # does not work due to the sub-Hash not
# converting keys
The new behavior uses a Mash so that the attributes will work as expected.
We removed the system_profile plugin because it incorrectly returned data on modern Mac systems. If you relied on this plugin, you'll want to update recipes to use node['hardware'] instead, which correctly returns the same data, but in a more easily consumed format. Removing this plugin speeds up Ohai (and Chef) by ~3 seconds and dramatically reduces the size of the node object on the Chef server.
We removed the Ohai::Util::Win32::GroupHelper helper class from Ohai. This class was intended for use internally in several Windows plugins, but it was never marked private in the codebase. If any of your Ohai plugins rely on this helper class, you will need to update your plugins for Ohai 15.
The chocolatey_package resource now uses the provided options to fetch information on available packages, which allows installation packages from private sources. Thanks @astoltz for reporting this issue.
The openssl_dhparam resource now supports updating the dhparam file's mode on subsequent chef-client runs. Thanks @anewb for the initial work on this fix.
The mount resource now properly adds a blank line between entries in fstab to prevent mount failures on AIX.
The windows_certificate resource now supports importing Base64 encoded CER certificates and nested P7B certificates. Additionally, private keys in PFX certificates are now imported along with the certificate.
The windows_share resource has improved logic to compare the desired share path vs. the current path, which prevents the resource from incorrectly converging during each Chef run. Thanks @Xorima for this fix.
The windows_task resource now properly clears out arguments that are no longer present when updating a task. Thanks @nmcspadden for reporting this.
InSpec has been updated from 3.4.1 to 3.7.1. This new release contains improvements to the plugin system, a new config file system, and improvements to multiple resources. Additionally, profile attributes have also been renamed to inputs to prevent confusion with Chef attributes, which weren't actually related in any way.
- bundler 1.16.1 -> 1.17.3
- libxml2 2.9.7 -> 2.9.9
- ca-certs updated to 2019-01-22 for new roots
OpenSSL has been updated to 1.0.2r in order to resolve CVE-2019-1559
RubyGems has been updated to 2.7.9 in order to resolve the following CVEs:
- CVE-2019-8320: Delete directory using symlink when decompressing tar
- CVE-2019-8321: Escape sequence injection vulnerability in verbose
- CVE-2019-8322: Escape sequence injection vulnerability in gem owner
- CVE-2019-8323: Escape sequence injection vulnerability in API response handling
- CVE-2019-8324: Installing a malicious gem may lead to arbitrary code execution
- CVE-2019-8325: Escape sequence injection vulnerability in errors
The windows_certificate resource is now fully idempotent and properly imports private keys. Thanks @Xorima for reporting these issues.
The apt_repository resource no longer creates .gpg directory in the user's home directory owned by root when installing repository keys. Thanks @omry for reporting this issue.
The git resource no longer displays the URL of the repository if the sensitive property is set.
InSpec has been updated from 3.2.6 to 3.4.1. This new release adds new aws_billing_report / aws_billing_reports resources, resolves multiple bugs, and includes tons of under the hood improvements.
Since Chef 13, knife cookbook site has actually called the knife supermarket command under the hood. In Chef 16 (April 2020), we will remove the knife cookbook site command in favor of knife supermarket.
Chef's Audit mode was introduced in 2015 as a beta that needed to be enabled via client.rb. Its functionality has been superceded by InSpec and we will be removing this beta feature in Chef 15 (April 2019).
Cookbook shadowing was deprecated in 0.10 and will be removed in Chef 15 (April 2019). Cookbook shadowing allowed combining cookbooks within a mono-repo, so long as the cookbooks in question had the same name and were present in both the cookbooks directory and the site-cookbooks directory.
On Windows hosts, the group resource now supports setting the comment field via a new comment property.
Two issues, which caused homebrew_cask to converge on each Chef run, have been resolved. Thanks @jeroenj for this fix. Additionally, the resource will no longer fail if the cask_name property is specified.
The homebrew_tap resource no longer fails if the tap_name property is specified.
The openssl_x509_request resource now properly writes out the CSR file if the path property is specified. Thank you @cpjones for reporting this issue.
powershell_package_source now suppresses warnings, which prevented properly loading the resource state, and resolves idempotency issues when both the name and source_name properties were specified. Thanks @Happycoil for this fix.
The sysctl resource now allows slashes in the key or block name. This allows keys such as net/ipv4/conf/ens256.401/rp_filter to be used with this resource.
Errors joining the domain are now properly suppressed from the console and logs if the sensitive property is set to true. Thanks @Happycoil for this improvement.
The delete action now longer fails if a certificate does not exist on the system. Additionally, certificates with special characters in their passwords will no longer fail. Thank you for reporting this @chadmccune.
The windows_printer resource no longer fails when creating or deleting a printer if the device_id property is specified.
Non-system users can now run tasks without a password being specified.
The ohai init_package plugin is now included as part of the minimal_ohai plugins set, which allows resources such as timezone to continue to function if Chef is running with the minimal number of ohai plugins.
Chef 14.9 now supports Ruby 2.6.
InSpec has been updated from 3.0.64 to 3.2.6 with improved resources for auditing. See the InSpec changelog for additional details on this new version.
The necessary VC++ runtimes for the powershell_exec helper are now bundled with Chef to prevent failures on hosts that lacked the runtimes.
The apt_package resource now supports using the allow_downgrade property to enable downgrading of packages on a node in order to meet a specified version. Thank you @whiteley for requesting this enhancement.
An issue was resolved in the apt_repository resource that caused the resource to fail when importing GPG keys on newer Debian releases. Thank you @EugenMayer for this fix.
Initial support has been added for Red Hat Enterprise Linux 8. Thank you @pixdrift for this fix.
gem_package now supports installing gems into Ruby 2.6 or later installations.
windows_ad_join now uses the UPN format for usernames, which prevents some failures authenticating to the domain.
An issue was resolved in the :acl_add action of the windows_certificate resource, which caused the resource to fail. Thank you @shoekstra for reporting this issue.
The windows_feature resource now allows for the installation of DISM features that have been fully removed from a system. Thank you @zanecodes for requesting this enhancement.
Multiple issues were resolved in windows_share, which caused the resource to either fail or update the share state on every Chef Client run. Thank you @chadmccune for reporting several of these issues and @derekgroh for one of the fixes.
A regression was resolved that prevented ChefSpec from testing the windows_task resource in Chef Client 14.7. Thank you @jjustice6 for reporting this issue.
Detection of Linux guests running on Hyper-V has been improved. In addition, Linux guests on Hyper-V hypervisors will also now detect their hypervisor's hostname. Thank you @safematix for contributing this enhancement.
Example node['virtualization'] data:
{
"systems": {
"hyperv": "guest"
},
"system": "hyperv",
"role": "guest",
"hypervisor_host": "hyper_v.example.com"
}On Linux systems running lxc or lxd containers, the lxc/lxd virtualization system will now properly populate the node['virtualization']['systems'] attribute.
BSD-based systems can now detect guests running on KVM and Amazon's hypervisor without the need for the dmidecode package.
- Ohai now properly detects the openSUSE 15.X platform. Thank you @megamorf for reporting this issue.
- SUSE Linux Enterprise Desktop now identified as platform_family 'suse'
- XCP-NG is now identified as platform 'xcp' and platform_family 'rhel'. Thank you @heyjodom for submitting this enhancement.
- Mangeia Linux is now identified as platform 'mangeia' and platform_family 'mandriva'
- Antergos Linux now identified as platform_family 'arch'
- Manjaro Linux now identified as platform_family 'arch'
OpenSSL has been updated to 1.0.2q in order to resolve:
- Microarchitecture timing vulnerability in ECC scalar multiplication (CVE-2018-5407)
- Timing vulnerability in DSA signature generation (CVE-2018-0734)
Use the windows_firewall_rule resource create or delete Windows Firewall rules.
See the windows_firewall_rule documentation for more information.
Thank you Schuberg Philis for transferring us the windows_firewall cookbook and to @Happycoil for porting it to chef-client with a significant refactoring.
Use the windows_share resource create or delete Windows file shares.
See the windows_share documentation for more information.
Use the windows_certificate resource add, remove, or verify certificates in the system or user certificate stores.
See the windows_certificate documentation for more information.
The dmg_package resource has been refactored to improve idempotency and properly support accepting a DMG's EULA with the accept_eula property.
Kernel_module now only runs the initramfs update once per Chef run to greatly speed up chef-client runs when multiple kernel_module resources are used. Thank you @tomdoherty for this improvement.
The supports property once again allows passing supports data as an array. This matches the behavior present in Chef 12.
macOS support has been added to the timezone resource.
A regression in Chef 14.6’s windows_task resource which resulted in tasks being created with the "Run only when user is logged on" option being set when created with a specific user other than SYSTEM, has been resolved.
Both Chef packages and on disk installations have been greatly reduced in size by trimming unnecessary installation files. This has reduced our package size on macOS/Linux by ~50% and Windows by ~12%. With this change Chef 14 is now smaller than a legacy Chef 10 package.
Chef now includes the timezone resource from @dragonsmith's timezone_lwrp cookbook. This resource supports setting a Linux node's timezone. Thank you @dragonsmith for allowing us to include this out of the box in Chef.
Example:
timezone 'UTC'The windows_task resource has been updated to support localized system users and groups on non-English nodes. Thanks @jugatsu for making this possible.
The user resource now includes a new full_name property for Windows hosts, which allows specifying a user's full name.
Example:
user 'jdoe' do
full_name 'John Doe'
endThe zypper_package resource now includes a new global_options property. This property can be used to specify one or more options for the zypper command line that are global in context.
Example:
package 'sssd' do
global_options '-D /tmp/repos.d/'
endInspec has been updated to version 3.0 with addition resources, exception handling, and a new plugin system. See https://blog.chef.io/2018/10/16/announcing-inspec-3-0/ for details.
Chef is now tested against macOS Mojave, and packages are now available at downloads.chef.io.
- Multiple bugfixes in Chef Vault have been resolved by updating chef-vault to 3.4.2
- Invalid yum package names now gracefully fail
windows_ad_joinnow properly executes. Thank you @cpjones01 for reporting this.rhsm_errata_levelnow properly executes. Thank you @freakinhippie for this fix.registry_keynow properly writes out the correct value whensensitiveis specified. Thank you @josh-barker for this fix.localenow properly executes on RHEL 6 and Amazon Linux 201X.
AIX and Solaris now ship with a filesystem2 plugin that updates the filesystem data to match that of Linux, macOS, and BSD hosts. This new data structure makes accessing filesystem data in recipes easier and especially improves the layout and depth of data on ZFS filesystems. In Chef 15 (April 2019) we will begin writing this same format of data to the existing node['filesystem'] namespace. In Chef 16 (April 2020) we will remove the node['filesystem2'] namespace, completing the transition to the new format. Thank you @jaymzh for continuing the updates to our filesystem plugins with this change.
The system_profile plugin has been improved to skip over unnecessary data, which reduces macOS node sizes on the Chef Server. Additionally the CPU plugin has been updated to limit what sysctl values it polls, which prevents hanging on some system configurations.
SLES 15 is now correctly detected as the platform "suse" instead of "sles". This matches the behavior of SLES 11 and 12 hosts.
The system_profile plugin will be removed from Chef/Ohai 15 in April 2019. This plugin does not correctly return data on modern Mac systems. Additionally the same data is provided by the hardware plugin, which has a format that is simpler to consume. Removing this plugin will reduce Ohai return by ~3 seconds and greatly reduce the size of the node object on the Chef server.
Ruby has been updated to from 2.5.1 to 2.5.3 to resolve multiple CVEs and bugs:
This release resolves a regression that caused the windows_ad_join resource to fail to run. It also makes the following additional fixes:
- The
ohairesource's unusedohai_nameproperty has been deprecated. This will be removed in Chef 15.0. - Error messages in the
windows_featureresources have been improved. - The
windows_serviceresource will no longer log potentially sensitive information if thesensitiveproperty is used.
Thanks to @cpjones01, @kitforbes, and @dgreeninger for their help with this release.
We've added new resources to Chef 14.5. Cookbooks using these resources will continue to take precedent until the Chef 15.0 release
Use the windows_workgroup resource to join or change a Windows host workgroup.
See the windows_workgroup documentation for more information.
Thanks @derekgroh for contributing this new resource.
Use the locale resource to set the system's locale.
See the locale documentation for more information.
Thanks @vincentaubert for contributing this new resource.
windows_ad_join now includes a new_hostname property for setting the hostname for the node upon joining the domain.
Thanks @derekgroh for contributing this new property.
InSpec has been updated from 2.2.70 to 2.2.102. This new version includes the following improvements:
- Support for using ERB templating within the .yml files
- HTTP basic auth support for fetching dependent profiles
- A new global attributes concept
- Better error handling with Automate reporting
- Vendor command now vendors profiles when using path://
Detection for the root_group attribute on Windows has been simplified and improved to properly support non-English systems. With this change, we've also deprecated the Ohai::Util::Win32::GroupHelper helper, which is no longer necessary. Thanks to @jugatsu for putting this together.
We've also added a new encryption_status attribute to volumes on Windows. Thanks to @kmf for suggesting this new feature.
The timeout period for communicating with OpenStack metadata servers can now be configured with the openstack_metadata_timeout config option. Thanks to @sawanoboly for this improvement.
Ohai now properly handles relative paths to config files when running on the command line. This means commands like ohai -c ../client.rb will now properly use your config values.
The rubyzip gem has been updated to 1.2.2 to resolve CVE-2018-1000544
Several new commands have been added under knife config to help manage multiple
profiles in your credentials file.
knife config get-profile displays the active profile.
knife config use-profile PROFILE sets the workstation-level default
profile. You can still override this setting with the --profile command line
option or the $CHEF_PROFILE environment variable.
knife config list-profiles displays all your available profiles along with
summary information on each.
$ knife config get-profile
staging
$ knife config use-profile prod
Set default profile to prod
$ knife config list-profiles
Profile Client Key Server
-----------------------------------------------------------------------------
staging myuser ~/.chef/user.pem https://example.com/organizations/staging
*prod myuser ~/.chef/user.pem https://example.com/organizations/prodThank you @coderanger for this contribution.
The following new previous resources were added to Chef 14.4. Cookbooks with the same resources will continue to take precedent until the Chef 15.0 release
Use the cron_d resource to manage cron definitions in /etc/cron.d. This is similar to the cron resource, but it does not use the monolithic /etc/crontab. file.
Use the cron_access resource to manage the /etc/cron.allow and /etc/cron.deny files. This resource previously shipped in the cron community cookbook and has fully backwards compatibility with the previous cron_manage definition in that cookbook.
Use the openssl_x509_certificate resource to generate signed or self-signed, PEM-formatted x509 certificates. If no existing key is specified, the resource automatically generates a passwordless key with the certificate. If a CA private key and certificate are provided, the certificate will be signed with them. This resource previously shipped in the openssl cookbook as openssl_x509 and is fully backwards compatible with the legacy resource name.
Thank you @juju482 for updating this resource!
Use the openssl_x509_request resource to generate PEM-formatted x509 certificates requests. If no existing key is specified, the resource automatically generates a passwordless key with the certificate.
Thank you @juju482 for contributing this resource.
Use the openssl_x509_crll resource to generate PEM-formatted x509 certificate revocation list (CRL) files.
Thank you @juju482 for contributing this resource.
Use the openssl_ec_private_key resource to generate ec private key files. If a valid ec key file can be opened at the specified location, no new file will be created.
Thank you @juju482 for contributing this resource.
Use the openssl_ec_public_key resource to generate ec public key files given a private key.
Thank you @juju482 for contributing this resource.
The windows_package resource now supports setting the sensitive property to avoid showing errors if a package install fails.
The sysctl resource will now update the on-disk systctl.d file even if the current sysctl value matches the desired value.
The windows_task resource now supports setting the task priority of the scheduled task with a new priority property. Additionally windows_task now supports managing the behavior of task execution when a system is on battery using new disallow_start_if_on_batteries and stop_if_going_on_batteries properties.
The ifconfig resource now supports setting the interface's VLAN via a new vlan property on RHEL platform_family and setting the interface's gateway via a new gateway property on RHEL/Debian platform_family.
Thank you @tomdoherty for this contribution.
The route resource now supports additional RHEL platform_family systems as well as Amazon Linux.
The systemd_unit resource now supports specifying options multiple times in the content hash. Instead of setting the value to a string you can now set it to an array of strings.
Thank you @dbresson for this contribution.
OpenSSL updated to 1.0.2p to resolve:
- Client DoS due to large DH parameter (CVE-2018-0732)
- Cache timing vulnerability in RSA Key Generation (CVE-2018-0737)
This release of Chef introduces the concept of Preview Resources. Preview resources behave the same as a standard resource built into Chef, except Chef will load a resource with the same name from a cookbook instead of the built-in preview resource.
What does this mean for you? It means we can introduce new resources in Chef without breaking existing behavior in your infrastructure. For instance if you have a cookbook with a resource named manage_everything and a future version of Chef introduced a preview resource named manage_everything you will continue to receive the resource from your cookbook. That way outside of a major release your won't experience a potentially breaking behavior change from the newly included resource.
Then when we perform our yearly major release we'll remove the preview designation from all resources, and the built in resources will take precedence over resources with the same names in cookbooks.
Use the chocolatey_config resource to add or remove Chocolatey configuration keys."
set- Sets a Chocolatey config value.unset- Unsets a Chocolatey config value.
config_key- The name of the config. We'll use the resource's name if this isn't provided.value- The value to set.
Use the chocolatey_source resource to add or remove Chocolatey sources.
add- Adds a Chocolatey source.remove- Removes a Chocolatey source.
source_name- The name of the source to add. We'll use the resource's name if this isn't provided.source- The source URL.bypass_proxy- Whether or not to bypass the system's proxy settings to access the source.priority- The priority level of the source.
Use the powershell_package_source resource to register a PowerShell package repository.
register- Registers and updates the PowerShell package source.unregister- Unregisters the PowerShell package source.
source_name- The name of the package source.url- The url to the package source.trusted- Whether or not to trust packages from this source.provider_name- The package management provider for the source. It supports the following providers: 'Programs', 'msi', 'NuGet', 'msu', 'PowerShellGet', 'psl' and 'chocolatey'.publish_location- The url where modules will be published to for this source. Only valid if the provider is 'PowerShellGet'.script_source_location- The url where scripts are located for this source. Only valid if the provider is 'PowerShellGet'.script_publish_location- The location where scripts will be published to for this source. Only valid if the provider is 'PowerShellGet'.
Use the kernel_module resource to manage kernel modules on Linux systems. This resource can load, unload, blacklist, install, and uninstall modules.
install- Load kernel module, and ensure it loads on reboot.uninstall- Unload a kernel module and remove module config, so it doesn't load on reboot.blacklist- Blacklist a kernel module.load- Load a kernel module.unload- Unload kernel module
modname- The name of the kernel module.load_dir- The directory to load modules from.unload_dir- The modprobe.d directory.
Use the ssh_known_hosts_entry resource to add an entry for the specified host in /etc/ssh/ssh_known_hosts or a user's known hosts file if specified.
create- Create an entry in the ssh_known_hosts file.flush- Immediately flush the entries to the config file. Without this the actual writing of the file is delayed in the Chef run so all entries can be accumulated before writing the file out.
host- The host to add to the known hosts file.key- An optional key for the host. If not provided this will be automatically determined.key_type- The type of key to store.port- The server port that the ssh-keyscan command will use to gather the public key.timeout- The timeout in seconds for ssh-keyscan.mode- The file mode for the ssh_known_hosts file.owner- The file owner for the ssh_known_hosts file.group- The file group for the ssh_known_hosts file.hash_entries- Hash the hostname and addresses in the ssh_known_hosts file for privacy.file_location- The location of the ssh known hosts file. Change this to set a known host file for a particular user.
The knife config get command has been added to help with debugging configuration issues with knife and other tools that use the knife.rb file.
With no arguments, it will display all options you've set:
$ knife config get
Loading from configuration file /Users/.../.chef/knife.rb
chef_server_url: https://...
client_key: /Users/.../.chef/user.pem
config_file: /Users/.../.chef/knife.rb
log_level: warn
log_location: STDERR
node_name: ...
validation_key:You can also pass specific keys to only display those knife config get node_name client_key, or use --all to display everything (including options that are using the default value).
The following helper methods have been deprecated in favor of the single shell_out helper:
shell_out_with_systems_localeshell_out_with_timeoutshell_out_compactshell_out_compact_timeoutshell_out_with_systems_locale!shell_out_with_timeout!shell_out_compact!shell_out_compact_timeout!
The functionality of shell_out_with_systems_locale has been implemented using the default_env: false option that removes the PATH and locale mangling that has been the default behavior of shell_out.
The functionality of shell_out_compact has been folded into shell_out. The shell_out API when called with varargs has its arguments flatted, compacted and coerced to strings. This style of calling is encouraged over using strings and building up commands using join(" ") since it avoids shell interpolation and edge conditions in the construction of spaces between arguments. The varargs form is still not supported on Windows.
The functionality of shell_out*timeout has also been folded into shell_out. Users writing Custom Resources should be explicit for Chef-14: shell_out!("whatever", timeout: new_resource.timeout) which will become automatic in Chef-15.
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:
silence_deprecation_warnings %w{deploy_resource chef-23 recipes/install.rb:22}or in your kitchen.yml:
provisioner:
name: chef_solo
solo_rb:
treat_deprecation_warnings_as_errors: true
silence_deprecation_warnings:
- deploy_resource
- chef-23
- recipes/install.rb:22You can also silence deprecations using a comment on the line that is raising the warning:
erl_call 'something' do # chef:silence_deprecationWe 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.
- A new
skip_publisher_checkproperty has been added to thepowershell_packageresource windows_feature_powershellnow supports Windows 2008 R2- The
mountresource now supports themount_pointproperty on Windows windows_feature_dismno longer errors when specifying the source- Resolved idempotency issues in the
windows_taskresource and prevented setting up a task with bad credentials windows_serviceno longer throws Ruby deprecation warnings
As noted above, this release of Chef unifies our shell_out helpers into just shell_out and shell_out!. Previous helpers are now deprecated and will be removed in Chef 15.
See CHEF-26 Deprecation Page for details.
Chef 15 will remove support for the legacy FreeBSD pkg format. We will continue to support the pkgng format introduced in FreeBSD 10.
You can now use ssh-agent to hold your user key when using knife. This allows storing your user key in an encrypted form as well as using ssh -A agent forwarding for running knife commands from remote devices.
You can enable this by adding ssh_agent_signing true to your knife.rb or ssh_agent_signing = true in your credentials file.
To encrypt your existing user key, you can use OpenSSL:
( openssl rsa -in user.pem -pubout && openssl rsa -in user.pem -aes256 ) > user_enc.pem
chmod 600 user_enc.pem
This will prompt you for a passphrase for to use to encrypt the key. You can then load the key into your ssh-agent by running ssh-add user_enc.pem. Make sure you add the ssh_agent_signing to your configuration, and update your client_key to point at the new, encrypted key (and once you've verified things are working, remember to delete your unencrypted key file).
The shell_out helper has been extended with a new option default_env to allow disabling Chef from modifying PATH and LOCALE environmental variables as it shells out. This new option defaults to true (modify the env), preserving the previous behavior of the helper.
The execute resource has also been updated with a new property default_env that allows utilizing this the ENV sanity functionality in shell_out. The new property defaults to false, but it can be set to true in order to ensure a sane PATH and LOCALE when shelling out. If you find that binaries cannot be found when using the execute resource, default_env set to true may resolve those issues.
Chef now bundles the inspec-core and train-core gems, which omit many cloud dependencies not needed within the Chef client. This change reduces the install size of a typical system by ~22% and the number of files within that installation by ~20% compared to Chef 14.1. Enjoy the extra disk space.
Ohai now detects the virtualization hypervisor amazonec2 when running on Amazon's new C5/M5 instances.
This release resolves a number of regressions in 14.1:
gitresource: don't use--prune-tagsas it's really new.rhsm_reporesource: now worksapt_repositoryresource: use therepo_nameproperty to name fileswindows_taskresource: properly handle commands with argumentswindows_taskresource: handle creating tasks as the SYSTEM userremote_directoryresource: restore the default for theoverwriteproperty
- Properly detect FIPS environments
shardplugin: work in FIPS compliant environmentsfilesystemplugin: Handle BSD platforms
Enable Ubuntu-18.04 and Debian-9 tested chef-client packages.
The windows_task resource has been entirely rewritten. This resolves a large number of bugs, including being able to correctly set the start time of tasks, proper creation and deletion of tasks, and improves Chef's validation of tasks. The rewrite will also solve the idempotency problems that users have reported.
The build_essential resource no longer requires a name, similar to the apt_update resource.
The ignore_failure property takes a new argument, :quiet, to suppress the error output when the resource does in fact fail.
- On Windows, the installer now correctly re-extracts files during repair mode
- Fix a number of issues relating to use with Red Hat Satellite
- Git fetch now prunes remotes before running
- Fix locking and unlocking packages with apt and zypper
- Ensure we don't request every remote file when running with lazy loading enabled
- The sysctl resource correctly handles missing keys when used with
ignore_error - --recipe-url apparently never worked on Windows. Now it does.
- CVE-2018-1000201: DLL loading issue which can be hijacked on Windows OS
The whitelist of DMI IDs is now user configurable using the additional_dmi_ids configuration setting, which takes an Array.
The Shard plugin has been returned to a default plugin rather than an optional one. To ensure we work in FIPS environments, the plugin will use SHA256 rather than MD5 in those environments.
A new plugin to enumerate SCSI devices has been added. This plugin is optional.
This release of Chef 14 resolves several regressions in the Chef 14.0 release.
- Resources contained in cookbooks would be used instead of built-in Chef client resources causing older resources to run
- Resources failed due to a missing
property_is_set?andresourcesmethods yum_packagechanged the order ofdisablerepoandenablerepooptions- Depsolving large numbers of cookbooks with chef zero/local took a very long time
Chef 14 includes a large number of resources ported from community cookbooks. These resources have been tested, improved, and had their functionality expanded. With these new resources in the Chef Client itself, the need for external cookbook dependencies and dependency management has been greatly reduced.
Use the build_essential resource to install packages required for compiling C software from source. This resource was ported from the build-essential community cookbook.
Note: This resource no longer configures msys2 on Windows systems.
Use the chef_handler resource to install or uninstall Chef reporting/exception handlers. This resource was ported from the chef_handler community cookbook.
Use the dmg_package resource to install a dmg 'package'. The resource will retrieve the dmg file from a remote URL, mount it using hdiutil, copy the application (.app directory) to the specified destination (/Applications), and detach the image using hdiutil. The dmg file will be stored in the Chef::Config[:file_cache_path]. This resource was ported from the dmg community cookbook.
Use the homebrew_cask resource to install binaries distributed via the Homebrew package manager. This resource was ported from the homebrew community cookbook.
Use the homebrew_tap resource to add additional formula repositories to the Homebrew package manager. This resource was ported from the homebrew community cookbook.
Use the hostname resource to set the system's hostname, configure hostname and hosts config file, and re-run the Ohai hostname plugin so the hostname will be available in subsequent cookbooks. This resource was ported from the chef_hostname community cookbook.
Use the macos_userdefaults resource to manage the macOS user defaults system. The properties of this resource are passed to the defaults command, and the parameters follow the convention of that command. See the defaults(1) man page for details on how the tool works. This resource was ported from the mac_os_x community cookbook.
Use the ohai_hint resource to pass hint data to Ohai to aid in configuration detection. This resource was ported from the ohai community cookbook.
Use the openssl_dhparam resource to generate dhparam.pem files. If a valid dhparam.pem file is found at the specified location, no new file will be created. If a file is found at the specified location but it is not a valid dhparam file, it will be overwritten. This resource was ported from the openssl community cookbook.
Use the openssl_rsa_private_key resource to generate RSA private key files. If a valid RSA key file can be opened at the specified location, no new file will be created. If the RSA key file cannot be opened, either because it does not exist or because the password to the RSA key file does not match the password in the recipe, it will be overwritten. This resource was ported from the openssl community cookbook.
Use the openssl_rsa_public_key resource to generate RSA public key files given a RSA private key. This resource was ported from the openssl community cookbook.
Use the rhsm_errata resource to install packages associated with a given Red Hat Subscription Manager Errata ID. This is helpful if packages to mitigate a single vulnerability must be installed on your hosts. This resource was ported from the redhat_subscription_manager community cookbook.
Use the rhsm_errata_level resource to install all packages of a specified errata level from the Red Hat Subscription Manager. For example, you can ensure that all packages associated with errata marked at a 'Critical' security level are installed. This resource was ported from the redhat_subscription_manager community cookbook.
Use the rhsm_register resource to register a node with the Red Hat Subscription Manager or a local Red Hat Satellite server. This resource was ported from the redhat_subscription_manager community cookbook.
Use the rhsm_repo resource to enable or disable Red Hat Subscription Manager repositories that are made available via attached subscriptions. This resource was ported from the redhat_subscription_manager community cookbook.
Use the rhsm_subscription resource to add or remove Red Hat Subscription Manager subscriptions for your host. This can be used when a host's activation_key does not attach all necessary subscriptions to your host. This resource was ported from the redhat_subscription_manager community cookbook.
Use the sudo resource to add or remove individual sudo entries using sudoers.d files. Sudo version 1.7.2 or newer is required to use the sudo resource, as it relies on the #includedir directive introduced in version 1.7.2. This resource does not enforce installation of the required sudo version. Supported releases of Ubuntu, Debian, SuSE, and RHEL (6+) all support this feature. This resource was ported from the sudo community cookbook.
Use the swap_file resource to create or delete swap files on Linux systems, and optionally to manage the swappiness configuration for a host. This resource was ported from the swap community cookbook.
Use the sysctl resource to set or remove kernel parameters using the sysctl command line tool and configuration files in the system's sysctl.d directory. Configuration files managed by this resource are named 99-chef-KEYNAME.conf. If an existing value was already set for the value it will be backed up to the node and restored if the :remove action is used later. This resource was ported from the sysctl community cookbook.
Note: This resource no longer backs up existing key values to the node when changing values as we have done in the sysctl cookbook previously. The resource has also been renamed from sysctl_param to sysctl with backwards compatibility for the previous name.
Use the windows_ad_join resource to join a Windows Active Directory domain and reboot the node. This resource is based on the win_ad_client resource in the win_ad community cookbook, but is not backwards compatible with that resource.
Use the windows_auto_run resource to set applications to run at logon. This resource was ported from the windows community cookbook.
Use the windows_feature resource to add, remove or delete Windows features and roles. This resource calls the windows_feature_dism or windows_feature_powershell resources depending on the specified installation method and defaults to dism, which is available on both Workstation and Server editions of Windows. This resource was ported from the windows community cookbook.
Note: These resources received significant refactoring in the 4.0 version of the windows cookbook (March 2018). windows_feature resources now fail if the installation of invalid features is requested and support for installation via server servermanagercmd.exe has been removed. If you are using a windows cookbook version less than 4.0 you may need to update cookbooks for Chef 14.
Use the windows_font resource to install or remove font files on Windows. By default, the font is sourced from the cookbook using the resource, but a URI source can be specified as well. This resource was ported from the windows community cookbook.
Use the windows_printer resource to setup Windows printers. Note that this doesn't currently install a printer driver. You must already have the driver installed on the system. This resource was ported from the windows community cookbook.
Use the windows_printer_port resource to create and delete TCP/IPv4 printer ports on Windows. This resource was ported from the windows community cookbook.
Use the windows_shortcut resource to create shortcut files on Windows. This resource was ported from the windows community cookbook.
Use the windows_workgroup resource to join a Windows Workgroup and reboot the node. This resource is based on the windows_ad_join resource.
We've expanded the DSL for custom resources with new functionality to better document your resources and help users with errors and upgrades. Many resources in Chef itself are now using this new functionality, and you'll see more updated to take advantage of this it in the future.
Chef 14 provides new primitives that allow you to deprecate resources or properties with the same functionality used for deprecations in Chef Client resources. This allows you make breaking changes to enterprise or community cookbooks with friendly notifications to downstream cookbook consumers directly in the Chef run.
Deprecate the foo_bar resource in a cookbook:
deprecated "The foo_bar resource has been deprecated and will be removed in the next major release of this cookbook scheduled for 12/25/2018!"
property :thing, String, name_property: true
action :create do
# you'd probably have some actual chef code here
endDeprecate the thing2 property in a resource
property :thing2, String, deprecated: 'The thing2 property has been deprecated and will be removed in the next major release of this cookbook scheduled for 12/25/2018!'Rename a property with a deprecation warning for users of the old property name
deprecated_property_alias 'thing2', 'the_second_thing', 'The thing2 property was renamed the_second_thing in the 2.0 release of this cookbook. Please update your cookbooks to use the new property name.'chef-client no longer is built or tested on OS X 10.10 in accordance with Chef's EOL policy.
Validation messages allow you give the user a friendly error message when any validation on a property fails.
Provide a friendly message when a regex fails:
property :repo_name, String, regex: [/^[^\/]+$/], validation_message: "The repo_name property cannot contain a forward slash '/'",You can now include documentation that describes how a resource is to be used. Expect this data to be consumed by Chef and other tooling in future releases.
A resource which includes description and introduced values in the resource, actions, and properties:
description 'The apparmor_policy resource is used to add or remove policy files from a cookbook file'
introduced '14.1'
property :source_cookbook, String,
description: 'The cookbook to source the policy file from'
property :source_filename, String,
description: 'The name of the source file if it differs from the apparmor.d file being created'
action :add do
description 'Adds an apparmor policy'
# you'd probably have some actual chef code here
endMany existing resources now include new actions and properties that expand their functionality.
apt_package includes a new overwrite_config_files property. Setting this new property to true is equivalent to passing -o Dpkg::Options::="--force-confnew" to apt, and allows you to install packages that prompt the user to overwrite config files. Thanks @ccope for this new property.
The env resource has been renamed to windows_env as it only supports the Windows platform. Existing cookbooks using env will continue to function, but should be updated to use the new name.
ifconfig includes a new family property for setting the network family on Debian systems. Thanks @martinisoft for this new property.
The sensitive property can now be used in registry_key to suppress the output of the key's data from logs and error messages. Thanks @shoekstra for implementing this.
powershell_package includes a new source property to allow specifying the source of the package. Thanks @Happycoil for this new property.
systemd_unit includes the following new actions:
preset- Restore the preset enable/disable configuration for a unitrevert- Revert to a vendor's version of a unit filereenable- Reenable a unit file
Thanks @nathwill for these new actions.
windows_service now includes actions for fully managing services on Windows, in addition to the previous actions for starting/stopping/enabling services.
create- Create a new servicedelete- Delete an existing serviceconfigure- Reconfigure an existing service
Thanks @jasonwbarnett for these new actions
route includes a new comment property.
Thanks Thomas Doherty for adding this new property.
Ohai has been expanded to collect more information than ever. This should make writing cross-platform and cross cloud cookbooks simpler.
The kernel plugin now reports the following information on Windows:
node['kernel']['product_type']- Workstation vs. Server editions of Windowsnode['kernel']['system_type']- What kind of hardware are we installed on (Desktop, Mobile, Workstation, Enterprise Server, etc.)node['kernel']['server_core']- Are we on Windows Server Core edition?
Ohai now detects the Scaleway cloud and provides additional configuration information for systems running on Azure.
In addition to detecting if a system is a Docker host, we now provide a large amount of Docker configuration information available at node['docker']. This includes the release of Docker, installed plugins, network config, and the number of running containers.
Ohai also now properly detects LXD containers and macOS guests running on VirtualBox / VMware. This data is available in node['virtualization']['systems'].
Ohai now includes the ability to mark plugins as optional, which skips those plugins by default. This allows us to ship additional plugins, which some users may find useful, but not all users want that data collected in the node object on a Chef server. The change introduces two new configuration options; run_all_plugins which runs everything including optional plugins, and optional_plugins which allows you to run plugins marked as optional.
By default we will now be marking the lspci, sessions shard and passwd plugins as optional. Passwd has been particularly problematic for nodes attached to LDAP or AD where it attempts to write the entire directory's contents to the node. If you previously disabled this plugin via Ohai config, you no longer need to. Hurray!
Ruby has been updated to version 2.5 bringing a 10% performance improvement and improved functionality.
InSpec has been updated to the 2.0 release. InSpec 2.0 brings compliance automation to the cloud, with new resource types specifically built for AWS and Azure clouds. Along with these changes are major speed improvements and quality of life updates. Please visit https://www.inspec.io/ for more information.
Many users of Policyfiles rely on "hoisting" to provide group specific attributes. This approach was formalized in the poise-hoist extension, and is now included in Chef 14.
To hoist an attribute, the user provides a default attribute structure in their Policyfile similar to:
default['staging']['myapp']['title'] = "My Staging App" default['production']['myapp']['title'] = "My App"and then accesses the node attribute in their cookbook as:
node['myapp']['title']The correct attribute is then provided based on the policy_group of the node, so with a policy_group of staging the attribute would contain "My Staging App".
yum_package received a ground up rewrite that greatly improves both the performance and functionality while also resolving a dozen existing issues. It introduces a new caching method that runs for the duration of the chef-client process. This caching method speeds up each package install and takes 1/2 the memory of the previous yum-dump.py process.
yum_package should now take any argument that yum install does and operate the same way, including version constraints "foo < 1.2.3" and globs "foo-1.2*" along with arches "foo.i386" and in combinations
Package with a version constraint:
yum_package "foo < 1.2.3"Installing a package via what it provides:
yum_package "perl(Git)"Since our supported Windows platforms can all run .NET Framework 4.0 and PowerShell 4.0 we have taken time to add a new helper that will allow for faster and safer interactions with the system PowerShell. You will be able to use the powershell_exec mixin in most places where you would have previously used powershell_out. For comparison, a basic benchmark test to return the $PSVersionTable 100 times completed 7.3X faster compared to the powershell_out method. The majority of the time difference is because of less time spent in invocation. So we believe it has big future potential where multiple calls to PowerShell are required inside (for example) a custom resource. Many core Chef resources will be updated to use this new mixin in future releases.
Chef now includes a new log level of :trace in addition to the existing :info, :warn, and :debug levels. With the introduction of trace level logging we've moved a large amount of logging that is more useful for Chef developers from debug to trace. This makes it easier for Chef Cookbook developers to use debug level to get useful information.
OpenSSL has been updated to 1.0.2o to resolve CVE-2018-0739
Ruby has been updated to 2.5.1 to resolve the following vulnerabilities:
- cve-2017-17742
- cve-2018-6914
- cve-2018-8777
- cve-2018-8778
- cve-2018-8779
- cve-2018-8780
- Multiple vulnerabilities in rubygems
This release completes the deprecation process for many of the deprecations that were warnings throughout the Chef 12 and Chef 13 releases.
The erl_call resource was deprecated in Chef 13.7 and has been removed.
The deploy resource was deprecated in Chef 13.6 and been removed. If you still require this resource, it is available in the new deploy_resource cookbook at https://supermarket.chef.io/cookbooks/deploy_resource
Support for Windows 2003 has been removed from both Chef and Ohai, improving the performance of Chef on Windows hosts.
knife bootstrapoptions--distroand--template_fileflags were deprecated in Chef 12 and have now been removed.knife helpfunctionality that read legacy Chef manpages has been removed as the manpages had not been updated and were often quite wrong. Running knife help will now simply show the help menu.knife index rebuildhas been removed as reindexing Chef Server was only necessary on releases prior to Chef Server 11.- The
knife ssh --identity-fileflag was deprecated and has been removed. Users should use the--ssh_identity_fileflag instead. knife ssh csshxwas deprecated in Chef 10 and has been removed. Users should useknife ssh csshinstead.
The Chef Solor -r flag has been removed as it was deprecated and replaced with the --recipe-url flag in Chef 12.
node.set and node.set_unless were deprecated in Chef 12 and have been removed in Chef 14. To replicate this same functionality users should use node.normal and node.normal_unless, although we highly recommend reading our attribute documentation to make sure normal is in fact the your desired attribute level.
The chocolatey_package resource in the chocolatey cookbook supported an :uninstall action. When this resource was moved into the Chef Client we allowed this action with a deprecation warning. This action is now removed.
Previously if a user wrote a custom resource with a property named foo they could reference it throughout the resource using the name foo. This caused multiple edge cases where the property name could conflict with resources or methods in Chef. Properties now must be referenced as new_resource.foo. This was already the case when writing LWRPs.
The original name for the ignore_failure property in resource was epic_fail. The legacy name has been removed.
Several legacy mixins mostly used in older HWRPs have been removed. Usage of these mixins has resulted in deprecation warnings for several years and they are rarely used in cookbooks available on the Supermarket.
- Chef::Mixin::LanguageIncludeAttribute
- Chef::Mixin::RecipeDefinitionDSLCore
- Chef::Mixin::LanguageIncludeRecipe
- Chef::Mixin::Language
- Chef::DSL::Recipe::FullDSL
In Chef 13 the cloud_v2 plugin replaced data at node['cloud'] and filesystem2 replaced data at node['filesystem']. For compatibility with cookbooks that were previously using the "v2" data we continued to write data to both locations (ie: both node['filesystem'] and node['filesystem2']). We now no longer write data to the "v2" locations which greatly reduces the amount of data we need to store on the Chef server.
The ipscopes plugin has been removed as it duplicated data already present in the network plugins and required the user to install an additional gem into the Chef installation.
The libvirt Ohai plugin now writes data to node['libvirt'] instead of writing to various locations in node['virtualization']. This plugin required installing an additional gem into the Chef installation and thus was infrequently used.
In 2014 we introduced Ohai v7 with a greatly improved plugin format. With Chef 14 we no longer support loading of the legacy "v6" plugin format.
As mentioned above we now support an optional flag for Ohai plugins and have marked the sessions, lspci, and passwd plugins as optional, which disables them by default. If you need one of these plugins you can include them using optional_plugins.
optional_plugins in the client.rb file:
optional_plugins [ "lspci", "passwd" ]- The mount provider now properly adds blank lines between fstab entries on AIX
- Ohai now reports itself as Ohai well communicating with GCE metadata endpoints
- Property deprecations in custom resources no longer result in an error. Thanks for reporting this martinisoft
- mixlib-archive has been updated to prevent corruption of archives on Windows systems
- libxml2 2.9.7 -> 2.9.9
- ca-certs updated to 2019-01-22 for new roots
- nokogiri 1.8.5 -> 1.10.1
OpenSSL has been updated to 1.0.2r in order to resolve CVE-2019-1559 and CVE-2018-5407
RubyGems has been updated to 2.7.9 in order to resolve the following CVEs:
- CVE-2019-8320: Delete directory using symlink when decompressing tar
- CVE-2019-8321: Escape sequence injection vulnerability in verbose
- CVE-2019-8322: Escape sequence injection vulnerability in gem owner
- CVE-2019-8323: Escape sequence injection vulnerability in API response handling
- CVE-2019-8324: Installing a malicious gem may lead to arbitrary code execution
- CVE-2019-8325: Escape sequence injection vulnerability in errors
We trimmed unnecessary installation files, greatly reducing the sizes of both Chef packages and on disk installations. MacOS/Linux/FreeBSD packages are ~50% smaller and Windows are ~12% smaller. Chef 13 is now smaller than a legacy Chef 10 package.
Chef is now tested against macOS Mojave and packages are now available at downloads.chef.io.
- Ohai now properly detects SLES 15
- The Chef package will no longer remove symlinks to chef-client and ohai when upgrading on SLES 15
Updating chef-vault to 3.4.2 resolved multiple bugs.
Improved Windows installation speed by skipping unnecessary steps when Windows Installer 5.0 or later is available.
- sysctl commands have been modified to gather only the bare minimum required data, which prevents sysctl hanging in some scenarios
- Extra data has been removed from the system_profile plugin, reducing the amount of data stored on the chef-server for each node
The system_profile plugin will be removed from Chef/Ohai 15 in April, 2019. This plugin incorrectly returns data on modern Mac systems. Further, the hardware plugin returns the same data in a more readily consumable format. Removing this plugin reduces the speed of the Ohai return by ~3 seconds and also greatly reduces the node object size on the Chef server
The ohai resource's unused ohai_name property has been deprecated. This will be removed in Chef 15.0.
Ruby has been updated to from 2.4.4 to 2.4.5 to resolve multiple CVEs as well as bugs:
windows_serviceno longer logs potentially sensitive information when a service is setupwindows_packagenow respects thesensitiveproperty to avoid logging sensitive data in the event of a package installation failure
remote_directorynow properly loads files in the root of a cookbook'sfilesdirectoryosx_profilenow uses the full path the profiles CLI tool to avoid running other binaries of the same name in a users pathpackageresources that don't support theallow_downgradeproperty will no longer failknife bootstrap windowserror messages have been improved
- OpenSSL has been updated to 1.0.2p to resolve CVE-2018-0732 and CVE-2018-0737
- Updated Rubyzip to 1.2.2 to resolve CVE-2018-1000544
- Resolves a duplicate logging getting created when redirecting stdout
- Using --recipe-url with a local file on Windows no longer fails
- Service resource no longer throws Ruby deprecation warnings on Windows
- Correctly identify the platform_version on the final release of Amazon Linux 2.0
- Detect nodes with the DMI data of "OpenStack Compute" as being OpenStack nodes
- CVE-2018-1000201: DLL loading issue which can be hijacked on Windows OS
Ruby has been updated to 2.4.4
- CVE-2017-17742: HTTP response splitting in WEBrick
- CVE-2018-6914: Unintentional file and directory creation with directory traversal in tempfile and tmpdir
- CVE-2018-8777: DoS by large request in WEBrick
- CVE-2018-8778: Buffer under-read in String#unpack
- CVE-2018-8779: Unintentional socket creation by poisoned NUL byte in UNIXServer and UNIXSocket
- CVE-2018-8780: Unintentional directory traversal by poisoned NUL byte in Dir
- Multiple vulnerabilities in RubyGems
Nokogiri has been updated to 1.8.2
- [MRI] Behavior in libxml2 has been reverted which caused CVE-2018-8048 (loofah gem), CVE-2018-3740 (sanitize gem), and CVE-2018-3741 (rails-html-sanitizer gem).
OpenSSL has been updated to 1.0.2o
- CVE-2018-0739: Constructed ASN.1 types with a recursive definition could exceed the stack.
As Debian 7 is now end of life we will no longer produce Debian 7 chef-client packages.
Incompatibilities with Ubuntu 18.04 in the ifconfig resource have been resolved.
Ohai now detects the virtualization hypervisor amazonec2 when running on Amazon's new C5/M5 instances.
The whitelist of DMI IDs is now user configurable using the additional_dmi_ids configuration setting, which takes an Array.
The Filesystem2 functionality has been backported to BSD systems to provide a consistent filesystem format.
Enable Ubuntu-18.04 and Debian-9 tested chef-client packages.
- On Windows, the installer now correctly re-extracts files during repair mode
- The mount resource will now not create duplicate entries when the device type differs
- Ensure we don't request every remote file when running with lazy loading enabled
- Don't crash when getting the access rights for Windows system accounts
We've expanded the DSL for custom resources with new functionality to better document your resources and help users with errors and upgrades. Many resources in Chef itself are now using this new functionality, and you'll see more updated to take advantage of this it in the future.
Chef 13 provides new primitives that allow you to deprecate resources or properties with the same functionality used for deprecations in Chef Client resources. This allows you make breaking changes to enterprise or community cookbooks with friendly notifications to downstream cookbook consumers directly in the Chef run.
Deprecate the foo_bar resource in a cookbook:
deprecated "The foo_bar resource has been deprecated and will be removed in the next major release of this cookbook scheduled for 12/25/2018!"
property :thing, String, name_property: true
action :create do
# you'd probably have some actual chef code here
endDeprecate the thing2 property in a resource
property :thing2, String, deprecated: 'The thing2 property has been deprecated and will be removed in the next major release of this cookbook scheduled for 12/25/2018!'Rename a property with a deprecation warning for users of the old property name
deprecated_property_alias 'thing2', 'the_second_thing', 'The thing2 property was renamed the_second_thing in the 2.0 release of this cookbook. Please update your cookbooks to use the new property name.'Validation messages allow you give the user a friendly error message when any validation on a property fails.
Provide a friendly message when a regex fails:
property :repo_name, String, regex: [/^[^\/]+$/], validation_message: "The repo_name property cannot contain a forward slash '/'",You can now include documentation that describes how a resource is to be used. Expect this data to be consumed by Chef and other tooling in future releases.
A resource which includes description and introduced values in the resource, actions, and properties:
description 'The apparmor_policy resource is used to add or remove policy files from a cookbook file'
introduced '14.1'
property :source_cookbook, String,
description: 'The cookbook to source the policy file from'
property :source_filename, String,
description: 'The name of the source file if it differs from the apparmor.d file being created'
action :add do
description 'Adds an apparmor policy'
# you'd probably have some actual chef code here
end- Fix uptime parsing on AIX
- Fix Softlayer cloud detection
- Use the current Azure metadata endpoint
- Correctly detect macOS guests on VMware and VirtualBox
Per https://discourse.chef.io/t/regression-in-chef-client-13-7-16/12518/1 , there was a regression in how arrays and hashes were handled in 13.7. In 13.8, we've reverted to the same code as 13.6.
13.8 has better validation for the idle_time property, when using the on_idle frequency.
- Updated libxml2 to 2.9.7; fixes: CVE-2017-15412
We've spent a considerable amount of time testing and fixing the windows_task resource to ensure that it is properly idempotent and correct in more situations.
Previously, chef on the workstation used knife.rb or config.rb to handle credentials. This didn't do a great job when interacting with multiple Chef servers, leading to the need for tools like knife_block. We've added support for a credentials file that can contain configuration for many Chef servers (or organizations), and we've made it easy to indicate which account you mean to use.
We introduced erl_call to help us to manage CouchDB servers back in the olden times of Chef. Since then, we've noticed that no-one uses it, and so erl_call will be removed in Chef 14. Foodcritic rule FC105 has been introduced to detect usage of erl_call.
The original name for the ignore_failure property in resources was epic_fail. Our documentation hasn't referred to epic_fail for years and out of the 3500 cookbooks on the Supermarket only one uses epic_fail. In Chef 14 we will remove the epic_fail property entirely. Foodcritic rule FC107 has been introduced to detect usage of epic_fail.
In Chef 14 several legacy legacy mixins will be removed. Usage of these mixins has resulted in deprecation warnings for several years. They were traditionally used in some HWRPs, but are rarely found in code available on the Supermarket. Foodcritic rules FC097, FC098, FC099, FC100, and FC102 have been introduced to detect these mixins.
- Chef::Mixin::LanguageIncludeAttribute
- Chef::Mixin::RecipeDefinitionDSLCore
- Chef::Mixin::LanguageIncludeRecipe
- Chef::Mixin::Language
- Chef::DSL::Recipe::FullDSL
The chocolatey cookbook's chocolatey_package resource originally contained an :uninstall action. When chocolatey_package was moved into core Chef we made :uninstall an alias for :remove. In Chef 14 :uninstall will no longer be a valid action. Foodcritic rule FC103 has been introduced to detect the usage of the :uninstall action.
- Resolved a bug where knife commands that prompted on Windows would never display the prompt
- Fixed hiding of sensitive resources when converge_if_changed was used
- Fixed scenarios where services would fail to start on Solaris
- OpenSSL has been upgraded to 1.0.2n to resolve CVE-2017-3738, CVE-2017-3737, CVE-2017-3736, and CVE-2017-3735.
- Ruby has been upgraded to 2.4.3 to resolve CVE-2017-17405
The Network plugin on Linux hosts now gathers additional information on tunnels
The new LsPci plugin provides a node[:pci] hash with information about the PCI bus based on lspci. Only runs on Linux.
The EC2 plugin has been updated to properly detect the new AWS hypervisor used in the C5 instance types
The mdadm plugin has been updated to properly handle arrays with more than 10 disks and to properly handle journal and spare drives in the disk counts
- Resolved a regression in 13.6.0 that prevented upgrading packages on Debian/Ubuntu when the package name contained a tilde.
- OpenSSL has been upgraded to 1.0.2m to resolve CVE-2017-3735 and CVE-2017-3736
- RubyGems has been upgraded to 2.6.14 to resolve CVE-2017-0903
The deploy resource (and its alter ego deploy_revision) have been deprecated, to be removed in Chef 14. This is being done because this resource is considered overcomplicated and error-prone in the modern Chef ecosystem. A compatibility cookbook will be available to help users migrate during the Chef 14 release cycle. See the deprecation documentation for more information.
zypper_package now supports downgrading installed packages with the allow_downgrade property.
It's no longer possible to create data bags named node, role, client, or environment. Existing data bags will continue to work as before.
If both dnf and yum were installed, in some circumstances the yum provider might choose to run dnf, which is not what we intended it to do. It now properly runs yum, all the time.
Users can now specify a list of plugins which are critical. Critical plugins will cause Ohai to fail if they do not run successfully (and thus cause a Chef run using Ohai to fail). The syntax for this is:
ohai.critical_plugins << :Filesystem
The Filesystem plugin now has a allow_partial_data configuration option. If set, the filesystem will return whatever data it can even if some commands it ran failed.
Windows nodes running on Rackspace will now properly detect themselves as running on Rackspace without a hint file.
The Packages plugin now supports gathering packages data on Amazon Linux
In Ohai 13 we replaced the filesystem and cloud plugins with the filesystem2 and cloud_v2 plugins. To maintain compatibility with users of the previous V2 plugins we write data to both locations. We had originally planned to continue writing data to both locations until Chef 15. Instead due to the large amount of duplicate node data this introduces we are updating OHAI-11 and OHAI-12 deprecations to remove node['cloud_v2'] and node['filesystem2'] with the release of Chef 14 in April 2018.
This means that passwords passed to mount won't show up in logs.
Previously, the resource would accept any date that was formatted correctly in the local locale, unlike the Windows cookbook and Windows itself. We now only support the MM/DD/YYYY format, in common with the Windows cookbook.
Previously we would ignore routes that ended ::, and now we properly detect them.
Debug logs will show the length of time each plugin takes to run, making debugging of long ohai runs easier.
Chef Client 13.4 includes Ruby 2.4.2 to fix the following CVEs:
- CVE-2017-0898
- CVE-2017-10784
- CVE-2017-14033
- CVE-2017-14064
Chef Client 13.4 includes RubyGems 2.6.13 to fix the following CVEs:
- CVE-2017-0899
- CVE-2017-0900
- CVE-2017-0901
- CVE-2017-0902
It is now possible to set ETHTOOL_OPTS, BONDING_OPTS, MASTER and SLAVE properties on interfaces on Red Hat compatible systems. See https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/s1-networkscripts-interfaces.html for further information
-
ethtool_opts
Ruby types: String
Platforms: Fedora, RHEL, Amazon Linux A string containing arguments to ethtool. The string will be wrapped in double quotes, so ensure that any needed quotes in the property are surrounded by single quotes -
bonding_opts
Ruby types: String
Platforms: Fedora, RHEL, Amazon Linux A string containing configuration parameters for the bonding device. -
master
Ruby types: String
Platforms: Fedora, RHEL, Amazon Linux The channel bonding interface that this interface is linked to. -
slave
Ruby types: String
Platforms: Fedora, RHEL, Amazon Linux Whether the interface is controlled by the channel bonding interface defined bymaster, above.
Chef Client 13.4 now includes the chef-vault gem, making it easier for users of chef-vault to use their encrypted items.
The remote_file resource now supports the use of credentials on Windows when accessing a remote UNC path on Windows such as \\myserver\myshare\mydirectory\myfile.txt. This allows access to the file at that path location even if the Chef client process identity does not have permission to access the file. The new properties remote_user, remote_domain, and remote_password may be used to specify credentials with access to the remote file so that it may be read.
Note: This feature is mainly used for accessing files between two nodes in different domains and having different user accounts. In case the two nodes are in same domain, remote_file resource does not need remote_user and remote_password specified because the user has the same access on both systems through the domain.
The following properties are new for the remote_file resource:
-
remote_user
Ruby types: String
Windows only: The user name of a user with access to the remote file specified by thesourceproperty. Default value:nil. The user name may optionally be specifed with a domain, i.e.domain\useroruser@my.dns.domain.comvia Universal Principal Name (UPN) format. It can also be specified without a domain simply asuserif the domain is instead specified using theremote_domainattribute. Note that this property is ignored ifsourceis not a UNC path. If this property is specified, theremote_passwordproperty must be specified. -
remote_password
Ruby types String
Windows only: The password of the user specified by theremote_userproperty. Default value:nil. This property is mandatory ifremote_useris specified and may only be specified ifremote_useris specified. Thesensitiveproperty for this resource will automatically be set totrueifremote_passwordis specified. -
remote_domain
Ruby types String
Windows only: The domain of the user user specified by theremote_userproperty. Default value:nil. If not specified, the user and password properties specified by theremote_userandremote_passwordproperties will be used to authenticate that user against the domain in which the system hosting the UNC path specified viasourceis joined, or if that system is not joined to a domain it will authenticate the user as a local account on that system. An alternative way to specify the domain is to leave this property unspecified and specify the domain as part of theremote_userproperty.
Accessing file from a (different) domain account
remote_file "E://domain_test.txt" do
source "\\\\myserver\\myshare\\mydirectory\\myfile.txt"
remote_domain "domain"
remote_user "username"
remote_password "password"
endOR
remote_file "E://domain_test.txt" do
source "\\\\myserver\\myshare\\mydirectory\\myfile.txt"
remote_user "domain\\username"
remote_password "password"
endAccessing file using a local account on the remote machine
remote_file "E://domain_test.txt" do
source "\\\\myserver\\myshare\\mydirectory\\myfile.txt"
remote_domain "."
remote_user "username"
remote_password "password"
endOR
remote_file "E://domain_test.txt" do
source "\\\\myserver\\myshare\\mydirectory\\myfile.txt"
remote_user ".\\username"
remote_password "password"
endwindows_path resource has been moved to core chef from windows cookbook. Use the windows_path resource to manage the path environment variable on Microsoft Windows.
:add- Add an item to the system path:remove- Remove an item from the system path
path- Name attribute. The name of the value to add to the system path
Add Sysinternals to the system path
windows_path 'C:\Sysinternals' do
action :add
endRemove 7-Zip from the system path
windows_path 'C:\7-Zip' do
action :remove
endDetection of nodes running in EC2 has been greatly improved and should now detect nodes 100% of the time including nodes that have been migrated to EC2 or were built with custom AMIs.
Ohai now polls the new Azure metadata endpoint, giving us additional configuration details on nodes running in Azure
Sample data now available under azure:
{
"metadata": {
"compute": {
"location": "westus",
"name": "timtest",
"offer": "UbuntuServer",
"osType": "Linux",
"platformFaultDomain": "0",
"platformUpdateDomain": "0",
"publisher": "Canonical",
"sku": "17.04",
"version": "17.04.201706191",
"vmId": "8d523242-71cf-4dff-94c3-1bf660878743",
"vmSize": "Standard_DS1_v2"
},
"network": {
"interfaces": {
"000D3A33AF03": {
"mac": "000D3A33AF03",
"public_ipv6": [
],
"public_ipv4": [
"52.160.95.99",
"23.99.10.211"
],
"local_ipv6": [
],
"local_ipv4": [
"10.0.1.5",
"10.0.1.4",
"10.0.1.7"
]
}
},
"public_ipv4": [
"52.160.95.99",
"23.99.10.211"
],
"local_ipv4": [
"10.0.1.5",
"10.0.1.4",
"10.0.1.7"
],
"public_ipv6": [
],
"local_ipv6": [
]
}
}
}The Package plugin has been updated to include package information on Arch Linux systems.
Chef can now create symlinks without privilege escalation, which allows for the creation of symlinks on Windows 10 Creator Update.
The nokogiri gem is once again bundled with the omnibus install of Chef
It is now possible to pass additional options to the zypper in the zypper_package resource. This can be used to pass any zypper CLI option
zypper_package 'foo' do
options '--user-provided'
endThe windows_task resource now properly allows updating the configuration of a scheduled task when using the :create action. Additionally the previous :change action from the windows cookbook has been aliased to :create to provide backwards compatibility.
The apt_preference resource has been ported from the apt cookbook. This resource allows for the creation of APT preference files controlling which packages take priority during installation.
Further information regarding apt-pinning is available via https://wiki.debian.org/AptPreferences and https://manpages.debian.org/stretch/apt/apt_preferences.5.en.html
:add: creates a preferences file under /etc/apt/preferences.d:remove: Removes the file, therefore unpin the package
package_name: name attribute. The name of the packageglob: Pin by glob() expression or regexp surrounded by /.pin: The package version/repository to pinpin_priority: The pinning priority aka "the highest package version wins"
Pin libmysqlclient16 to version 5.1.49-3:
apt_preference 'libmysqlclient16' do
pin 'version 5.1.49-3'
pin_priority '700'
endUnpin libmysqlclient16:
apt_preference 'libmysqlclient16' do
action :remove
endPin all packages from dotdeb.org:
apt_preference 'dotdeb' do
glob '*'
pin 'origin packages.dotdeb.org'
pin_priority '700'
endThe zypper_repository resource allows for the creation of Zypper package repositories on SUSE Enterprise Linux and openSUSE systems. This resource maintains full compatibility with the resource in the existing zypper cookbooks
:add- adds a repo:delete- removes a repo
repo_name- repository name if different from the resource name (name property)type- the repository type. default: 'NONE'description- the description of the repo that will be shown inzypper reposbaseurl- the base url of the repopath- the relative path from thebaseurlmirrorlist- the url to the mirrorlist to usegpgcheck- should we gpg check the repo (true/false). default: truegpgkey- location of repo key to importpriority- priority of the repo. default: 99autorefresh- should the repository be automatically refreshed (true/false). default: truekeeppackages- should packages be saved (true/false). default: falserefresh_cache- should package cache be refreshed (true/false). default: trueenabled- should this repository be enabled (true/false). default: truemode- the file mode of the repository file. default: "0644"
Add the Apache repository for openSUSE Leap 42.2
zypper_repository 'apache' do
baseurl 'http://download.opensuse.org/repositories/Apache'
path '/openSUSE_Leap_42.2'
type 'rpm-md'
priority '100'
endOhai now properly detects the F5 Big-IP platform and platform_version.
- platform: bigip
- platform_family: rhel
When sending events back to the Chef Server, we now correctly expand the run_list for nodes that use Policyfiles. This allows Automate to correctly report the node.
When Chef performs a reconfigure, it re-reads the configuration files. It also re-opens its log files, which facilitates log file rotation.
Chef normally will reconfigure when sent a HUP signal. As of this release if you send a HUP signal while it is converging, the reconfigure happens at the end of the run. This is avoids potential Ruby issues when the configuration file contains additional Ruby code that is executed. While the daemon is sleeping between runs, sending a SIGHUP will still cause an immediate reconfigure.
Additionally, Chef now always performs a reconfigure after every run when daemonized.
https://docs.chef.io/deprecations_namespace_collisions.html
In Chef 14, custom resources will no longer assume property methods are being called on new_resource, and instead require the resource author to be explicit.
Ohai 13.2 has been a fantastic release in terms of community involvement with new plugins, platform support, and critical bug fixes coming from community members. A huge thank you to msgarbossa, albertomurillo, jaymzh, and davide125 for their work.
A new plugin has been added to expose system and user paths from systemd-path (see https://www.freedesktop.org/software/systemd/man/systemd-path.html for details).
The Network, Filesystem, and Mdadm plugins have been improved to greatly reduce failures to collect data. The Network plugin now better finds the binaries it requires for shelling out, filesystem plugin utilizes data from multiple sources, and mdadm handles arrays in bad states.
The Zpool plugin has been updated to support BSD and Linux in addition to Solaris.
The packages plugin now correctly parses RPM package name / version information on AIX systems.
Ohai now properly detects the Clear and ClearOS Linux distributions.
- platform: clearlinux
- platform_family: clearlinux
- platform: clearos
- platform_family: rhel
https://docs.chef.io/deprecations_ohai_ipscopes.html
In Chef/Ohai 14 (April 2018) we will remove the IpScopes plugin. The data returned by this plugin is nearly identical to information already returned by individual network plugins and this plugin required the installation of an additional gem into the Chef installation. We believe that few users were installing the gem and users would be better served by the data returned from the network plugins.
For security reasons we are switching Local Mode to use socketless connections by default. This prevents potential attacks where an unprivileged user or process connects to the internal Zero server for the converge and changes data.
If you use Chef Provisioning with Local Mode, you may need to pass --listen to chef-client.
https://docs.chef.io/deprecations_ohai_v6_plugins.html
In Chef/Ohai 14 (April 2018) we will remove support for loading Ohai v6 plugins, which we deprecated in Ohai 7/Chef 11.12.
The behavior of gem_package and chef_gem is now to always apply the Chef::Config[:rubygems_url] sources, which may be a String uri or an Array of Strings. If additional sources are put on the resource with the source property those are added to the configured :rubygems_url sources.
This should enable easier setup of rubygems mirrors particularly in "airgapped" environments through the use of the global config variable. It also means that an admin may force all rubygems.org traffic to an internal mirror, while still being able to consume external cookbooks which have resources which add other mirrors unchanged (in a non-airgapped environment).
In the case where a resource must force the use of only the specified source(s), then the include_default_source property has been added -- setting it to false will remove the Chef::Config[:rubygems_url] setting from the list of sources for that resource.
The behavior of the clear_sources property is now to only add --clear-sources and has no magic side effects on the source options.
We've upgraded to the latest stable release of the Ruby programming language. See the Ruby 2.4.0 Release Notes for an overview of what's new in the language.
The core apt_update resource can now be declared without any name argument, no need for apt_update "this string doesn't matter but why do i have to type it?".
This can be used by any other resource by just overriding the name property and supplying a default:
property :name, String, default: ""Notifications to resources with empty strings as their name is also supported via either the bare resource name (apt_update -- matches what the user types in the DSL) or with empty brackets (apt_update[] -- matches the resource notification pattern).
A bare name to knife search node will search for the name in tags, roles, fqdn, addresses, policy_name or policy_group fields and will match when given partial strings (available since Chef 11). The knife ssh search term has been similarly extended so that the search API matches in both cases. The node search fuzzifier has also been extracted out to a fuzz option to Chef::Search::Query for re-use elsewhere.
Rather than attributes/default.rb, cookbooks can now use attributes.rb in the root of the cookbook. Similarly for a single default recipe, cookbooks can use recipe.rb in the root of the cookbook.
The new gateway_identity_file option allows the operator to specify the key to access ssh gateways with.
The windows_task resource has been ported from the windows cookbook, and many bugs have been fixed.
It is now possible to load Solaris services recursively, by ensuring the new options property of the service resource contains -r.
This is the inverse of the pre-existing whitelisting functionality.
When writing not_if or only_if statements, by default we now run those statements using powershell, rather than forcing the user to set guard_interpreter each time.
Zypper now defaults to performing gpg checks of packages.
The inspec and train gems are shipped by default in the chef omnibus package, making it easier for users in airgapped environments to use InSpec.
Chef now properly supports managing sys-v services on hosts running systemd. Previously Chef would incorrectly attempt to fallback to Upstart even if upstart was not installed.
When Chef compiles resources, it will no longer attempt to merge the properties of previously compiled resources with the same name and type in to the new resource. See the deprecation page for further information.
Chef 12 made this work by picking the first option it found, but it was always an error and has now been disallowed.
It was never implemented in the provider, so it was always a no-op to use it, the remediation is to simply delete it.
This was always a usage mistake. The command property was used internally by the script resource and was not intended to be exposed to users. Users should use the code property instead (or use the command property on an execute resource to execute a single command).
It is possible that this was being used as a no-op resource, but the log resource is a better choice for that until we get a null resource added. Omitting the code property or mixing up the code property with the command property are also common usage mistakes that we need to catch and error on.
The compile_time true flag may still be used to force compile time.
In order to for community cookbooks to behave consistently across all users this optional flag has been removed.
The remediation is to set the manage_home and non_unique properties directly.
Using relative paths in the creates property of an execute resource with specifying a cwd is now a hard error
Without a declared cwd the relative path was (most likely?) relative to wherever chef-client happened to be invoked which is not deterministic or easy to intuit behavior.
This change is most likely to only affect internals of tooling like chefspec if it affects anything at all.
PolicyFile users on Chef-13 should be using Chef Server 12.3 or higher.
The remediation is removing the self-dependency depends line in the metadata.
Retained only for the service resource (where it makes some sense) and for the mount resource.
Exceptions not decending from StandardError (e.g. LoadError, SecurityError, SystemExit) will no longer trigger a retry if they are raised during the executiong of a resources with a non-zero retries setting.
Previously, the syntax node.foo.bar could be used to mean node["foo"]["bar"], but this API had sharp edges where methods collided with the core ruby Object class (e.g. node.class) and where it collided with our own ability to extend the Chef::Node API. This method access has been deprecated for some time, and has been removed in Chef-13.
Dropped the create_if_missing parameter that was immediately supplanted by the edit_resource API (most likely nobody ever used this) and converted the created_at parameter from an optional positional parameter to a named parameter. These changes are unlikely to affect any cookbook code.
The node.to_hash/node.to_h and node.dup APIs have been fixed so that they correctly deep-dup the node data structure including every string value. This results in a mutable copy of the immutable merged node structure. This is correct behavior, but is now more expensive and may break some poor code (which would have been buggy and difficult to follow code with odd side effects before).
For example:
node.default["foo"] = "fizz"
n = node.to_hash # or node.dup
n["foo"] << "buzz"
before this would have mutated the original string in-place so that node["foo"] and node.default["foo"] would have changed to "fizzbuzz" while now they remain "fizz" and only the mutable n["foo"] copy is changed to "fizzbuzz".
Since Chef 11 merged node attributes have been intended to be immutable but the merged strings have not been frozen. In Chef 13, in the process of merging the node attributes strings and other simple objects are dup'd and frozen. In order to get a mutable copy, you can now correctly use the node.dup or node.to_hash methods, or you should mutate the object correctly through its precedence level like node.default["some_string"] << "appending_this".
It has been fully replaced with Chef::ServerAPI in chef-client code.
Defining a property that overrides methods defined on the base ruby Object or on Chef::Resource itself can cause large amounts of confusion. A simple example is property :hash which overrides the Object#hash method which will confuse ruby when the Custom Resource is placed into the Chef::ResourceCollection which uses a Hash internally which expects to call Object#hash to get a unique id for the object. Attempting to create property :action would also override the Chef::Resource#action method which is unlikely to end well for the user. Overriding inherited properties is still supported.
Running chef-shell -s or chef-shell --solo will give you an experience consistent with chef-solo. chef-shell --solo-legacy-mode will give you an experience consistent with chef-solo --legacy-mode.
The deprecated code has been removed. All providers and resources should now be using Chef >= 12.0 provides syntax.
This option has been unimplemented on the server side for years, so any use of it has been pointless.
This was deprecated and replaced a long time ago with mixlib-shellout and the shell_out mixin.
The core of chef hasn't used this to implement the Recipe DSL since 12.5.1 and its unlikely that any external code depended upon it.
Support for actions with spaces and hyphens in the action name has been dropped. Resources and property names with spaces and hyphens most likely never worked in Chef-12. UTF-8 characters have always been supported and still are.
The Python easy_install package installer has been deprecated for many years, so we have removed support for it. No specific replacement for pip is being included with Chef at this time, but a pip-based python_package resource is available in the poise-python cookbooks.
All the APIs in chef/mixlib/command have been removed. They were deprecated by mixlib-shellout and the shell_out mixin API.
The ruby Iconv library was replaced by the Encoding library in ruby 1.9.x and since the deprecation of ruby 1.8.7 there has been no need for the Iconv library but we have carried it forwards as a dependency since removing it might break some chef code out there which used this library. It has now been removed from the ruby build. This also removes LGPLv3 code from the omnibus build and reduces build headaches from porting iconv to every platform we ship chef-client on.
This will also affect nokogiri, but that gem natively supports UTF-8, UTF-16LE/BE, ISO-8851-1(Latin-1), ASCII and "HTML" encodings. Users who really need to write something like Shift-JIS inside of XML will need to either maintain their own nokogiri installs or will need to convert to using UTF-8.
The recommends, suggests, conflicts, replaces and grouping metadata fields are no longer supported, and have been removed, since they were never used. Chef will ignore them in existing metadata.rb files, but we recommend that you remove them. This was proposed in RFC 85.
We now treat every file under a cookbook directory as belonging to a cookbook, unless that file is ignored with a chefignore file. This is a change from the previous behaviour where only files in certain directories, such as recipes or templates, were treated as special. This change allows chef to support new classes of files, such as Ohai plugins or Inspec tests, without having to make changes to the cookbook format to support them.
Up until now, creating a mycook/resources/thing.rb would create a Chef::Resources::MycookThing name to access the resource class object. This const is no longer created for resources and providers. You can access resource classes through the resolver API like:
Chef::Resource.resource_for_node(:mycook_thing, node)Accessing a provider class is a bit more complex, as you need a resource against which to run a resolution like so:
Chef::ProviderResolver.new(node, find_resource!("mycook_thing[name]"), :nothing).resolveA resource declaring something like:
property :x, default: {}will now see the default value set to be immutable. This prevents cases of modifying the default in one resource affecting others. If you want a per-resource mutable default value, define it inside a lazy{} helper like:
property :x, default: lazy { {} }Resources which later modify their name during creation will have their name changed on the ResourceCollection and notifications
some_resource "name_one" do
name "name_two"
endThe fix for sending notifications to multipackage resources involved changing the API which inserts resources into the resource collection slightly so that it no longer directly takes the string which is typed into the DSL but reads the (possibly coerced) name off of the resource after it is built. The end result is that the above resource will be named some_resource[name_two] instead of some_resource[name_one]. Note that setting the name (not the name_property, but actually renaming the resource) is very uncommon. The fix is to simply name the resource correctly in the first place (some_resource "name_two" do ...)
The use_inline_resources provider mode is always enabled when using the action :name do ... end syntax. You can remove the use_inline_resources line.
Please use knife cookbook site install instead.
Please use chef generate cookbook from the ChefDK instead.
Chef has always recommended %{path}, and %{file} has now been removed.
The partial_search method has been fully replaced by the filter_result argument to search, and has now been removed.
The default now is the formatter. There is no more automatic switching to the logger when logging or when output is sent to a pipe. The logger needs to be specifically requested with --force-logger or it will not show up.
The --force-formatter option does still exist, although it will probably be deprecated in the future.
If your logfiles switch to the formatter, you need to include --force-logger for your daemonized runs.
Redirecting output to a file with chef-client > /tmp/chef.out now captures the same output as invoking it directly on the command line with no redirection.
The chef client itself no long modifies its ENV['PATH'] variable directly. When using the shell_out API now, in addition to setting up LANG/LANGUAGE/LC_ALL variables that API will also inject certain system paths and the ruby bindir and gemdirs into the PATH (or Path on Windows). The shell_out_with_systems_locale API still does not mangle any environment variables. During the Chef-13 lifecycle changes will be made to prep Chef-14 to switch so that shell_out by default behaves like shell_out_with_systems_locale. A new flag will get introduced to call shell_out(..., internal: [true|false]) to either get the forced locale and path settings ("internal") or not. When that is introduced in Chef 13.x the default will be true (backwards-compat with 13.0) and that default will change in 14.0 to 'false'.
The PATH changes have also been tweaked so that the ruby bindir and gemdir PATHS are prepended instead of appended to the PATH. Some system directories are still appended.
Some examples of changes:
which rubyin 12.x will return any system ruby and fall back to the embedded ruby if using omnibuswhich rubyin 13.x will return any system ruby and will not find the embedded ruby if using omnibusshell_out_with_systems_locale("which ruby")behaves the same aswhich rubyaboveshell_out("which ruby")in 12.x will return any system ruby and fall back to the embedded ruby if using omnibusshell_out("which ruby")in 13.x will always return the omnibus ruby first (but will find the system ruby if not using omnibus)
The PATH in shell_out can also be overridden:
shell_out("which ruby", env: { "PATH" => nil })- behaves like shell_out_with_systems_locale()shell_out("which ruby", env: { "PATH" => [...include PATH string here...] })- set it arbitrarily however you need
Since most providers which launch custom user commands use shell_out_with_systems_locale (service, execute, script, etc) the behavior will be that those commands that used to be having embedded omnibus paths injected into them no longer will. Generally this will fix more problems than it solves, but may causes issues for some use cases.
The implementation switched to shell_out_with_systems_locale to match execute resource, etc.
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.
Ruby has been updated to 2.3.6 to resolve CVE-2017-17405
Libxml2 has been updated to 2.9.7 to resolve CVE-2017-15412
Ohai now provides EC2 metadata configuration information on the new C5/M5 instance types running on Amazon's new hypervisor.
The new LsPci plugin provides a node[:pci] hash with information about the PCI bus based on lspci. Only runs on Linux.
The virtualization plugin has been updated to properly detect when running on Docker CE
This release of Chef Client contains Ruby 2.3.5, fixing 4 CVEs:
- CVE-2017-0898
- CVE-2017-10784
- CVE-2017-14033
- CVE-2017-14064
It also contains a new version of Rubygems, fixing 4 CVEs:
- CVE-2017-0899
- CVE-2017-0900
- CVE-2017-0901
- CVE-2017-0902
This release also contains a new version of zlib, fixing 4 CVEs:
On Debian systems, packages that support systemd will often ship both an old style init script and a systemd unit file. When this happened, Chef would incorrectly choose Upstart rather than Systemd as the service provider. We now pick Systemd.
Chef 13 removed the supports property from core resources. However,
many cookbooks also have a property named support, and Chef 12 was
incorrectly giving a deprecation notice in that case, preventing users
from properly testing their cookbooks for upgrades.
On systems where Chef 13 had been run, Chef 12 would crash as the on disk cookbook format has changed. Chef 12 now correctly ignores the unexpected files.
When Chef crashes, the output now includes details about the platform and version of Chef that was running, so that a bug report has more detail from the off.
- Systemd unit files are now verified before being installed.
- Added support for windows alternate user identity in execute resources.
- Added ed25519 key support for for ssh connections.
The execute resource and similar resources such as script, batch, and powershell_script now support the specification of credentials on Windows so that the resulting process is created with the security identity that corresponds to those credentials.
Note: When Chef is running as a service, this feature requires that the user that Chef runs as has 'SeAssignPrimaryTokenPrivilege' (aka 'SE_ASSIGNPRIMARYTOKEN_NAME') user right. By default only LocalSystem and NetworkService have this right when running as a service. This is necessary even if the user is an Administrator.
This right bacn be added and checked in a recipe using this example:
# Add 'SeAssignPrimaryTokenPrivilege' for the user
Chef::ReservedNames::Win32::Security.add_account_right('<user>', 'SeAssignPrimaryTokenPrivilege')
# Check if the user has 'SeAssignPrimaryTokenPrivilege' rights
Chef::ReservedNames::Win32::Security.get_account_right('<user>').include?('SeAssignPrimaryTokenPrivilege')The following properties are new or updated for the execute, script, batch, and powershell_script resources and any resources derived from them:
-
user
Ruby types: String
The user name of the user identity with which to launch the new process. Default value:nil. The user name may optionally be specified with a domain, i.e.domain\useroruser@my.dns.domain.comvia Universal Principal Name (UPN) format. It can also be specified without a domain simply asuserif the domain is instead specified using thedomainattribute. On Windows only, if this property is specified, thepasswordproperty must be specified. -
password
Ruby types String
Windows only: The password of the user specified by theuserproperty. Default value:nil. This property is mandatory ifuseris specified on Windows and may only be specified ifuseris specified. Thesensitiveproperty for this resource will automatically be set totrueifpasswordis specified. -
domain
Ruby types String
Windows only: The domain of the user user specified by theuserproperty. Default value:nil. If not specified, the user name and password specified by theuserandpasswordproperties will be used to resolve that user against the domain in which the system running Chef client is joined, or if that system is not joined to a domain it will resolve the user as a local account on that system. An alternative way to specify the domain is to leave this property unspecified and specify the domain as part of theuserproperty.
The following examples explain how alternate user identity properties can be used in the execute resources:
powershell_script 'create powershell-test file' do
code <<-EOH
$stream = [System.IO.StreamWriter] "#{Chef::Config[:file_cache_path]}/powershell-test.txt"
$stream.WriteLine("In #{Chef::Config[:file_cache_path]}...word.")
$stream.close()
EOH
user 'username'
password 'password'
end
execute 'mkdir test_dir' do
cwd Chef::Config[:file_cache_path]
domain "domain-name"
user "user"
password "password"
end
script 'create test_dir' do
interpreter "bash"
code "mkdir test_dir"
cwd Chef::Config[:file_cache_path]
user "domain-name\\username"
password "password"
end
batch 'create test_dir' do
code "mkdir test_dir"
cwd Chef::Config[:file_cache_path]
user "username@domain-name"
password "password"
end- Ensure that the Windows Administrator group can access the chef-solo nodes directory
- When loading a cookbook in Chef Solo, use
metadata.jsonin preference tometadata.rb
- As of version 12.19, chef client will no longer be build or tested on the Cisco NX-OS and IOS XR platforms.
Cumulus Linux will now be detected as platform cumulus instead of debian and the platform_version will be properly set to the Cumulus Linux release.
Windows / Linux / BSD guests running on the Veertu hypervisors will now be detected
Windows guests running on Xen and Hyper-V hypervisors will now be detected
A new plugin parses the output of the sysconf command to provide information on the underlying system.
The EC2 plugin now fetches the AWS Account ID in addition to previous instance metadata
GCC detection has been improved to collect additional information, and to not prompt for the installation of Xcode on macOS systems
- Deprecation ID: OHAI-1
- Remediation Docs: https://docs.chef.io/deprecations_ohai_legacy_config.html
- Expected Removal: Ohai 13 (April 2017)
- Deprecation ID: OHAI-2
- Remediation Docs: https://docs.chef.io/deprecations_ohai_sigar_plugins.html
- Expected Removal: Ohai 13 (April 2017)
- Deprecation ID: OHAI-3
- Remediation Docs: https://docs.chef.io/deprecations_ohai_run_command_helpers.html
- Expected Removal: Ohai 13 (April 2017)
- Deprecation ID: OHAI-4
- Remediation Docs: https://docs.chef.io/deprecations_ohai_libvirt_plugin.html
- Expected Removal: Ohai 13 (April 2017)
- Deprecation ID: OHAI-5
- Remediation Docs: https://docs.chef.io/deprecations_ohai_windows_cpu.html
- Expected Removal: Ohai 13 (April 2017)
- Deprecation ID: OHAI-6
- Remediation Docs: https://docs.chef.io/deprecations_ohai_digitalocean.html
- Expected Removal: Ohai 13 (April 2017)