I’m not sure if this will work, but have you tried to stick ‘path “/path/to/cookbooks”’ at the top of the Berksfile?On Monday, November 25, 2013 at 14:53, Rob Watkin wrote:
I was just trying to be able to create new local cookbooks in a dev environmentOn 25 November 2013 16:44, Nic Grayson < " target="_blank"> > wrote:
The idea behind Berkshelf is that you shouldn't use your local cookbooks. You should pull them from git, a chef api, opscode, etc. Setup Berkshelf to pull from the default location where they are and berks install.On Mon, Nov 25, 2013 at 10:15 AM, Andy Gale < " target="_blank"> > wrote:On Mon, Nov 25, 2013 at 4:12 PM, Rob Watkin < " target="_blank"> > wrote:I think that the plugin overrides the cookbook_path variable so "no"
>
> Thanks for your help. I just changed the Berksfile as shown below and it
> works fine. Is there anyway I can get all my local cookbooks scanned without
> explicitly naming them?
is the answer. From http://berkshelf.com/
"Chef Solo provisioner
The Chef Solo provisioner’s cookbook_path attribute is hijacked when
using the Vagrant Berkshelf plugin. Cookbooks resolved from your
Berksfile will automatically be made available to your Vagrant virtual
machine. There is no need to explicitly set a value for cookbook_path
attribute."
--
Andy Gale
http://andy-gale.com
http://twitter.com/andygale
Archive powered by MHonArc 2.6.16.