I am trying to create a vagrant box that launches a cluster of 3 VMs. The Vagrantfile to accomplish this works when this definition is in the Vagrantfile in the CWD. However, when I move this multi-machine definition to the embedded Vagrantfile, vagrant ignores it and creates a default VM, ignoring the named machine definitions.
I read the documentation, which doesn’t say anything concrete about this, only that multiple Vagrantfiles are merged before starting a vagrant box, and that some definitions in the Vagrantfile are added, and some do overwrite, which is not very descriptive. My first question is if this is intended behaviour. My second question is if there’s way to make vagrant execute a multi-machine setup with the definition in the embedded Vagrantfile, so that a user can use a simple default generated Vagrantfile. -- 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/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- 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 vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2f2ecef8-a895-4b80-80a1-65aa6dc29f23n%40googlegroups.com.
