chef-provisioning-vagrant
chef-provisioning-vagrant copied to clipboard
chef-boneyard
Vagrant provisioner for chef-provisioning
If I include a vm.synced_folder setting in vagrant_options, then the resulting vagrant file is invalid, which causes vagrant up to fail. ## Example: The following recipe: ``` options = {...
Does this driver support policy files? Here's what I tried: ``` ruby options = { vagrant_options: { 'vm.box' => 'opscode-centos-7.2', 'vm.network' => [ ':forwarded_port, guest: 443, host: 443' ] },...
I had to remove the indent on the closing EOF in order to avoid this error: > syntax error, unexpected end-of-input, expecting tSTRING_CONTENT or tSTRING_DBEG or tSTRING_DVAR or tSTRING_END
Hi, I have the following code which cannot converge because `the Vagrantfile is not correct` on the second convergence. ``` my_machine_options_for_virtualbox = ------------ > vagrant reload my-machine failed! > STDOUT:...
When I run this code: ``` require 'chef/provisioning/vagrant_driver' with_driver 'vagrant' vagrant_box 'opscode-centos-6.5' do url 'http://opscode-vm-bento.s3.amazonaws.com/vagrant/vmware/opscode_centos-6.5_chef-provisionerless.box' vagrant_provider 'vmware_desktop' end ``` I get this error: ``` ================================================================================ Error executing action `create` on...
When converging a Windows machine with the chef-provisioning-vagrant driver with WinRM transport I get an error: `wrong number of arguments (3 for 4)` Looks like [this line](https://github.com/chef/chef-provisioning-vagrant/blob/70b6581d7f238d0933e3f3418dcaa851372d573b/lib/chef/provisioning/vagrant_driver/driver.rb#L418) is missing a...
We have a requirement to specify multiple vm.network settings in our vagrant_options. For example, setting a private network IP address, as well as setting a forwarded port. ### Setting up...
When I tried to use `machine_image` with vagrant driver, after successful converging I got `Chef::Provisioning::VagrantDriver::Driver does not implement create_image` error. So I suppose it's impossible to build an actual vagrant...
This is bad, mmmkay Unit tests plus integration tests that assert the correct shell-out commands are invoked would be nice.
