From d086d6d775f2b000556a32f7c86f1db6868e7f0e Mon Sep 17 00:00:00 2001 From: Anthony Scalisi Date: Tue, 10 Dec 2013 10:47:39 -0800 Subject: [PATCH] mention chef.delete_node and chef.delete_client methods in the DOCS --- .../source/v2/provisioning/chef_client.html.md | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/website/docs/source/v2/provisioning/chef_client.html.md b/website/docs/source/v2/provisioning/chef_client.html.md index 6ef1831c5..60a201d2a 100644 --- a/website/docs/source/v2/provisioning/chef_client.html.md +++ b/website/docs/source/v2/provisioning/chef_client.html.md @@ -92,9 +92,17 @@ of these variables: When you provision your Vagrant virtual machine with Chef server, it creates a new Chef "node" entry and Chef "client" entry on the Chef server, using the -hostname of the machine. After you tear down your guest machine, you must -explicitly delete these entries from the Chef server before you provision -a new one with Chef server. For example, using Chef's built-in `knife` tool: +hostname of the machine. After you tear down your guest machine, Vagrant can be +configured to do it automatically with the following settings: + +```ruby +chef.delete_node = true +chef.delete_client = true +``` + +If you don't specify it or set it to `false`, you must explicitly delete these +entries from the Chef server before you provision a new one with Chef server. +For example, using Chef's built-in `knife` tool: ``` $ knife node delete precise64