[chef] Re: Re: Re: Delete node and client when destroying Vagrant VM

["steve ." < >]

I seem to recall someone from Opscode steering people away from making direct calls using Chef's internal REST client for some reason.  I'd do it through the Knife object, something like (untested code alert):

Chef::Knife::ClientDelete.run(env[:vm].config.vm.host_name)

On Thu, Dec 6, 2012 at 7:48 AM, Cassiano Leal < " target="_blank"> > wrote:

Nice one.

Just one correction to my original post, the link to my gist is https://gist.github.com/4223941 and not the one I sent before (that was a reference).

I like your REST approach, though, and will certainly have a look at that.

Thanks,

-- 

Cassiano Leal

On Thursday, December 6, 2012 at 12:04, Jesse Nelson wrote:

meant to say "no subshell" not "syscall" 

On Thu, Dec 6, 2012 at 11:04 PM, Jesse Nelson < " target="_blank"> > wrote:

You can check out the code in my chef-sandbox  that does this using the vagrant provisioner class and chef client code directly (no syscall:

  https://github.com/spheromak/chef-sandbox/blob/develop/Vagrantfile#L52-L96

Change:

::Chef::Config.from_file(File.join( File.dirname(__FILE__), 'chef', 'knife.rb'))

To point to your knife.rb location.

Pop the rest in your vagrant file, and you should be good.

On Thu, Dec 6, 2012 at 9:03 PM, Cassiano Leal < " target="_blank"> > wrote:

I was trying to find a solution for that on the web, and the two references that made more sense were:

http://frank.be/articles/2011/12/16/vagrant-and-chef-auto-deregister-on-vm-destroy/

https://gist.github.com/1010660

Neither worked out of the box, so I hacked my own solution, adapting a bit from each, and came to this:

https://gist.github.com/1010660

Feel free to use it if you find it useful. Comments and suggestions are welcome.

Cheers!

-- 

Cassiano Leal