If the code works when you move the ENV and systems definitions inside the Vagrantfile, you’re probably having issues with variable scope. When you define a module it hides all the variables inside it from the outside world.
Unless you need to run Ruby code in your config, maybe it would be better to define your configuration in some kind of text format, like YAML, then you can import that in the Vagrantfile and use it like an object. I’m not a Ruby programmer by any stretch, but a quick Google search made it look like the YAML module would be easy to use. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/5b03e094-c3e6-4858-b61a-610ffadd3852%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
