41 lines
2.0 KiB
Markdown
41 lines
2.0 KiB
Markdown
## 0.5.2 (unreleased)
|
|
|
|
- `vagrant up` can be used as a way to resume the VM as well (same as
|
|
`vagrant resume`). [GH-134]
|
|
- Sudo uses "-E" flag to preserve environment for chef provisioners.
|
|
This fixes issues with CentOS. [GH-133]
|
|
- Added "IdentitiesOnly yes" to options when `vagrant ssh` is run to
|
|
avoid "Too Many Authentication Failures" error. [GH-131]
|
|
- Fix regression with `package` not working. [GH-132]
|
|
- Added ability to specify box url in `init`, which populates the
|
|
Vagrantfile with the proper `config.vm.box_url`.
|
|
|
|
## 0.5.1 (July 31, 2010)
|
|
|
|
- Allow specifying cookbook paths which exist only on the VM in `config.chef.cookbooks_path`.
|
|
This is used for specifying cookbook paths when `config.chef.recipe_url` is used. [GH-130]
|
|
See updated chef solo documentation for more information on this.
|
|
- No longer show "Disabling host only networks..." if no host only networks
|
|
are destroyed. Quiets `destroy`, `halt`, etc output a bit.
|
|
- Updated getting started guide to be more up to date and generic. [GH-125]
|
|
- Fixed error with doing a `vagrant up` when no Vagrantfile existed. [GH-128]
|
|
- Fixed NFS erroring when NFS wasn't even enabled if `/etc/exports` doesn't
|
|
exist. [GH-126]
|
|
- Fixed `vagrant resume` to properly resume a suspended VM. [GH-122]
|
|
- Fixed `halt`, `destroy`, `reload` to where they failed if the VM was
|
|
in a saved state. [GH-123]
|
|
- Added `config.chef.recipe_url` which allows you to specify a URL to
|
|
a gzipped tar file for chef solo to download cookbooks. See the
|
|
[chef-solo docs](http://wiki.opscode.com/display/chef/Chef+Solo#ChefSolo-RunningfromaURL) for more information.
|
|
[GH-121]
|
|
- Added `vagrant box repackage` which repackages boxes which have
|
|
been added. This is useful in case you want to redistribute a base
|
|
box you have but may have lost the actual "box" file. [GH-120]
|
|
|
|
## Previous
|
|
|
|
The changelog began with version 0.5.1 so any changes prior to that
|
|
can be seen by checking the tagged releases and reading git commit
|
|
messages.
|
|
|