vagrant/test/unit
Mitchell Hashimoto 7a299ae2de Configuration loader can handle upgrading.
The basic process for this is to:

1. Load the configuration using the proper loader for that version. i.e.
   if you're loading V1 config, then use the V1 loader.
2. If we just loaded a version that isn't current (imagine we're
   currently at V3), then we need to upgrade that config. So we first
   ask the V2 loader to upgrade the V1 config to V2, then we ask the V3
   loader to upgrade the V2 config to V3. We keep track of warnings and
   errors throughout this process.
3. Finally, we have a current config, so we merge it into the in-process
   configuration that is being loaded.
2012-06-23 19:56:31 -07:00
..
support Even with a custom vagrantfile name, use defaults [GH-778] 2012-03-08 13:24:04 -08:00
vagrant Configuration loader can handle upgrading. 2012-06-23 19:56:31 -07:00
base.rb Clean up test load paths 2011-12-11 15:53:11 -08:00
vagrant_test.rb Vagrant.require_plugin [GH-916] 2012-05-06 14:01:10 -07:00