If you're using Vagrant with the Chef-Client provisioner it creates a client and a node on the Chef server when the VM spins up.
This plugin will automatically get rid of that cruft for you when you destroy the VM.
Install this plugin using the Vagrant command line:
$ vagrant plugin install vagrant-butcher
The plugin is loaded automatically once installed.
For most cases, the plugin shouldn't need any configuration. However, there are a few options that can be set. The options are all set in the
Vagrantfile in the format:
Vagrant.configure("2") do |config| ... config.butcher.<option> = <value> ... end
||Location of the client key in the guest VM|
||If set to false, does not verify Chef's host key|
||Inform the URL of a proxy server between your host and the Chef Server|
||Guest's node name||Inform a client name to override the plugin's default behaviour|
||Guest's client key||Point to a local
- So far this has only been tested and confirmed to run with the VirtualBox and Rackspace provisioners. It should work with others, but if you run into issues please file a bug.
- The default
/vagrantshared folder should be mounted.
verify_sslis enabled by default. You might want to disable that if, for example, you run your own Chef server with a self-signed cert. Check here to see how.
- Removed compatibility with Vagrant < 1.5
- Fixes an issue with recent Vagrant versions where the butcher sequence would never run
- Sets default
guest_key_pathdepending on OS
- Tested and confirmed working on Windows and Linux
- No more option to point to
knife.rb. Data is retrieved from the
chefis no longer a requirement (no more
- Configuration items were added to point to custom client name and key
- It's possible to disable the plugin by setting the
falsein the Vagrantfile.
See Configuration for all possible customisations.
- :auto was added as an optional value for knife_config_file
- Support for Vagrant 1.2
- Support for Vagrant 1.x (it's been tested on 1.1.4, but should work on previous minor releases) -- if you're using a pre-1.0 Vagrant release, stick to vagrant-butcher 0.0.3.
- Configuration change.
- Installation via
- Provider-independent. Read more
- Uses chef.node_name if set. Otherwise, fall back to vm.host_name (as before), or vm.box. -- Kudos to pikesley.
- Fork it
- Create your feature branch (
git checkout -b my-new-feature)
- Commit your changes (
git commit -am 'Add some feature')
- Push to the branch (
git push origin my-new-feature)
- Create new Pull Request