vagrant-butcher 0.0.1

data/.gitignore

@@ -0,0 +1,17 @@
+*.gem
+*.rbc
+.bundle
+.config
+.yardoc
+Gemfile.lock
+InstalledFiles
+_yardoc
+coverage
+doc/
+lib/bundler/man
+pkg
+rdoc
+spec/reports
+test/tmp
+test/version_tmp
+tmp

data/Gemfile

@@ -0,0 +1,4 @@
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in vagrant-butcher.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,22 @@
+Copyright (c) 2012 Cassiano Leal
+
+MIT License
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.md

@@ -0,0 +1,51 @@
+# Vagrant::Butcher
+
+If you're using Vagrant with the Chef-Client provisioner, e.g. for creating cookbooks, it creates a client and a node on the Chef server. Once you destroy the VM, both the client and node will be kept on the server, which may cause problems if you fire up the same VM again.
+
+This gem attempts to correct that.
+
+## Installation
+
+Installation will depend on whether you're using bundler or not.
+
+### If you're using Bundler
+
+Add this line to your application's Gemfile:
+
+    gem 'vagrant-butcher'
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install vagrant-butcher
+
+### If you're not using bundler
+
+You have to install this plugin via Vagrant:
+
+    $ vagrant gem 'vagrant-butcher'
+
+Explanation for that is found on the [Vagrant Plugins Documentation](http://vagrantup.com/v1/docs/extending/types.html)
+
+## Usage
+
+The plugin is loaded automatically once installed.
+
+By default, the gem looks for `$HOME/.chef/knife.rb` for the Chef server settings. This setting can be overrdidden by setting:
+
+    Vagrant::Config.run do |config|
+      config.vm.provision :chef_solo do |chef|
+        chef.knife_config = '/path/to/knife.rb'
+      end
+    end
+
+## Contributing
+
+1. Fork it
+2. Create your feature branch (`git checkout -b my-new-feature`)
+3. Commit your changes (`git commit -am 'Add some feature'`)
+4. Push to the branch (`git push origin my-new-feature`)
+5. Create new Pull Request

data/Rakefile

@@ -0,0 +1 @@
+require "bundler/gem_tasks"

data/lib/vagrant-butcher.rb

@@ -0,0 +1,4 @@
+require "vagrant/provisioners/chef"
+require "vagrant-butcher/version"
+require "vagrant-butcher/cleanup"
+require "chef"

data/lib/vagrant-butcher/cleanup.rb

@@ -0,0 +1,27 @@
+module Vagrant
+  module Provisioners
+    class ChefClient < Chef
+      class Config < Chef::Config
+        attr_accessor :knife_config
+        def knife_config; @knife_config || "#{ENV['HOME']}/.chef/knife.rb"; end
+      end
+
+      def cleanup_chef_server(host_name)
+        env[:ui].info "Removing node and client \"#{host_name}\" from Chef server"
+        [::Chef::Node, ::Chef::ApiClient].each do |chef_resource|
+          begin
+            chef_resource = chef_resource.load(host_name)
+            chef_resource.destroy
+          rescue Exception => e
+            env[:ui].warn "Could not destroy #{chef_resource} #{host_name}: #{e.message}"
+          end
+        end
+      end
+
+      def cleanup
+        ::Chef::Config.from_file(config.knife_config)
+        cleanup_chef_server(env[:vm].config.vm.host_name)
+      end
+    end
+  end
+end

data/lib/vagrant-butcher/version.rb

@@ -0,0 +1,5 @@
+module Vagrant
+  module Butcher
+    VERSION = "0.0.1"
+  end
+end

data/lib/vagrant_init.rb

@@ -0,0 +1,3 @@
+# This file is automatically loaded by Vagrant. We use this to kick-start
+# our plugin.
+require 'vagrant-butcher'

data/vagrant-butcher.gemspec

@@ -0,0 +1,22 @@
+# -*- encoding: utf-8 -*-
+lib = File.expand_path('../lib', __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require 'vagrant-butcher/version'
+
+Gem::Specification.new do |gem|
+  gem.name          = "vagrant-butcher"
+  gem.version       = Vagrant::Butcher::VERSION
+  gem.authors       = ["Cassiano Leal"]
+  gem.email         = ["cassianoleal@gmail.com"]
+  gem.description   = %q{Delete Chef client and node when destroying Vagrant VM}
+  gem.summary       = %q{When a Vagrant VM that was spun up using Chef-Client is destroyed, it leaves behind a client and a node on the Chef server. What butcher does is to clean up those during the destroy operation.}
+  gem.homepage      = "https://github.com/cassianoleal/vagrant-butcher"
+
+  gem.files         = `git ls-files`.split($/)
+  gem.executables   = gem.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
+  gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
+  gem.require_paths = ["lib"]
+  
+  gem.add_dependency "vagrant", "~> 1.0"
+  gem.add_dependency "chef"
+end

metadata

@@ -0,0 +1,90 @@
+--- !ruby/object:Gem::Specification
+name: vagrant-butcher
+version: !ruby/object:Gem::Version
+  version: 0.0.1
+  prerelease: 
+platform: ruby
+authors:
+- Cassiano Leal
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2012-12-17 00:00:00.000000000 Z
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: vagrant
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ~>
+      - !ruby/object:Gem::Version
+        version: '1.0'
+- !ruby/object:Gem::Dependency
+  name: chef
+  requirement: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+description: Delete Chef client and node when destroying Vagrant VM
+email:
+- cassianoleal@gmail.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- .gitignore
+- Gemfile
+- LICENSE.txt
+- README.md
+- Rakefile
+- lib/vagrant-butcher.rb
+- lib/vagrant-butcher/cleanup.rb
+- lib/vagrant-butcher/version.rb
+- lib/vagrant_init.rb
+- vagrant-butcher.gemspec
+homepage: https://github.com/cassianoleal/vagrant-butcher
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: '0'
+requirements: []
+rubyforge_project: 
+rubygems_version: 1.8.23
+signing_key: 
+specification_version: 3
+summary: When a Vagrant VM that was spun up using Chef-Client is destroyed, it leaves
+  behind a client and a node on the Chef server. What butcher does is to clean up
+  those during the destroy operation.
+test_files: []
+has_rdoc: