Skip to content
This repository has been archived by the owner on Jun 25, 2023. It is now read-only.

Rename VMware Fusion support to VMware Desktop #358

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

nickcharlton
Copy link

On 2016-03-26, HashiCorp released the VMware Desktop Plugin, which
replaced the existing VMware Fusion implementation. With the rename, the
hooks that Landrush needs to start services can no longer be called.
Renaming those makes those work again.

Fixes #334.

On 2016-03-26, HashiCorp released the VMware Desktop Plugin, which
replaced the existing VMware Fusion implementation. With the rename, the
hooks that Landrush needs to start services can no longer be called.
Renaming those makes those work again.

Fixes vagrant-landrush#334.
@davividal
Copy link
Collaborator

I can't test this.
But the tests passed, so I believe. :)

@nickcharlton
Copy link
Author

I would've liked to have tested my changes too, but I couldn't work out how to do it. Running it locally, I found I wasn't able to run the tests for Landrush whilst having the (private) VMware provider plugin installed.

I don't suppose you have any suggestions?

@davividal
Copy link
Collaborator

I never used VMware + Vagrant, so no.

This attempts to document the need for the new plugin model, which
should be enough to prompt anyone upgrading to know that they need it.

https://www.hashicorp.com/blog/introducing-the-vagrant-vmware-desktop-plugin/
@davividal
Copy link
Collaborator

@hferentschik this one looks fine for me.
What do you think?

@nickcharlton
Copy link
Author

I'm conscious that this has been sat a little while without any activity. Is there anything I can help with to move this along?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Landrush doesn't start with Vagrant 2.2.0 on VMWare Fusion
2 participants