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
Empty puppet_version gives error. #38
Comments
Same issue here... |
+1 Im hitting this issue too, when the install url is not set, the vagrant box crashes out:
Can we please get a hot fix for this issue when you guys have the time? Otherwise, I will need to specific a puppet version & Install for all my Vagrant builds or remove the plugin utterly, which I defiantly do not want to do since this plugin is utterly amazing! Keep up the great works guy and thanks so much for all the effort that has gone into this plugin! |
Hi everyone! So most of the trouble seems to come from the code in #28, which seems to have started this whole thing. If the version isn't set, then it seems to always set it to latest. I don't have the time to properly investigate it now, so I'm just going to remove it. In my tests, after that everything works fine for vagrant setups without the version or install url set. Since this is a breaking change, I'll bump the version number to 4.0.0. I should be able to get that done by EOD today, and I'll add an acceptance test to catch this in the future! 😄 |
This should be fixed by the 4.0.0 release, please say if it's not! 👍 |
I confirm that works for me. |
I am still getting an error with vagrant-puppet-install >=3.x installed and puppet_version is not set. This is after the fix in #36.
vagrant 1.8.1
VirtualBox 5.0.12
OS X Yosemite 10.10.5
The text was updated successfully, but these errors were encountered: