haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #2627 from scalp42/chef_delete 

website/docs: mention chef.delete_node and chef.delete_client methods
This commit is contained in:
Mitchell Hashimoto 2013-12-10 18:02:50 -08:00
parent 70b662e307 d086d6d775
commit 306248db9c
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/docs/source/v2/provisioning/chef_client.html.md
View File

@ -92,9 +92,17 @@ of these variables:
When you provision your Vagrant virtual machine with Chef server, it creates a 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 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 hostname of the machine. After you tear down your guest machine, Vagrant can be
explicitly delete these entries from the Chef server before you provision configured to do it automatically with the following settings:
a new one with Chef server. For example, using Chef's built-in `knife` tool:
```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 $ knife node delete precise64