- From: Jamie Winsor <
>
- To:
- Subject: [chef] Berkshelf 1.3.1 with Vagrant 1.1 support
- Date: Wed, 20 Mar 2013 13:46:58 -0700
Hey Chefs,
Today we released Berkshelf 1.3.1 which includes Vagrant 1.1 support. Vagrant is no longer distributed as a Rubygem so there are some additional things to consider when upgrading.
- Vagrant is no longer installed with ruby gems. Grab a copy of the latest version's installer from their download page.
- Berkshelf core no longer ships with the Berkshelf plugin. There is a new gem which contains the berkshelf-vagrant plugin.
- Install this plugin with the command `vagrant plugin install berkshelf-vagrant` once you have Vagrant installed.
- You no longer require 'berkshelf/vagrant' at the top of your Vagrantfile to include the Berkshelf plugin; it's just automatically loaded now.
- The Vagrantfile format generated by Berkshelf 1.0-1.2 is no longer, valid. You can generate a new Vagrantfile by renaming your cookbook's current Vagrantfile and re-running `berks init`. Diff the two files and make the appropriate changes; there shouldn't be too many.
Berkshelf 1.3.1 and the Berkshelf-Vagrant plugin do not support Vagrant 1.0.x. See the
CHANGELOG for extra details on this release.
And please, open a ticket with us if you have an issue!
--
Jamie Winsor
@resetexistence
https://github.com/reset
- [chef] Berkshelf 1.3.1 with Vagrant 1.1 support, Jamie Winsor, 03/20/2013
Archive powered by MHonArc 2.6.16.