vagrant-digitalocean | Vagrant provider plugin that manages DigitalOcean droplets | 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.