We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Vagrantfile rendered by the init command should set up Berkshelf support by default. This means:
gem "berkshelf"
require 'berkshelf/vagrant'
source :opscode metadata group :test do cookbook "apt" cookbook "yum" cookbook "minitest-handler" require 'pathname' cb_dir = ::File.join('.', 'test', 'kitchen', 'cookbooks') if ::File.exist?(cb_dir) Pathname.new(cb_dir).children.select(&:directory?).each do |c| cookbook c.basename.to_s, :path => ::File.join(cb_dir, c.basename.to_s).to_s end end end
The last part is to support #24.
A command-line option could be added to disable Berkshelf support, or switch to librarian-chef.
The text was updated successfully, but these errors were encountered:
We don't need the Gemfile/Vagrantfile integration. A "--create-berksfile" for Berkshelf would still be nice.
Sorry, something went wrong.
This is resolved with existing auto-detection magic.
No branches or pull requests
The Vagrantfile rendered by the init command should set up Berkshelf support by default. This means:
gem "berkshelf"
to Gemfilerequire 'berkshelf/vagrant'
to VagrantfileThe last part is to support #24.
A command-line option could be added to disable Berkshelf support, or switch to librarian-chef.
The text was updated successfully, but these errors were encountered: