vagrant-berkshelf | Vagrant plugin to add Berkshelf integration | Plugin library

I have had a number of issues recently with vagrant-berkshelf not syncing Chef cookbooks on an existing machine reliably. And, basically, when doing research on workarounds, I see something like:

vagrant-berkshelf is deprecated, use Test Kitchen instead.

My use case is that I have Vagrantfiles, used to build VMs and DigitalOcean droplets, that are hand-written and only use Chef to provision the VMs. I am most definitely approaching Chef as a user, not an author or tester of cookbooks.

So, I am in a case of Vagrant -> Chef, not Chef -> Vagrant.

When looking at Kitche-Vagrant, I see that:

The kitchen-vagrant driver for Kitchen generates a single Vagrantfile for each instance of Kitchen in a sandboxed directory..

My question is: if my workflow relies on hand-written, complex, Vagrantfiles, can I continue to use Chef as a provisioner without having to rely on vagrant-berkshelf?

Some of the possible alternatives I see are:

• mangle Test Kitchen configuration to work with my exiting Vagrantfile. I fear that this is not the intent of this tool and will not end well.

• use chef.cookbooks_path attribute in vagrant and let it take the place of vagrant-berkshelf.

• switch out provisioners and use say Vagrant->Ansible.

The Vagrantfile below is somewhat simplified, but the gist is that the Vagrantfile is in charge and Chef is just used to provision.

Within the following code's creates directive, the specified value contains a (actually, more than one) wildcard.

TL:DR; How does one import the chef-manage ssl certificate into chromium/firefox? Is /var/opt/opscode/nginx/ca/[fqdn].crt the appropriate file?

I'm generating a chef-server machine using vagrant, vagrant-berkshelf, and the chef-server supermarket cookbook. Once complete, I'm running chef-server-ctl install chef-manage chef-server-ctl reconfigure chef-manage-ctl reconfigure ...in order to install and setup the chef-manage addon. With the addon installed, I attempt to import the generated certificate at /var/opt/opscode/nginx/ca/[fqdn].crt into the browser (chromium/firefox) through the browser's certificate management interface, but I receive the following error(s):

Chromium:

Certificate Import Error Invalid or corrupt file.

Firefox:

This personal certificate can’t be installed because you do not own the corresponding private key which was created when the certificate was requested.

The file looks like a ssh public key but with "BEGIN / END CERTIFICATE" instead of "BEGIN / END RSA PUBLIC KEY". The format and content of the cert seems correct.

Any tips, hints, or suggestions would be greatly appreciated!

• K.E.

I want to spin up a Vagrant box and provision a LAMP stack using chef-solo and berkshelf. Here's the steps I take: