Vagrant v0.6.0 Release Notes

Release Date: 2010-09-27 // over 13 years ago
    • VM name now defaults to the name of the containing folder, plus a timestamp. This should make it easier to identify VMs in the VirtualBox GUI.
    • Exposed Vagrant test helpers in Vagrant::TestHelpers for plugins to easily test themselves against Vagrant environments.
    • Plugins have landed. Plugins are simply gems which have a vagrant_init.rb file somewhere in their load path. Please read the documentation on vagrantup.com before attempting to create a plugin (which is very easy) for more information on how it all works and also some guidelines.
    • vagrant package now takes a --vagrantfile option to specify a Vagrantfile to package. The --include approach for including a Vagrantfile no longer works (previously built boxes will continue to work).
    • vagrant package has new logic with regards to the --include option depending on if the file path is relative or absolute (they can be intermixed):
      • Relative paths are copied directly into the box, preserving their path. So --include lib/foo would be in the box as "lib/foo"
      • Absolute paths are simply copied files into the root of the box. So --include /lib/foo would be in the box as "foo"
    • "vagrant_main" is no longer the default run list. Instead, chef run list starts empty. It is up to you to specify all recipes in the Vagrantfile now.
    • Fixed various issues with certain action middleware not working if the VM was not created.
    • SSH connection is retried 5 times if there is a connection refused. Related to GH-140.
    • If http_proxy environmental variable is set, it will be used as the proxy box adding via http.
    • Remove config.ssh.password. It hasn't been used for a few versions now and was only kept around to avoid exceptions in Vagrantfiles.
    • Configuration is now validated so improper input can be found in Vagrantfiles.
    • Fixed issue with not detecting Vagrantfile at root directory ("/").
    • Vagrant now gives a nice error message if there is a syntax error in any Vagrantfile. [GH-154]
    • The format of the ".vagrant" file which stores persisted VMs has changed. This is backwards incompatible. Will provide an upgrade utility prior to 0.6 launch.
    • Every [expected] Vagrant error now exits with a clean error message and a unique exit status, and raises a unique exception (if you're scripting Vagrant).
    • Added I18n gem dependency for pulling strings into clean YML files. Vagrant is now localizable as a side effect! Translations welcome.
    • Fixed issue with "Waiting for cleanup" message appearing twice in some cases. [GH-145]
    • Converted CLI to use Thor. As a tradeoff, there are some backwards incompatibilities:
      • vagrant package - The --include flag now separates filenames by spaces, instead of by commas. e.g. vagrant package --include x y z
      • vagrant ssh - If you specify a command to execute using the --execute flag, you may now only specify one command (before you were able to specify an arbitrary amount). e.g. vagrant ssh -e "echo hello"
      • vagrant ssh-config has become vagrant ssh_config due to a limitation in Thor.