There are several talks & slides talking about multi-provider Vagrant boxes but the documentation doesn't have the kind of depth that I need at this time so I thought I'd bring it to the community. I'll give you some background on what my process is and where we want to go with this:
1. Use packer to build the base ami and virtualbox OVA machines. 2. Run that through some shell provisioners. 3. Chunk both through the Vagrant post-processor and get two Vagrant boxes. 4. Make something happen. Step 4 is proving to be elusive. The post processor gives me (when I manually unpackage teh boxes) a Vagrantfile with provider specific settings and the metadata.json file (that is generated). What I would like to do is combine these two boxes into one uber box to distribute. I can manually add both boxes with the same name and launch vagrant init BOX_NAME then vagrant up --provider=PROVIDER_NAME successfully but I'd love to put both provider configs in the same Vagrantfile. So, here's the questions I have: A) Can one .box have one Vagrantfile with mutilple providers? B) If so, how is the metadata.json file structured to handle both provisioners? C) If so, for Vagrant 1.5, how does the box metadata (for versioning) look in multi-provider? OR Do I just make two different boxes, modify their Vagrantfiles to add more config info, and just continue with adding them with the same name but different --provider flags? -- 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]. For more options, visit https://groups.google.com/d/optout.
