Note: ChefDK will be enter end-of-life product phase Dec 31st 2020. The 4.13 release of ChefDK is the last planned release and all users should upgrade to Chef Workstation, which offers signicant improvements to all included tools.
ChefDK packages are no longer produced for Debian 8 and RHEL/CentOS 6 as these platforms are now both EOL.
Test Kitchen was updated from 2.7.2 to 2.8.0. This release improves how we execute commands on Windows hosts in order to avoid failures executing commands that are too long for the windows command line. Thanks for this fix @ramereth!
The Kitchen Google driver for Test Kitchen was updated from 2.0.3 to 2.1.0. This release adds a new network_ip config for an IPv4 internal IP address to assign to the instance. The driver automatically assigns an unused internal IP to an unconfigured network_ip. Thanks @eReGeBe for this new feature!
The kitchen-vagrant plugin is updated from version 1.7.1 to 1.7.2 with a bug fix to no longer stop with an error when updating a Vagrant box that has not yet been downloaded.
Kitchen Dokken has been updated to 2.11.2 to resolve failures from creating containers during the Test Kitchen converge. Thanks for reporting this issue @emeshuris!
Chef InSpec has been updated to 4.24.8 including the following improvements:
- An unset
HOMEenvironment variable will not cause execution failures - You can use wildcards in
platform-nameandreleasein InSpec profiles. Thanks for this improvement @yarick! - The
WMIresource now returns an array to support returning multiple WMI objects - The
packageresource on Windows properly escapes package names. Thanks for this improvement @ramereth! - The
grub_confresource succeeds even if without amenuentryin the grub config - Loaded plugins won't try to re-load themselves
- Waiver expiration is now always populated
We've updated the release of chef-vault to 4.1. Chef Vault 4.1 properly handles escape strings in secrets and greatly improves performance for users with large numbers of secrets. Thanks for the performance work @Annih!
The knife-ec2 plugin has been updated to 2.1.0, which allows for the creation of instances with ST1 or SC1 EBS volume types
The openSSL library has been updated to 1.0.2x to resolve CVE-2020-1971.
InSpec has been updated from 4.22.22 to 4.23.11. This release includes a --no-diff CLI option to suppress diff output for textual tests, a --sort_results_by CLI option to sort control output, and implements a sensitive mechanism to hide sensitive output.
The kitchen-azurerm plugin has been updated from 1.3.0 to 1.4.0. This release includes multiple bug fixes, as well as a new use_fqdn_hostname config option that forces using the instance's FQDN for all communication.
The kitchen-dokken plugin has been updated from 2.10.0 to 2.11.0. This release works with newer Docker API releases and resolves Ruby 2.7 compatibility warnings.
The kitchen-ec2 plugin has been updated from 3.7.1 to 3.8.0. This release now avoids beta releases of Red Hat when searching for AMIs to converge, allows multiple IP addresses to be specified when creating a security group, and fixes block_duration_minutes when creating spot instances.
The kitchen-inspec plugin has been updated from 2.0.0 to 2.2.1. This release includes the ability to disable input caching in InSpec, as well as a fix for using the junit reporter under Test Kitchen.
Test Kitchen has been updated from 2.7.0 to 2.7.2. This release marks the legacy chef_solo provisioner as unsafe for concurrency and includes various performance optimizations.
The knife-opc plugin has been updated from 0.4.6 to 0.4.7. This release includes a new --all-info flag for use with the knife opc user list command. This flag provides additional details on each listed user:
antima_gupta:
display_name: Antima Gupta
email: [email protected]
first_name: Antima
last_name: Gupta
pivotal:
display_name: Chef Server Superuser
email: [email protected]
first_name: Chef
last_name: Server
The knife-ec2 plugin has been updated from 2.0.4 to 2.0.6. This release fixes an error that would occur when using the --server-connect-attribute private_ip_address flag.
The chef-vault gem has been updated from 4.0.11 to 4.0.12. This release fixes vault show -F json and knife vault list -F json displaying invalid JSON.
We've reworked how the knife command loads dependencies to greatly improve performance. For some users this may result in a 2/3 reduction in the time knife commands take to load the first time. We also fixed the knife ssh command hanging when connecting to Windows nodes over SSH.
Chef Infra Client has been updated from 15.13.8 to 15.14.0 with a large number of improvements to built-in Chef Infra resources.
Chef InSpec has been updated from 4.22.1 to 4.22.22. This new release includes the following improvements:
- Fix mysql_session stdout, stderr and exit_status parameters. Thanks @ramereth!
- Add new windows_firewall and windows_firewall_rule resources. Thanks @tecracer-theinen!
Chef Vault has been updated from 4.0.1 to 4.0.11. This release resolves errors when running some knife vault commands and better inputs command inputs.
Test Kitchen has been updated from 2.5.4 to 2.7.0, which adds the ability to mark plugins as unable to run with a concurrency (-c) level greater than 1. This will help prevent strange failures that occur with some plugins which cannot run concurrently in the future.
Kitchen AzureRM has been updated from 1.0.0 to 1.3.0. This release includes:
- Support for deletion or preservation of resource group tags with a new
destroy_explicit_resource_group_tagsconfig that defaults to true. - Default password generation increased to 25 characters to avoid failures on newer Windows releases.
- Improve performance by loading depedencies only when we need them.
The kitchen-vagrant plugin has been updated from 1.6.1 to 1.7.0. This release adds new box_auto_update and box_auto_prune options to pull newer Vagrant base boxes. Thank you @Stromweld!
- We now produce packages for Apple's upcoming macOS 11 Big Sur release.
OpenSSL has been updated to 1.0.2w which includes a fix for CVE-2020-1968.
The included cacerts bundle in Chef Infra Client has been updated to the 7-22-2020 release. This new release removes 4 legacy root certificates and adds 4 additional root certificates.
Chef Infra Client has been updated from 15.12.2 to 15.13.8. This new release includes a new deprecation warning when resources specify resource_name without also specifying provides which results in failures on Chef Infra Client 16.2 and later. This release also improves the warning message that occurs when a cookbook includes a resource that is now bundled directly in Chef Infra Client.
Chef InSpec has been updated from 4.21.3 to 4.22.1:
- The = character is now allowed for command line inputs
- apt-cdrom repositories are now skipped when parsing out the list of apt repositories
- Faulty profiles are now reported instead of causing a crash
- Improved macOS support in the
serviceresource
cookbook-omnifetch has been updated from 0.9.1 to 0.10.0. This release adds support for Chef Server API v2 so we can support segmentless cookbooks with the Chef CLI and Policyfiles.
knife-cloud has been updated from 4.0.0 to 4.0.2. This release properly supports jump hosts when the bootstrap flags are used.
knife-google has been updated from 5.0.0 to 5.0.5. This release adds support for all the aliases for new OSes and distributions, and removes several EOL distributions.
kitchen-opc has been updated from 0.4.4 to 0.4.6. This release fixes several errors that could occur when running knife opc user edit USERNAME.
kitchen-dokken has been updated from 2.9.0 to 2.10.0. This release adds a memory_limit config to set memory usage limits on the container. It also fixes the multiple_converge and enforce_idempotency configurations so they work correctly.
kitchen-ec2 has been updated from 3.7.0 to 3.7.1. This release fixes the default search for CentOS machines to use the official CentOS images and adds support for subnet filtering with spot instances.
- Support for legacy DSA host keys has been restored in
knife sshandknife bootstrapcommands.
The Chef Infra Client has been updated from 15.11 to 15.12. This release includes a large number of backported improvements to resources from our Chef Infra Client 16 releases. See the release notes for a complete list of what's new.
InSpec was updated from 4.19 to 4.21. This new release includes the following improvements:
- Certain substrings within a .toml file no longer cause unexpected crashes.
- Accurate InSpec CLI input parsing for numeric values and structured data, which were previously treated as strings. Numeric values are cast to an integer or float and YAML or JSON structures are converted to a hash or an array.
- Suppress deprecation warnings on
inspec execwith the--silence-deprecationsoption.
The knife bootstrap command has been updated with several fixes and improvements
- knife bootstrap will now warn when bootstrapping a system using a validation key. Users should instead use validatorless bootstrapping with
knife bootstrapwhich generates node and client keys using the client key of the user bootstrapping the node. This method is far more secure as an organization-wide validation key does not need to be distributed or rotated. Users can switch to validatorless bootstrapping by removing anyvalidation_keyentries in their config.rb (knife.rb) file. - Resolved an error bootstrapping Linux nodes from Windows hosts
- Improved information messages during the bootstrap process
- Bootstrapping will now be done using a single SSH connection improving bootstrap times on high latency network connection.
Knife Tidy has been updated from 2.0.12 to 2.1.0 which adds support for a --keep-versions command line flag. Specifying this keeps a minimum number of versions of each cookbook and defaults to 0.
The net-ssh gem which powers knife ssh and knife bootstrap commands has been updated from 5.2.0 to 6.1.0 which includes the following updates:
- Support empty lines and comments in known_hosts.
- Add sha2-{256,512}[email protected] MAC algorithms.
- curve25519sha256 support.
The Test Kitchen driver kitchen-ec2 has been updated from 3.6.0 to 3.7.0. This new release improves how instances and volumes are tagged to ensure that these are tagged at create time. This resolves failures on AWS accounts that enforced tagging rules on all objects.
The Test Kitchen verifier kitchen-inspec has been updated from 1.3.2 to 2.0.0. This new release adds a config option load_plugins which can be used to load all InSpec plugins during the Test Kitchen verify phase.
Sample kitchen.yml config:
verifier:
name: inspec
load_plugins: trueChefDK packages are now created for Ubuntu 20.04 and Debian 10! Additionally, we have increased package validation for our Windows 10 packages to ensure compatibility. See the ChefDK Downloads Page for a complete list of platforms.
Each binary in the macOS ChefDK installation is now signed to improve the integrity of the installation and ensure compatibility with macOS Catalina security requirements.
Chef Infra Client has updated from 15.7 to 15.11, which includes improvements to resources, additional cookbook helpers, and critical bug fixes for bootstrapping nodes using knife bootstrap and SSHing to nodes with ed25519 keys from Windows hosts. For a complete list of changes, see the Chef Infra Client 15.11 release notes.
Chef InSpec has updated from 4.18.51 to 4.19.0. This update includes a large number of fixes to resources and these significant new features:
- You can now develop your own Chef InSpec Reporter plugin and determine how Chef InSpec will report result data. Learn more about Chef InSpec plugins and implementation in our documentation
- The
inspec archivecommand packs your profile into a tar.gz file that includes the profile in JSON form as theinspec.jsonfile. Use this JSON file to programmatically examine the profile without needing to load it into Chef InSpec - Chef InSpec accepts a variety of date formats in the
waivers.yamlconfiguration file, rather than only theYYYY-MM-DDformat - Use the new
inspeccommand options to control the size of reports:--reporter-message-truncationsets a length limit for themessagefield in test failure report data--reporter-backtrace-inclusiondetermines if Ruby backtraces should be included in test failure report data
- Implemented VMware and Hyper-V detection on Linux systems
- Implemented VMware, Hyper-V, Virtualbox, KVM, and Xen detection on Windows systems
- Added helpers
virtual_system?andphysical_system?
Cookstyle has upgraded from 5.20 to 5.23, which includes 8 new cops, and significant improvements to the detection and autocorrect capabilities in existing cops.
- ChefModernize/NodeInitPackage
- ChefDeprecations/WindowsFeatureServermanagercmd
- ChefModernize/WindowsRegistryUAC
- ChefModernize/UseRequireRelative
- ChefStyle/UnnecessaryOSCheck
- ChefModernize/SimplifyAptPpaSetup
- ChefRedundantCode/StringPropertyWithNilDefault
- ChefRedundantCode/PropertySplatRegex
Note: Chef Workstation ships with Cookstyle 6.x, which includes a significantly improved RuboCop engine, and 24 additional cops for resolving deprecations and preparing cookbooks for Chef Infra Client 16. Cookstyle 5.x does not include Chef Infra Client 16 preparation cops.
Test Kitchen itself has updated from 2.3.4 to 2.5.0 with several significant improvements to the provisioners and verifiers:
- The CHEF_LICENSE env var is now automatically exported from the workstation to the instance running in Test Kitchen. Thanks @Xorima
- All local Workstation env vars are now passed to the instance running in Test Kitchen with the TKENV_ prefix. Thanks @Xorima
- Test Kitchen now includes support for Ohai plugins stored in the
ohaidirectory of cookbooks. Thanks @SAPDanJoe - Failures using the PowerShell provisioner have been resolved. Thanks@alanghartJC
- You can now download content from your test instance to you workstation using
downloadsconfig option inverify. Thanks @smurawski
The Kitchen AzureRM driver has updated from 0.15.1 to 1.0. This release fixes several failures from running the Kitchen Azurerm driver. It also includes support for Azure Marketplace plans and Managed Service Identity (MSI). Thanks @jasonwbarnett, @zanecodes, @albertvaka, and @KSerrania for these improvements.
The Kitchen Hyper-V driver has updated from 0.5.3 to 0.5.4, which resolves failures from getting the default VM Switch if there were spaces in the name. Thanks @kdoores for this improvement.
The Kitchen DigitalOcean driver has updated from 0.10.5 to 0.11.0. This release adds slugs for Ubuntu 20.04 / RHEL 8 / Fedora 31 support, increases the the default instance memory size to 1GB, and adds support for VPCs. Thanks @zmaupin, @tolland, and @gregf for these improvements.
The Kitchen EC2 driver has updated from 3.3 to 3.6. This release lets the driver cleanly exit if the test instance was destroyed outside of the Test Kitchen run, either by automation or in the console. Test Kitchen will also now select the subnet with the most available IPs to better distribute systems across multiple Availability Zones. Thanks @bdwyertech and @kamaradclimber for these improvements.
The Kitchen InSpec verifier has updated to allow setting Chef InSpec plugins for use during the verification. This new functionality can be enabled by adding load_plugins: true to your InSpec verifier config. Thanks @tecracer-theinen for this improvement.
The Kitchen Dokken driver has updated from 2.8.1 to 2.9.0. This release adds a new provisioning configuration, clean_dokken_sandbox, that does not require cleaning the Chef Infra and Test Kitchen files between converges. This configuration will speed up repeatedly converging systems. This defaults to true which maintains the existing behavior. Thanks @chrisUsick.
Knife Tidy has updated from 2.0.9 to 2.0.12, which provides compatibility with Chef Infra Client 15 and improves error handling in JSON parsing.
Knife Azure has updated from 2.0.6 to 3.0.0, which includes significant performance enhancements.
Knife EC2 has updated from 1.0.28 to 2.0. This update resolves several errors bootstrapping nodes and avoids attempting to bootstrap nodes using private DNS which may not be accessible from the node running the bootstrap command.
Knife Spork has updated from 1.7.2 to 1.7.3. This release adds a new --fail-if-frozen flag to knife spork check to only fail when local version matches a frozen version and allows the git plugin to push to the current branch. Thanks to @shoekstra and @zmaupin for these improvements.
Knife Windows has updated from 3.0.6 to 4.0.2. This update includes significant performance improvements, fixes for errors when using the concurrency flag, and better indication that the legacy bootstrap commands have been replaced.
Git has updated from 2.24.1 to 2.26.2 to resolve the following CVEs:
- CVE-2020-5260: Heap exposure vulnerability in the socket library
- CVE-2020-11008: Heap exposure vulnerability in the socket library
Ruby has updated from 2.6.5 to 2.6.6 to resolve the following CVEs:
- CVE-2020-16255: Unsafe Object Creation Vulnerability in JSON (Additional fix)
- CVE-2020-10933: Heap exposure vulnerability in the socket library
libarchive has updated from 3.4.0 to 3.4.2 to resolve multiple security vulnerabilities including the following CVEs:
- CVE-2019-19221: archive_wstring_append_from_mbs in archive_string.c has an out-of-bounds read because of an incorrect mbrtowc or mbtowc call
- CVE-2020-9308: archive_read_support_format_rar5.c in libarchive before 3.4.2 attempts to unpack a RAR5 file with an invalid or corrupted header
openSSL has updated from 1.0.2u to 1.0.2v, which does not address any particular CVEs, but includes multiple security hardening updates.
Rake has updated to 13.0.1 to resolve CVE-2020-8130.
Berkshelf has been updated from 7.0.8 to 7.0.9, which resolves errors when running berks verify and when using the --skip-syntax-check flag.
Chef Infra Client has been updated from 15.5 to 15.7 which includes improvements to the apt_repository, archive_file, cron, cron_d, file, launchd, sudo, user, windows_task, x509_certificate, and yum_repository resources as well as the usual collection of bug fixes and bootstrap improvements.
Chef InSpec has been updated from 4.18.39 to 4.18.51 with the following improvements:
- Example groups can now use InSpec resources
- The user resource can now check the last login date on Windows
- Improved the fetchers to fail consistently
Cookstyle has been updated from 5.13 to 5.20 with 30 new cops, improvements to existing cops, a new TargetChefVersion config option, and expanded cop departments.
Cookstyle now includes a new top-level configuration option TargetChefVersion. This new configuration option works similarly to RuboCop's TargetRubyVersion config option and allows you to specify a Chef Infra version that you want to target in your Cookstyle analysis. This prevents Cookstyle from autocorrecting cookbook code in a way that would make your cookbook incompatible with your desired Chef Infra Client version. It also makes it easier to perform staged upgrades of the Chef Infra Client by allowing you to step the TargetChefVersion one major version at a time.
Example .rubocop.yml config specifying a TargetChefVersion of 14.0:
AllCops:
TargetChefVersion: 14.0Cookstyle now includes two new Chef cop departments with a large number of existing cops moved into these more appropriate departments. Our goal is to have clearly defined cop departments that can be enabled or disabled to detect particular conditions in your cookbooks. Cops in the new ChefSharing department are focused around sharing cookbooks internally or on the public Supermarket. This includes things like ensuring proper license strings and complete metadata. Cops in the ChefRedundantCode category detect and correct unnecessary cookbook code. Anything detected by ChefRedundantCode cops can be removed regardless of the Chef Infra Client release you run in your infrastructure, so these are always safe to run.
With the addition of these new departments, we've moved many cops out of the ChefCorrectness department. Going forward only cops that detect code that may fail a Chef Infra Client run or cause it to behave incorrectly will be included in this category. We hope that ChefCorrectness along with ChefDeprecations are used in most cookbook CI pipelines.
kitchen-azurerm has been updated from 0.14.9 to 0.15.1 with the following improvements:
- Enable the WinRM HTTP listener by default. Thanks @sean-nixon
- Allow overriding of the
subscription_idby setting theAZURE_SUBSCRIPTION_IDENV variable. - Add a new
nic_nameconfig. Thanks @libertymutual - Support for creating VM with Azure KeyVault certificate. Thanks @javgallegos
kitchen-dokken has been updated to 2.8.1 which fixes a bug that prevented ENV vars from being passed into containers.
kitchen-google and knife-google plugins have been updated to allow the updated google-api-client SDK v0.35.
knife-ec2 has been updated from 1.0.17 to 1.0.28 with the following fixes:
- Resolved a missing credential error when using aws-profile.
- Mask AWS access keys data in any error or debug logs.
- Resolved ssh_gateway uninitialised error.
- Fixed invalid format of auto generated keypair file name.
- Raises an error if password length is less than 8 characters on Windows and will stop warning on passwords over 14 characters.
knife-tidy has been updated from 2.0.1 to 2.0.6 to resolve issues if an org was named cookbooks and to improve error messages.
mixlib-install has been updated from 3.11.21 to 3.11.24 and will now properly identify Windows 2019 hosts.
The chef-vault gem has been updated to 4.0.1. This release includes bug fixes from @MarkGibbons and @jeremy-clerc as well as a new way to update existing keys to sparse-mode by running knife vault update --keys_mode sparse thanks to @jeunito.
kitchen-ec2 has been updated to 3.3.0. This new version improves how we search for security groups by tags, improves the logic that detects usage of the chef Test Kitchen provisioner, and improves security group and spot instance logic. Thanks @slapvanilla and @bdwyertech for these enhancements.
We continue to optimize the size of the ChefDK package with this release taking up 12% less space on disk and containing 7,000 fewer files.
ChefDK packages are no longer produced for Windows 2008 R2 as this release reached its end of life on January 14th, 2020.
OpenSSL has been updated to 1.0.2u to resolve CVE-2019-1551
The embedded git client has been updated to 2.24.1 to resolve the following CVEs:
- CVE-2019-1348
- CVE-2019-1349
- CVE-2019-1350
- CVE-2019-1351
- CVE-2019-1352
- CVE-2019-1353
- CVE-2019-1354
- CVE-2019-1387
- CVE-2019-19604
The Chef Infra Client has been updated from 15.4.45 to 15.5.17 with updated helpers, Chefignore improvements, and a new chef_sleep resource:
Chef Infra Client now includes a new chef-utils gem which ships with a large number of helpers to make writing cookbooks easier. Many of these helpers existed previously in the chef-sugar gem. We have renamed many of the named helpers for consistency while providing backwards compatibility with existing chef-sugar names. Existing cookbooks written with chef-sugar should work unmodified with any of these new helpers. Expect a Cookstyle rule in the near future to help you update existing chef-sugar code to use the newer built-in helpers.
For more information on all of the new helpers available, see the chef-utils readme
We've reworked how chefignore files are handled in knife which has allowed us to close out a large number of long outstanding bugs. knife will now traverse all the way up the directory structure looking for a chefignore file. This means you can place a chefignore file in each cookbook or any parent directory in your repository structure. Additionally, we have made fixes that ensure that commands like knife diff and knife cookbook upload always honor your chefignore files.
The new chef_sleep resource can be used to sleep for a specified number of seconds during a Chef Infra Client run. This may be helpful to use with other commands that return a completed status before they are actually ready. In general, do not use this resource unless you truly need it.
Using with a Windows service that starts, but is not immediately ready:
service 'Service that is slow to start and reports as started' do
service_name 'my_database'
action :start
notifies :sleep, chef_sleep['wait for service start']
end
chef_sleep 'wait for service start' do
seconds 30
action :nothing
endThe Cookstyle cookbook linter has been updated from 5.9 to 5.13 and includes 28 new Chef cops for detecting deprecated and outdated cookbook code. This release also updates the underlying RuboCop engine used by Cookstyle which includes a large number of bug fixes that better detect violations and prevent false positives. See the Cookstyle Release Notes for a complete list of changes between 5.9 and 5.13.
This new release also allows you to use cookstyle specific comments in your cookbook code to enable or disable cops instead of the standard rubocop comments. We think that it will be easier to understand the cops that you intend to control if you use cookstyle comments. You can continue to use the existing rubocop comments, if you prefer them, since both types of comments will be honored by Cookstyle.
Rubocop comment to disable a cop:
'node.normal[:foo] # rubocop: disable ChefCorrectness/Bar'Cookstyle comment to disable a cop:
'node.normal[:foo] # cookstyle: disable ChefCorrectness/Bar'Foodcritic has been updated from 16.1.1 to 16.2.0. This release includes a fix for detecting incorrect notification actions and ships with updated Chef Infra Client Metadata. Keep in mind that Foodcritic is no longer being actively developed and users should migrate to Cookstyle instead.
Chef InSpec has been updated from 4.18.0 to 4.18.39. This release includes a large number of bug fixes to resources:
- The
serviceresource now includes astartnameproperty for Windows and systemd services. - The
nginxresource now includes parsing support for wildcard, dot prefix, and regex. - The
iis_app_poolresource now handles empty app pools. - The
filesystemresource now supports devices with very long names. - The
aptbetter handles URIs and supports repos with anarch. - The
oracledb_sessionhas received multiple fixes to make it work better.
We updated Test Kitchen has to 2.3.4, which includes more robust code for finding the Chef binary on Windows and also improves some logging messages.
The knife-ec2 plugin has been updated from 1.0.16 to 1.0.17 which includes a fix for an error when launching non-T2 type instances.
kitchen-digitalocean has been updated to 0.10.5 which adds new image aliases for Debian-10 and FreeBSD-12.
kitchen-dokken has been updated to 2.8.0. This will make the CI and TEST_KITCHEN environmental variables match the behavior of kitchen-vagrant.
We updated the kitchen-inspec plugin to 1.3.1, which allows relative paths in the GIT fetcher and resolves failures when using inputs.
This release of ChefDK ships with several optimizations to our Ruby installation that improve the performance of the included commands, especially on Windows systems. Expect to see more here in future releases.
libxlst was updated from 1.1.30 to 1.1.34 to resolve these vulnerabilities:
We are now publishing Habitat packages for ChefDK 4. See chef/chef-dk on Habitat Depot for a complete list of available versions.
Chef Infra Client has been updated from 15.3 to 15.4 with updated resources and several significant fixes to knife bootstrap. See the Chef Infra Client 15.4 Release Notes for a complete list of the new and improved functionality.
Chef InSpec has been updated from 4.16 to 4.18 with the following changes:
- We have released our beta Chef InSpec plug-in for HashiCorp Vault. Check it out in our inspec-vault GitHub repo and let us know what you think -- or better yet, start jumping in and contributing with us on it.
- Waivers, our new beta feature, was added to InSpec! Waivers allows you to better manage compliance failures. We would love to hear your feedback on this! See the InSpec Waivers documentation for more details.
- The
interfaceresource now has a name property. - Expanded
userresource to include the passwordage, maxbadpasswords, and badpasswordattempts properties with Windows. - The
sys_inforesource now supports ip_address, fqdn, domain, and short options when giving a version of the hostname. - Sped up initial load/response time for all commands by removing pre-leading of resources on invocation of inspec.
- If an error occurs when using the
jsonresource with a command source, you will now get the error message from STDERR returned in the report. - We improved the formatting of the usage help, so what you see when you type
inspec exec --helpshould look better!
Cookstyle has been updated from 5.6.2 to 5.9.3, which includes 13 new Chef cops, improved detection in existing cops, and improved autocorrection. See the Cookstyle 5.7, 5.8, and 5.9 release notes for additional information on the new cops.
knife-google was updated from 4.1.0 to 4.2.0 with support for adding multiple local SSD interfaces to a new instance.
knife-vsphere was updated from 4.0.1 to 4.0.3, which resolves a bug in determining the state of instances.
Ruby has been updated from 2.6.4 to 2.6.5 in order to resolve the following CVEs:
- CVE-2019-16255: A code injection vulnerability of Shell#[] and Shell#test
- CVE-2019-16254: HTTP response splitting in WEBrick (Additional fix)
- CVE-2019-15845: A NUL injection vulnerability of File.fnmatch and File.fnmatch?
- CVE-2019-16201: Regular Expression Denial of Service vulnerability of WEBrick’s Digest access authentication
Chef Infra Client has been updated from 15.2 to 15.3 with updated resources, a new way to write streamlined custom resources, and updated platform support! See the Chef Infra Client 15.3 Release Notes for a complete list of the new and improved functionality.
Chef InSpec has been updated from 4.10.4 to 4.16.0 with the following changes:
- A new
postfix_confhas been added for inspecting Postfix configuration files. - A new
pluginssection has been added to the InSpec configuration file which can be used to pass secrets or other configurations into Chef InSpec plugins. - The
serviceresource now includes a newstartnameproperty for determining which user is starting the Windows services. - The
groupsresource now properly gathers membership information on macOS hosts.
See the Chef InSpec 4.16.0 Release Notes for more information.
Cookstyle has been updated from 5.1.19 to 5.6.2. This update brings the total number of Chef cops to 94 and divides the cops into four separate departments. The new departments make it easier to search for specific cops, and to enable and disable groups of cops. Instead of just "Chef", we now have the following departments:
ChefDeprecations: Cops that detect, and in many cases correct, deprecations that will prevent cookbooks from running on modern versions of Chef Infra Client.ChefStyle: Cops that will help you improve the format and readability of your cookbooks.ChefModernize: Cops that will help you modernize your cookbooks by including features introduced in new releases of Chef Infra Client.ChefEffortless: Cops that will help you migrate your cookbooks to the Effortless pattern. These are disabled by default.
You can run cookstyle with just a single department:
cookstyle --only ChefDeprecationsYou can also exclude a specific department from the command line:
cookstyle --except ChefStyleYou can also disable a specific department by adding the following to your .rubocop.yml config:
ChefStyle:
Enabled: falseSee the Cookstyle cops documentation for a complete list of cops included in Cookstyle 5.6.
Going forward, Cookstyle will be our sole Ruby and Chef Infra cookbook linting tool. With the release of Cookstyle 5.6, we're officially deprecating Foodcritic and will not be shipping Foodcritic in the next major release of Chef Workstation (April 2020). See our Goodbye, Foodcritic blog post for more information on why Cookstyle is replacing Foodcritic.
kitchen-ec2 has been updated from 3.1.0 to 3.2.0. This adds support for Windows Server 2019 and adds the ability to look up security group by subnet_filter in addition to subnet_id.
kitchen-inspec has been updated from 1.1.0 to 1.2.0. This renames the attrs key to input_files, and the attributes key to inputs to match InSpec 4. The old names are still supported, but issue a warning.
knife-ec2 has been updated from 1.0.12 to 1.0.16. This resolves the following issues:
- Fix argument error for --platform option #609 (dheerajd-msys)
- Fix for Generate temporary keypair when none is supplied #608 (kapilchouhan99)
- Color code fixes in json format output of knife ec2 server list #606 (dheerajd-msys)
- Allow instances to be provisioned with source/dest checks disabled #605 (kapilchouhan99)
Test Kitchen has been updated from 2.2.5 to 2.3.2 with the following changes:
- Add
keepalive_maxcountsetting for better control of ssh connection timeouts. - Add
lifecycle_hooksinformation tokitchen diagnoseoutput.
The knife-google plugin has been updated to 4.1.0 with support for bootstrapping Chef Infra Client 15, and also includes a new knife google image list command, which lists project and public images.
For example knife google image list --gce_project "chef-msys":
NAME PROJECT FAMILY DISK SIZE STATUS
kpl-w-image chef-msys windows 60 GB READY
centos-6-v20190916 centos-cloud centos-6 10 GB READY
centos-7-v20190916 centos-cloud centos-7 10 GB READY
coreos-alpha-2261-0-0-v20190911 coreos-cloud coreos-alpha 9 GB READY
coreos-beta-2247-2-0-v20190911 coreos-cloud coreos-beta 9 GB READY
....
....
....
Git has been updated from 2.20.0 to 2.23.0 on Windows and from 2.14.1 to 2.23.0 on non-Windows systems. This brings the latest git workflows to our users who do not have it installed another way and fixes two CVEs:
- non-Windows systems: CVE-2017-14867
- Windows systems: CVE-2019-1211
Nokogiri has been updated from 1.10.2 to 1.10.4 in order to resolve CVE-2019-5477
OpenSSL has been updated from 1.0.2s to 1.0.2t in order to resolve CVE-2019-1563 and CVE-2019-1547.
Ruby has been updated from 2.6.3 to 2.6.4 in order to resolve CVE-2012-6708 and CVE-2015-9251.
Chef DK is now validated against macOS 10.15 (Catalina). Additionally, Chef DK will no longer be validated against macOS 10.12.
ChefDK 4.3 now includes native packages for RHEL 8 with all builds now validated on RHEL 8 hosts.
Packages will no longer be built for SUSE Linux Enterprise Server (SLES) 11 as SLES 11 exited the 'General Support' phase on March 31, 2019. See Chef's Platform End-of-Life Policy for more information on when Chef ends support for an OS release.
Chef Infra Client has been updated from 15.1 to 15.2 with new and improved resources and support for RHEL 8. See the Chef Infra Client 15.2 Release Notes for a complete list of new and improved functionality.
Chef InSpec has been updated from 4.7.3 to 4.10.4 with the following changes:
- Fixed handling multiple triggers in the
windows_taskresource - Fixed exceptions when resources are used with incompatible transports
- Un-deprecated the
be_runningmatcher on theserviceresource - Added
sys_info.manufacturerandsys_info.modelresources - Added
ip6tablesresource
Cookstyle has been updated from 5.0 to 5.1.19 with twenty-four new Chef specific cops to detect, and in many cases, to auto-correct errors in your cookbook code. With the release of Cookstyle 5.1, we have started the process of replacing Foodcritic with Cookstyle. Cookstyle offers a modern configuration system, auto-correction, and a faster and more reliable engine thanks to RuboCop. We will continue to port useful rules from Foodcritic to Cookstyle, as well as add rules that were not possible in the legacy Foodcritic engine. See the Cookstyle 5.1 Release Notes for a complete list of new rules.
kitchen-azurerm has been updated from 0.14.8 to 0.14.9, which adds a new use_ephemeral_osdisk configuration option. See Microsoft's Empheral OS Disk Announcement for more information on this new feature.
kitchen-ec2 has been updated from 3.0.1 to 3.1.0 with several new features:
- Added support for SSH through Session Manager. Thanks @awiddersheim
- Adds support for searching for multiple security groups, as well as searching by group name. Thanks @bdwyertech
- Allows asking for multiple instance types and subnets for spot pricing. Thanks @vmiszczak-teads
kitchen-vagrant has been updated from 1.5.2. to 1.6.0. This new version properly truncates the instance name to avoid hitting the 100 character limit in Hyper-V, and also updates the hostname length limit on Windows from 12 characters to 15 characters. Thanks @Xorima and @PowerSchill.
knife-ec2 has beeen updated from 1.0.8 to 1.0.12. This new version includes multiple fixes for network configuration setup, a new --cpu-credits option for launching T2/T3 instances as unlimited, and fixes for issues with attaching emphemeral disks.
- Rubygems has been rolled back to 3.0.3 to resolve duplicate bundler gems that shipped in ChefDK 4.1.7. This resulted in warning messages when running commands as well as performance degradations.
- Fixed 'chef install foo.lock.json' errors when loading cookbooks from Artifactory.
Knife-ec2 has been updated to 1.0.8. This release removes previously deprecated bootstrap command-line options that were removed from Chef Infra Client 15.
Knife-vsphere has been updated to 3.0.1 to resolve Ruby warnings that occurred when running some commands.
Fauxhai has been updated to 7.4.0, which adds additional platforms for use with ChefSpec testing.
- Updated
suse15 from 15.0 to 15.1 - Added a new
redhat8 definition to replace the 8.0 definition, which is now deprecated - Updated all
amazonandubuntureleases to Chef 15.1 - Added
debian10 and 9.9
Chef InSpec has been updated to 4.7.3, which adds a new ip6tables resource and includes new aws-sdk gems that are necessary for the Chef InSpec AWS Resource Pack.
Chef Infra Client has been updated to 15.1 with new and improved resources, improvements to target mode, bootstrap bug fixes, new Ohai detection on VirtualBox hosts, and more. See the Chef Infra Client 15.1 Release Notes for a complete list of new and improved functionality.
Chef InSpec has been updated from 4.3.2 to 4.6.9 with the following changes:
- InSpec
Attributeshave now been renamed toInputsto avoid confusion with Chef Infra attributes. - A new InSpec plugin type of
Inputhas been added for defining new input types. See the InSpec Plugins documentation for more information on writing these plugins. - InSpec no longer prints errors to the stdout when passing
--format json. - When fetching profiles from GitHub, the URL can now include periods.
- The performance of InSpec startup has been improved.
Cookstyle has been updated to 5.0.0 with a large number of bugfixes and major improvements that lay the groundwork for future autocorrecting of cookobook style and deprecation warnings.
The RuboCop engine that powers Cookstyle has been updated from 0.62 to 0.72, which includes several hundred bugfixes to the codebase. Due to some of these bugfixes, existing cookbooks may fail when using Cookstyle 5.0. Additionally, some cops have had their names changed and the Rubocop Performance cops have been removed. If you disabled individual cops in your .rubocop.yml file, this may require you to update your confg.
This new release also merges in code from the rubocop-chef project, providing new alerting and autocorrecting capabilities specific to Chef Infra Cookbooks. Thank you @coderanger for your work in the rubocop-chef project and @chrishenry for helping with new cops.
Foodcritic has been updated from 16.0.0 to 16.1.1 with new rules and support for the latest Chef:
- Updated Chef Infra Client metadata for 15.1 to include the new
chocolatey_featureresources, as well as new properties in thelaunchdandchocolatey_sourceresources - Added new rule to detect large files shipped in a cookbook:
FC123: Content of a cookbook file is larger than 1MB. Thanks @mattray - Allowed configuring the size of the AST cache with a new
--ast-cache-sizecommand line option. Thanks @Babar
ChefSpec has been updated to 7.4 with better support stubbing commands, and a new policyfile_path configuration option for specifying the path to the PolicyFile.
kitchen-dokken has been updated to 2.7.0 with new options for controlling how containers are setup and pulled. You can now disable user namespace mode when running privileged containers with a new userns_host config option. There is also a new option pull_chef_image (true/false) to control force-pulling the chef image on each run to check for newer images. This option now defaults to true so that testing on latest and current always actually mean latest and current. See the kitchen-dokken readme for kitchen.yml config examples.
kitchen-digitalocean has been updated to 0.10.4 with support for new distros and additional configuration options for instance setup. You can now control the default DigitalOcean region systems that are spun up by using a new DIGITALOCEAN_REGION env var. You can still modify the region in the driver section of your kitchen.yml file if you'd like, and the default region of nyc1 has not changed. This release also adds slug support for fedora-29, fedora-30, and ubuntu-19. Finally, if you'd like to monitor your test instances, the new monitoring configuration option in the kitchen.yml driver section allows enabling DigitalOcean's instance monitoring. See the kitchen-digitalocean readme for kitchen.yml config examples.
knife-vsphere has been updated to 3.0. This new version adds support for specifying the bootstrap_template when creating new VMs. This release also improves how the plugin finds VM hosts, in order to support hosts in nested directories.
knife-ec2 has received a near-complete rewrite with this release of ChefDK. The new knife-ec2 release switches the underlying library used to communicate with AWS from fog-aws to Amazon's own aws-sdk. The official AWS SDK has greatly improved support for the many AWS authentication methods available to users. It also has support for all of the latest AWS regions and instance types. As part of this switch to the new SDK we did have to remove the knife ec2 flavor list command as this used hard coded values from fog-aws and not AWS API calls. The good news is, we were able to add several new commands to the plugin. This makes provisioning systems in AWS even easier.
This command lists all VPCs in your environment including the ID, which you need when provisioning new systems into a specific VPC.
$ knife ec2 vpc list
ID State CIDR Block Instance Tenancy DHCP Options ID Default VPC?
vpc-b1bc8d9d available 10.0.0.0/16 default dopt-1d78412a No
vpc-daafd931 available 172.0.0.0/16 default dopt-1d78412a Yes
This command lists all ENIs in your environment including the ID, which you need when adding the ENI to a newly provisioned instance.
$ knife ec2 eni list
ID Status AZ Public IP Private IPs IPv6 IPs Subnet ID VPC ID
eni-0123f25ae7805b651 in-use us-west-2a 63.192.209.236 10.0.0.204 subnet-4ef3b123 vpc-b1bc8d9d
eni-2451c913 in-use us-west-2a 137.150.209.123 10.0.0.245 subnet-4ef3b123 vpc-b1bc8d9d
This command lists all security groups in your environment including the ID, which you need when assigning a newly provisioned instance to a group.
$knife ec2 securitygroup list
ID Name VPC ID
sg-12332d875a4a123d6 not-today-hackers vpc-dbbf59a2
sg-123708ab12388cac5 open-to-the-world vpc-dbbf59a2
This command lists all subnets in your environment including the ID, which you need when placing a newly provisioned instance in a subnet.
$ knife ec2 subnet list
ID State CIDR Block AZ Available IPs AZ Default? Maps Public IP? VPC ID
subnet-bd2333a9 available 172.31.0.0/20 us-west-2b 4091 Yes Yes vpc-b1bc8d9d
subnet-ba1135c9 available 172.31.16.0/20 us-west-2a 4091 Yes Yes vpc-b1bc8d9d
Ubuntu 14.04 entered the end-of-life phase April 30, 2019. Since this version of Ubuntu is now end-of-life, we have stopped building packages for Ubuntu 14.04. If you rely on Ubuntu 14.04 in your environment, we highly recommend upgrading your host to Ubuntu 16.04 or 18.04.
- CVE-2019-5435: Integer overflows in curl_url_set
- CVE-2019-5436: tftp: use the current blksize for recvfrom()
- CVE-2018-16890: NTLM type-2 out-of-bounds buffer read
- CVE-2019-3822: NTLMv2 type-3 header stack buffer overflow
- CVE-2019-3823: SMTP end-of-response out-of-bounds read
- CVE-2019-5443: Windows OpenSSL engine code injection
- Our
cacertbundle has been updated to the 5-11-2019 bundle, which adds four additional CAs.
Usage of ChefDK 4.0, Chef Infra Client 15, and InSpec 4 requires accepting the Chef EULA. See the frequently asked questions for information about the license update and the associated business model change.
Chef Provisioning is no longer included with Chef DK, and will be officially end of life on August 31, 2019. The source code of Chef Provisioning and the drivers have been moved into the chef-boneyard GitHub organization and will not be further maintained. Current users of Chef Provisioning should contact your Chef Customer Success Manager or Account Representative to review your options.
knife bootstrap was rewritten in Chef Infra Client 15.
The knife-* cloud providers need to be updated to use this new API.
As of ChefDK 4.0, knife bootstrap functionality against the cloud providers will be broken.
We will fix this ASAP in a ChefDK 4.1 release.
The only gem not affected is the knife-windows gem.
It has already been re-written to leverage the new bootstrap library.
Affected gems:
knife-ec2knife-googleknife-vsphere
If you leverage this functionality, please wait to update ChefDK until 4.1 is released with fixes for these gems.
The chef generate command has been updated to produce cookbooks and repositories that match Chef's best practices.
chef generate reponow generates a Chef repository with Policyfiles by default. You can revert to the previous roles / environment behavior with the--rolesflag.chef generate cookbooknow generates a cookbook with a Policyfile and no Berksfile by default. You can revert to the previous behavior with the--berksflag.chef generate cookbooknow includes ChefSpecs that utilize the ChefSpec 7.3+ format. This is a much simpler syntax that requires less updating of specs as older platforms are deprecated.chef generate cookbookno longer creates cookbook files with the unecessaryfrozen_string_literal: truecomments.chef generate cookbookno longer generates a full Workflow (Delivery) build cookbook by default. A new--workflowflag has been added to allow generating the build cookbook. This flag replaces the previously unused--deliveryflag.chef generate cookbooknow generates cookbooks with metadata requiring Chef 14 or later.chef generate cookbook --kitchen dokkennow generates a fully working kitchen-dokken config.chef generate cookbooknow generates Test Kitchen configs with theproduct_name/product_versionmethod of specifying Chef Infra Client releases asrequire_chef_omnibuswill be removed in the next major Test Kitchen release.chef generate cookbook_fileno longer places the specified file in a "default" folder as these aren't needed in Chef Infra Client 12 and later.chef generate repono longer outputs the full Chef Infra Client run information while generating the repository. Similar to thecookbookcommand you can view this verbose output with the--verboseflag.
Chef InSpec has been updated to 4.3.2 which includes the new InSpec AWS resource pack with 59 new AWS resources, multi-region support, and named credentials support. This release also includes support for auditing systems that use ed25519 SSH keys.
Chef Infra Client has been updated to Chef 15 with 8 new resources, target mode prototype functionality, ed25519 SSH key support, and more. See the Chef Infra Client 15 Release Notes for more details.
Fauxhai has been updated from 6.11 to 7.3. This removes all platforms that were previously marked as deprecated. So if you've noticed deprecation warnings during your ChefSpec tests, you will need to update those specs for the latest supported Faxhai platforms. This release also adds the following new platform releases for testing in ChefSpec:
- RHEL 6.10 and 8.0
- openSUSE 15.0
- CentOS 6.10
- Debian 9.8 / 9.9
- Oracle Linux 6.10, 7.5, and 7.6
Test Kitchen has been updated from 1.24 to 2.2.5. This update adds support for accepting the Chef Infra Client and Chef InSpec EULAs during testing, as well as support for newer ed25519 format SSH keys on guests. The newer release does remove support for the legacy Librarian depsolver and testing of Chef Infra Client 10/11 releases in some scenarios. See the Test Kitchen Release Notes for additional details on this release.
Kitchen-ec2 has been updated to 3.0, which uses the newer aws-sdk-v3 and includes a large number of improvements to the driver including improved hostname detection, backoff retries, additional security group configuration options, and more. See the kitchen-ec2 Changelog for additional details.
Kitchen-dokken has been updated to 2.6.9 with a new config option pull_platform_image, which allows you to disable pulling the platform Docker image on every Test Kitchen converge / test. This is particularly useful for local platform image testing.
kitchen.yml example:
driver:
name: dokken
pull_platform_image: falseChef Infra Client has been updated to 14.13.11 with resource improvements and bug fixes. See the Release Notes for a detailed list of changes.
Test Kitchen has been updated to 1.25 with backports of many non-breaking Test Kitchen 2.0 features:
- Support for accepting the Chef 15 license in Test Kitchen runs. See Accepting the Chef License for usage details.
- A new
--fail-fastcommand line flag for use with theconcurrencyflag. With this flag set, Test Kitchen will immediately fail when any converge fails instead of continuing to test additional instances. - The
policyfile_pathconfig option now accepts relative paths. - A new
berksfile_pathconfig option allows specifying Berkshelf files in non-standard locations. - Retries are now honored when using SSH proxies
- The Chef Docker image is now pulled by default so that locally cached
latestorcurrentcontainer versions will be compared to those available on DockerHub. See the readme for instructions on reverting to the previous behavior. - User namespace mode can be disabled when running privileged containers with a new
userns_hostconfig option. See the readme for details. - You can now disable pulling the platform Docker images for local platform image testing or air gapped testing. See the readme for details.
- openssl 1.0.2r -> 1.0.2s (bugfix only release)
- cacerts 2019-01-23 -> 2019-05-15
- CVE-2019-5435: Integer overflows in curl_url_set
- CVE-2019-5436: tftp: use the current blksize for recvfrom()
- CVE-2018-16890: NTLM type-2 out-of-bounds buffer read
- CVE-2019-3822: NTLMv2 type-3 header stack buffer overflow
- CVE-2019-3823: SMTP end-of-response out-of-bounds read
include_policy now supports :remote policy files. This new functionality allows you to include policy files over http. Remote policy files require remote cookbooks and install will fail otherwise if the included policy file includes cookbooks with paths. Thanks @mattray!
kitchen-vagrant: 1.5.1 -> 1.5.2mixlib-install: 3.11.12 -> 3.11.18chef: 14.12.3 -> 14.12.9
ChefDK now ships with Chef 14.12.3. See Chef 14.12 release notes for more information on what's new.
ChefDK now ships with InSpec 3.9.0. See InSpec 3.9.0 release details for more information on what's new.
Ruby has been updated from 2.5.3 to 2.5.5, which includes a large number of bug fixes.
kitchen-hyperv has been updated to 0.5.3, which now automatically disables snapshots on the VMs and properly waits for the IP to be set.
kitchen-vagrant has been updated to 1.5.1, which adds support for using the new bento/amazonlinux-2 box when setting the platform to amazonlinux-2.
kitchen-ec2 has been updated to 2.5.0 with support for Amazon Linux 2.0 image searching using the platform 'amazon2'. This release also adds supports Windows Server 1709 and 1803 image searching.
knife-vsphere has been updated to 2.1.3, which adds support for knife's bootstrap_template flag and removes the legacy distro and template_file flags.
Push Jobs Client has been updated to 2.5.6, which includes significant optimizations and minor bug fixes.
Rubygems has been updated from 2.7.8 to 2.7.9 to resolves 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
ChefDK now ships with Inspec 3.6.6. See InSpec 3.6.6 release details for more information on what's new.
- Added Windows 2019 Server, Red Hat Linux 7.6, Debian 9.6, and CentOS 7.6.1804.
- Updated Windows7, 8.1, and 10, 2008 R2, 2012, 2012 R2, and 2016 to Chef 14.10.
- Update Oracle Linux 6.8/7.2/7.3/7.4 to Ohai 14.8 in EC2
- Updated the fetcher logic to be compatible with ChefSpec 7.3+. Thanks @oscar123mendoza
- Removed duplicate json data in gentoo 4.9.6
- Fixes issue #1913. No longer producess corrupted archives on windows. Thanks @kenmacleod for the fix!
kitchen-digitalocean: 0.10.1 -> 0.10.2mixlib-install: 3.11.5 -> 3.11.11
OpenSSL updated to 1.0.2r to resolve CVE-2019-1559
ChefDK now ships with Chef 14.10.9. See https://docs.chef.io/release_notes.html for more information on what's new.
ChefDK now ships with InSpec 3.4.1. See https://github.com/inspec/inspec/releases/tag/v3.4.1 for more information on what's new.
Support bastion configuration in transport options.
This fixes audio for virtualbox users by disabling audio in virtualbox by default to prevent interrupting the host's Bluetooth audio.
Support Azure Managed Identities and apply vm_tags to all resources in resource group.
bundler: 1.16.1 -> 1.17.3chef-apply: 0.2.4 -> 0.2.7kitchen-tidy: 1.2.0 -> 2.0.0rubygems: 2.7.6 -> 2.7.8
chef provision- Chef Provisioning has been in maintenance mode since 2015 and due to the age of it's dependencies it cannot be included in ChefDK 4 which is scheduled for an April release. Additional information on the future of Chef Provisioning will be announced in the coming weeks.
ChefDK now ships with Chef 14.8.12. See https://docs.chef.io/release_notes.html for more information on what's new.
OpenSSL updated to 1.0.2q to resolve:
- Microarchitecture timing vulnerability in ECC scalar multiplication (CVE-2018-5407)
- Timing vulnerability in DSA signature generation (CVE-2018-0734)
- New option:
chef generate cookbook --kitchen (dokken|vagrant)Generate cookbooks with a specific kitchen configuration (defaults to vagrant).
chef-client has been updated from 14.7 to 14.8, which includes resources improvements and bug fixes throughout.
- Added new aws_sqs_queue resource. Thanks @amitsaha
- Exposed additional WinRM options for transport, basic auth, and SSPI. Thanks @frezbo
- Improved UI experience throughout including new CLI flags --color/--no-color and --interactive/--no-interactive
- Added
berks outdated --allcommand to get a list of outdated dependencies, including those that wouldn't satisfy the version constraints set in Berksfile. Thanks @jeroenj
- Added Fedora 29 Ohai dump for use in ChefSpec
- Added a new parallels? helper. Thanks @ehanlon
- Added support for the Raspberry Pi 1 and Zero to armhf? helper
- Added a centos_final? helper. Thanks @kareiva
- Updated the Chef metadata to 13.12 / 14.8 and removed all other Chef metadata
- Resolved failures in the plugin by updating the azure API gems
- Added support for arm64 architecture instances
- Support Windows Server 1709 and 1803 image searching. Thanks @xtimon
- Support Amazon Linux 2.0 image searching. Use the platform 'amazon2'. Thanks @pschaumburg
- Allow passing the
--bootstrap-templateoption during node bootstrapping
- Allow running knife google zone list, region list, region quotas, project quotas to run without specifyig the
gce_zoneoption
- The yank command has been removed as this command causes large downstream impact to other users and should not be part of the tooling
- The metadata.rb file will now be included in uploads to match the behavior of berkshelf 7+
- Added support for the Chef 13+ root aliases. With this chance you can now test a cookbook with a simple recipe.rb and attributes.rb file.
- Improve WinRM support with retries and graceful connection cleanup. Thanks @bdwyertech and @dwozx
ChefDK now ships with Chef 14.7.17. See https://docs.chef.io/release_notes.html for more information on what's new.
The chef/chefdk Docker image now includes graphviz (to support berks viz) and rsync (to support kitchen-dokken) which makes it a little bigger, but also a little more useful in development and test pipelines.
ChefDK now ships with Chef 14.6.47. See https://docs.chef.io/release_notes.html for more information on what's new.
ChefDK RPM and Debian packages are now compressed. Additionally many gems were updated to remove extraneous files that do not need to be included. The download size of packages has decreased accordingly (all measurements in megabytes):
- .deb: 108 -> 84 (22%)
- .rpm: 112 -> 86 (24%)
macOS 10.14 (Mojave) is now fully tested and packages are available on downloads.chef.io.
Fauxhai has been updated from 6.6.0 to version 6.9.1. This update brings in the latest mocked Ohai run data for use with ChefSpec. This release adds data for Linux Mint 19, macOS 10.14, Solaris 5.11 (11.4 release), and SLES 15. This release also deprecates the following platforms for removal April 2018: Linux Mint 18.2, Gentoo 4.9.6, All versions of ios_xr, All versions of omnios, All versions of nexus, macOS 10.10, and Solaris 5.10. See https://github.com/chefspec/fauxhai/tree/master/lib/fauxhai/platforms for a complete list of non-deprecated platform data for use with ChefSpec.
Foodcritic has been updated from 14.1 to 14.3. This updates the metadata that ships with Foodcritic to provide the latest Chef 13.11 and 14.5 metadata, while removing metadata from older Chef releases. This update also removes the FC121 rule, which was causing confusion with community cookbook authors. This rule will be added back when Chef 13 goes EOL in April 2019.
This release updates InSpec from 2.2.112 to 3.0.12. This is a major milestone and includes the plugin system, global attributes, enhanced skip messaging, and more. Please head over to https://www.inspec.io/ for a full rundown.
The Kitchen AzureRM driver now supports the Shared Image Gallery.
The Kitchen DigitalOcean driver now supports FreeBSD 10.4 and 11.2 in Kitchen configs.
Kitchen EC2 has been updated to better support Windows systems. The auto-generated security group will now include support for RDP and the log directory will alway be created.
Kitchen Google now includes support for adding labels to instances with a new labels config that accepts labels as a hash.
Knife Windows has improved Windows detection support to identify Windows 2012r2, 2016, and 10. Additionally when bootstrapping nodes, there is now support for using the client.d directories.
Ruby has been updated to 2.5.3 to resolve the following vulnerabilities:
CVE-2018-16396: Tainted flags are not propagated in Array#pack and String#unpack with some directivesCVE-2018-16395: OpenSSL::X509::Name equality check does not work correctly
ChefDK now ships with Chef 14.5.33. See https://docs.chef.io/release_notes.html for more information on what's new.
- New option:
chef update --exclude-depsfor policyfiles will only update the cookbook(s) given on the command line.
ChefSpec 7.3.2 greatly simplifies the syntax as well as allows testing of custom resources. See the README and especially the section on testing custom resoures for examples of the new syntax.
chef-provisioning-aws: 3.0.4 -> 3.0.6chef-vault: 3.3.0 -> 3.4.2foodcritic: 14.0.0 -> 14.1.0inspec: 2.2.70 -> 2.2.112kitchen-inspec: 0.23.1 -> 0.24.0kitchen-vagrant: 1.3.3 -> 1.3.4
chef generate app- Application repos were a pattern that didn't take off.chef generate lwrp- Usechef generate resource. Every supported release of Chef knows about custom resources. Custom resources are awesome. No one should be writing new LWRPs any more. LWRPS are not awesome.
ChefDK now ships with Chef 14.4.56. See https://docs.chef.io/release_notes.html for more information on what's new.
- New
chef describe-cookbookcommand to display the cookbook checksum. - Change policyfile generator to use 'policyfiles' directory instead of 'policies' directory
Chef Apply is the new gem which provides ad-hoc node management via the chef-run binary. It is included in the ChefDK only as a stepping stone towards managing gem resolution in the Chef Workstation repository. Please continue to download and install Chef Workstation if you wish to use the ad-hoc functionality. No guarantees for backwards compatability or functionality are made for the Chef Apply gem when used via the ChefDK.
ChefDK now includes a driver for Azure Resource Manager. This allows Microsoft Azure resources to be provisioned prior to testing. This driver uses the new Microsoft Azure Resource Management REST API via the azure-sdk-for-ruby.
Test Kitchen 1.23 now includes support for lifecycle hooks.
berkshelf: 7.0.4 -> 7.0.6chef-provisioning: 2.7.1 -> 2.7.2chef-provisioning-aws: 3.0.2 -> 3.0.4chef-sugar: 4.0.0 -> 4.1.0fauxhai: 6.4.0 -> 6.6.0inspec: 2.1.72 ->2.2.70kitchen-google: 1.4.0 -> 1.5.0
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)
ChefDK now ships with Chef 14.2.0. See https://docs.chef.io/release_notes.html for more information on what's new.
ChefDK is now released as a habitat package under the identifier chef/chef-dk. All successful builds will be available in the unstable channel and all promoted builds will be available in the stable channel. This is similar to the current and stable downloads of ChefDK available on https://downloads.chef.io/chefdk/stable.
On macOS you can install ChefDK using brew cask install chef/chef/chefdk. This behavior is not new but the tap name changed.
Fauxhai 6.4.0 brings support for 3 new platforms - CentOS 7.5, Debian 8.11, and FreeBSD 11.2. It also updates the dumps for Amazon Linux, Redhat, SLES, and Ubuntu to match Chef 14.2 output. Finally it deprecates FreeBSD 10.3.
Foodcritic 14.0.0 adds support for Chef 14.2 metadata, makes it the default, and removes old Chef 13 metadata. It also updated rules for clarity, removed an unnecessary rule, and added a new rule saying when cookbooks have unnecessary dependencies now that resources moved into core Chef. See the changelog for a full list of changes.
knife-acl is now included with ChefDK. This knife plugin allows admin users to modify Chef Server ACLs from their command line.
knife-tidy is now included with ChefDK. This knife plugin generates reports about stale nodes and helps clean them up.
Test Kitchen 1.11.0 adds a new ssh_gateway_port config and fixed a bug on Unix systems where scripts were not created as executable.
fauxhai: 6.3.0 -> 6.4.0foodcritic: 13.1.1 -> 14.0.0kitchen-digitalocean: 0.9.8 -> 0.10.0knife-opc: 0.3.2 -> 0.4.0test-kitchen: 1.21.2 ->1.22.0
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)
-
CVE-2018-1000201: DLL loading issue which can be hijacked on Windows OS
ChefDK now ships with Chef 14.1.1. See https://docs.chef.io/release_notes.html for more information on what's new.
ChefDK now ships packages for Ubuntu 18.04 and Debian 9. In accordance with Chef's platform End Of Life policy, ChefDK is no longer shipped on macOS 10.10.
ChefDK now uses an embedded copy of libarchive to support Policyfile and Berkshelf. This improves overall performance and provides a well tested interface to many different types of archives. It also resolves the long standing "not an octal string" problem users face when depending on certain cookbooks in the supermarket.
Policyfiles now support git targets for included policies.
include_policy 'base_policy',
git: 'https://github.com/happychef/chef-repo.git',
branch: master,
path: 'policies/base/Policyfile.lock.json'
When using this, behavior is very strict: it updates only the cookbook(s) mentioned on command line.
Test Kitchen has been updated from 1.20.0 to 1.21.2. This release allows you to use a kitchen.yml config file instead of .kitchen.yml so the kitchen config will no longer be hidden in your cookbook directories. It also introduces new config options for SSH proxy servers and allows you to specify multiple paths for data bags. See https://github.com/test-kitchen/test-kitchen/blob/master/CHANGELOG.md for the complete list of changes.
InSpec has been updated from 1.51.21 to 2.1.68. 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.
ChefSpec has been updated to 7.2.1 with Fauxhai 6.2.0. This release removes all platforms that were previously marked as deprecated in Fauxhai. If you saw Fauxhai deprecation warnings during your ChefSpec runs these will now be failures. This update also adds 9 new platforms and updates existing data for Chef 14. To see a complete list of platforms that can be mocked in ChefSpec see https://github.com/chefspec/fauxhai/blob/master/PLATFORMS.md.
Foodcritic has been updated to from 12.3.0 to 13.1.1. This updates Foodcritic for Chef 13 or later by removing Chef 12 metadata and removing several legacy rules that suggested writing resources in a Chef 12 manner. The update also adds 9 new rules for writing custom resources and updating cookbooks to Chef 13 and 14, resolves several long standing file detection bugs, and improves performance.
Cookstyle has been updated to 3.0, which updates the underlying RuboCop engine to 0.55 with a long list of bug fixes and improvements. This release of Cookstyle also enables 19 new rules available in RuboCop. See https://github.com/chef/cookstyle/blob/master/CHANGELOG.md for a complete list of newly enabled rules.
Berkshelf has been updated to 7.0.2. Berkshelf 7 moves to using the same libraries as the Chef Client, ensuring consistent behaviour - for instance, ensuring that chefignore files work the same - and enabling a quicker turnaround on bug fixes. The “Actor crashed” failures of celluloid will no longer be produced by Berkshelf.
The knife-vsphere plugin for managing VMware vSphere is now bundled with ChefDK.
chef cookbook generate [cookbook_name] now creates a CHANGELOG.md file.
chef-provisioning2.7.0 -> 2.7.1knife-ec20.17.0 -> 0.18.0opscode-pushy-client2.3.0 -> 2.4.11
Ruby has been updated to 2.5.1 to resolve the following vulnerabilities:
CVE-2017-17742: HTTP response splitting in WEBrickCVE-2018-6914: Unintentional file and directory creation with directory traversal in tempfile and tmpdirCVE-2018-8777: DoS by large request in WEBrickCVE-2018-8778: Buffer under-read in String#unpackCVE-2018-8779: Unintentional socket creation by poisoned NUL byte in UNIXServer and UNIXSocketCVE-2018-8780: Unintentional directory traversal by poisoned NUL byte in Dir- Multiple vulnerabilities in RubyGems
OpenSSL has been updated to 1.0.2o to resolve CVE-2018-0739.
The cookbook, recipe, and app generators now name the test directory integration instead of smoke.
ChefDK now ships with Chef 13.8.5. See https://docs.chef.io/release_notes.html for more information on what's new.
When running chef generate cookbook the generated cookbook will now specify a minimum chef release of 12.14 not 12.1.
Ruby has been updated to 2.4.3 to resolve CVE-2017-17405
OpenSSL has been updated to 1.0.2n to resolve CVE-2017-3738, CVE-2017-3737, CVE-2017-3736, and CVE-2017-3735.
LibXML2 has been updated to 2.9.7 to fix CVE-2017-15412
minitar has been updated to 0.6.1 to resolve CVE-2016-10173
chefspec7.1.2 -> 7.1.2chef-api0.7.1 -> 0.8.0chef-provisioning2.6.0 -> 2.7.0chef-provisioning-aws3.0.0 -> 3.0.2chef-sugar3.6.0 -> 4.0.0foodcritic12.2.1 -> 12.3.0inspec1.45.13 -> 1.51.21kitchen-dokken2.6.5 -> 2.6.7kitchen-ec21.3.2 -> 2.2.1kitchen-inspec0.20.0 -> 0.23.1kitchen-vagrant1.2.1 -> 1.3.1knife-ec20.16.0 -> 0.17.0knife-windows1.9.0 -> 1.9.1test-kitchen1.19.2 -> 1.20.0chef-provisioning-azurehas been removed as it used deprecated Azure APIs
Policyfile users who use a Chef Server as a cookbook source will experience faster cookbook downloads when running chef install. Chef Server's API requires each file in a cookbook to be downloaded separately; ChefDK will now download the files in parallel. Additionally, HTTP keepalives are enabled to reduce connection overhead.
Policyfile users may now source cookbooks from the Chef Server's cookbook artifact store. This is mainly intended to support the upcoming include_policy feature, but could be useful in some situations.
Given a cookbook that has been uploaded to the Chef Server via chef push, it can be used in another policy by adding code like the following to the ruby policyfile:
cookbook "runit",
chef_server_artifact: "https://chef.example/organizations/myorg",
identifier: "09d43fad354b3efcc5b5836fef5137131f60f974"
Policyfile maybe now use the include_policy directive as described in
RFC097.
This directive's purpose is to allow the inclusion policyfile locks to the current
policyfile. In this iteration, we support sourcing lock files from a local path or a
chef server. Below is a simple example of how the include_policy directive can be used.
Given a policyfile base.rb:
name 'base'
default_source :supermarket
run_list 'motd'
cookbook 'motd', '~> 0.6.0'
Run:
>> chef install ./base.rb
Building policy base
Expanded run list: recipe[motd]
Caching Cookbooks...
Using motd 0.6.4
Using chef_handler 3.0.2
Lockfile written to /home/jaym/workspace/chef-dk/base.lock.json
Policy revision id: 1238e7a353ec07a4df6636cdffd8805220a00789bace96d6d70268a4b0064023
This will produce the base.lock.json that will be included in our next policy users.rb:
name 'users'
default_source :supermarket
run_list 'user'
cookbook 'user', '~> 0.7.0'
include_policy 'base', path: './base.lock.json'
Run:
>> chef install ./users.rb
Building policy users
Expanded run list: recipe[motd::default], recipe[user]
Caching Cookbooks...
Using motd 0.6.4
Installing user 0.7.0
Using chef_handler 3.0.2
Lockfile written to /home/jaym/workspace/chef-dk/users.lock.json
Policy revision id: 20fac68f987152f62a2761e1cfc7f1dc29b598303bfb2d84a115557e2a4a8f27
This will produce a users.lock.json that has the base policyfile lock merged in.
More information can be found in RFC097 and the docs.
We are now shipping the following new tools as part of Chef-DK
- kitchen-digitalocean
- kitchen-google
- knife-ec2
- knife-google
The Chef Provisioning AWS gem has been updated from the Amazon AWS SDK V1 to V2. This includes a huge number of under the hood improvements and bug fixes.
- aws-sdk 2.10.45 -> 2.10.90
- chef 13.4.19 -> 13.6.4 (Changelog)
- chefspec 7.1.0 -> 7.1.1 (Changelog
- chef-provisioning 2.5.0 -> 2.6.0 (Changelog)
- chef-provisioning-aws 2.2.2 -> 3.0.0 (Changelog)
- chef-provisioning-fog 0.21.0 -> 0.26.0 (Changelog)
- chef-sugar 3.5.0 -> 3.6.0 (Changelog)
- fauxhai 5.3.0 -> 5.5.0 (Changelog)
- foodcritic 11.4.0 -> 12.2.1 (Changelog)
- inspec 1.36.1 -> 1.44.13 (Changelog)
- kitchen-digitalocean new @ 0.9.8
- kitchen-google new @ 1.4.0
- kitchen-inspec 0.19.0 -> 0.20.0 (Changelog)
- knife-ec2 new @ 0.16.0
- knife-google new @ 3.2.0
- knife-spork 1.6.3 -> 1.7.1 (Changelog)
- mixlib-install 2.1.12 -> 3.8.0 (Changelog)
- rspec 3.6.0 -> 3.7.0 (Changelog)
- serverspec 2.40.0 -> 2.41.3
- test-kitchen 1.17.0 -> 1.19.2 (Changelog)
- train 0.26.2 -> 0.29.2 (Changelog)
- winrm-fs 1.0.1 -> winrm-fs 1.1.1 (Changelog)
ChefDK 2.3 includes Ruby 2.4.2 to fix the following CVEs:
- CVE-2017-0898
- CVE-2017-10784
- CVE-2017-14033
- CVE-2017-14064
The 2.2.1 release includes RubyGems 2.6.13 to fix the following CVEs:
- CVE-2017-0899
- CVE-2017-0900
- CVE-2017-0901
- CVE-2017-0902
ChefDK 2.3 includes:
- Chef 13.4.19
- InSpec 1.36.1
- Berkshelf 6.3.1
- Chef Vault 3.3.0
- Foodcritic 11.4.0
- Test Kitchen 1.17.0
- Stove 6.0
We are now shipping stove in ChefDK, to aid users in uploading their cookbooks to supermarkets.
The cookbook generator now adds a LICENSE file when creating a new cookbook.
When chef generate cookbook is ran, boilerplate unit tests for the CentOS 7 platform are now generated as well.