-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Find and install box file for multi-provider boxes automatically #86
Conversation
Hi there, For such a small change it did a couple of things. First, it broke the specs....
But it also appears to have shown a mismatch somewhere in the boxen.
Not sure what to do with this. Sorry, |
Sorry for the tests, I'm fixing them now. Your second issue must be caused by upper-case "vSphere" word specified On Wednesday, August 27, 2014, Matt Savoie [email protected] wrote:
|
So I don't have access to the vsphere hypervisor, but only the code in this project. There is a vsphere.box file, but it's a binary file of some sort. Can you give me something to take to the Admins? Sorry for my ignorace on that side of the house, it certainly makes this hard for me to maintain. (also, this may end up waiting until next week as I'll be on vacation til Tuesday) Thanks |
What ignorance are you talking about? I have replies the same day, and a new release after each accepted pull request. Thank you! vsphere.box file needs to be be re-packed with a change from #87 as explained in https://github.com/nsidc/vagrant-vsphere#usage. This should fix the second issue. |
Here you are. |
I'm following up with my box provider now. I'll let you know what I hear |
That's a simple change with a quite long explanation.
I develop multi-provider boxes, and publish them on private Vagrant cloud server.
For that I need to put all vSphere connection settings into "dummy box" file, which is published on the server.
Actual Vagrantfiles inherit these settings, and do not set them explicitly.
The setup works fine, with one exception: on each new machine
vagrant up
fails with errors likeConfiguration must specify a vSphere host
. This happens because dummy box files are not downloaded yet, and vSphere connections settings are nowhere defined. I have to explicitly usevagrant box add
command to download the box file from the server.This pull request fixes the whole issue. It forces Vagrant to check whether required box file for this particular provider is installed, and if not then downloads and installs it automatically.