Here's my shot at adding support for Parallels Desktop (specifically, the vagrant-parallels provider.
Three main things have happened here:
Reorganized the way Vlad handles provider-specific configuration. Instead of the not-always-most-optimal method of parsing command line arguments to figure out the provider, we simply use Vagrant's override argument (abbreviated to o). This works the same (better, actually) than what Vlad was doing before. The problem this fixes is Vlad forgetting the proper box when using vagrant reload without VAGRANT_DEFAULT_PROVIDER set.
Added a provider-specific configuration block for parallels.
Added a setting (default false) for whether the Parallels Desktop guest tools should be updated or not. Since vagrant-vbguest handles this itself without configuration, and I have no idea what VMware does, I special-cased this to Parallels.
Tested for Parallels but should probably have the tires re-kicked with VirtualBox/VMware as well.
Here's my shot at adding support for Parallels Desktop (specifically, the
vagrant-parallels
provider.Three main things have happened here:
override
argument (abbreviated too
). This works the same (better, actually) than what Vlad was doing before. The problem this fixes is Vlad forgetting the proper box when usingvagrant reload
withoutVAGRANT_DEFAULT_PROVIDER
set.parallels
.false
) for whether the Parallels Desktop guest tools should be updated or not. Sincevagrant-vbguest
handles this itself without configuration, and I have no idea what VMware does, I special-cased this to Parallels.Tested for Parallels but should probably have the tires re-kicked with VirtualBox/VMware as well.