-
Notifications
You must be signed in to change notification settings - Fork 12
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
Error occurred: no implicit conversion of nil into String #36
Comments
Same issue with 0.3.0:
|
@jantman I know you fixed this similar error back in 0.2.0 but maybe it's back? |
The issue come from this: https://github.com/jantman/vagrant-r10k/blob/master/lib/vagrant-r10k/helpers.rb#L107 With the changes made to the puppet apply provisioner in vagrant for Puppet 4, the The workaround for now is to explicitly specify the |
Ah, ok. I actually haven't used this plugin with puppet4 yet. @trlinkin thanks for spotting that and suggesting the workaround. I'm going to need some time to dig into this and try to figure out the best fix, but I'm not sure I'll be able to get to it until tomorrow night. @cdenneen If the workaround of explicitly specifying |
Um... this looks like a bit of an oops on my part. r10k doesn't need to know about the manifest file. In fact, as far as I can tell, the |
@trlinkin @cdenneen 0.4.1 is released and pushed to rubygems. Could someone please update the plugin and verify that things now work, without the workaround? I've documented example puppet4 use in the readme: https://github.com/jantman/vagrant-r10k/blob/master/README.md#usage-with-puppet4-environment-based-provisioner |
Vagrantfile
vagrant debug output:
The text was updated successfully, but these errors were encountered: