The 'chef generate' subcommand now has the '--generator-cookbook' option to let you
specify a path to an alternate skeleton cookbook for generating cookbooks. For an
example, look at 'lib/chef-dk/skeletons' which is the default if this option
is not specified. Your cookbook will need to be named code_generator in order
for the recipes to be run.
The 'chef exec' subcommand added to execute commands with the PATH and ruby environment of the chefdk omnibus environment (analogous to 'bundle exec').
Berkshelf is updated to 3.1.1. (Berkshelf Changelog)
ChefDK changes for Berkshelf 3.1.1:
ChefDK now includes the kitchen-vagrant driver by default. Other
drivers can be installed via chef gem. Additionally, Test Kitchen has
been updated to install drivers to the embedded ruby when using kitchen init.
Runs a set of smoke tests by default; Can independently run smoke, unit and/or integration tests.
Gems now install in "user" mode by default, and are installed to
~/.chefdk/gem. Executables will be installed to
~/.chefdk/gem/ruby/2.1.0/bin. See the notes on the README
for more information about updating your environment to use ChefDK as
your primary Ruby development environment.
The README now has basic usage instructions for the chef command line
tool and documents how it interacts (or doesn't) with other Ruby
development tools.
chef-vault is now a part of the default package.