reorder chef_environment alphabetically

This commit is contained in:
cfortier2 2014-05-21 13:34:12 -04:00
parent fe743f96c7
commit bf38fa9f4f
1 changed files with 3 additions and 3 deletions

View File

@ -33,6 +33,9 @@ The reference of available configuration options is listed below. No
configuration is actually required, but `node_name` is recommended configuration is actually required, but `node_name` is recommended
since it will allow the provisioner to clean up the node/client. since it will allow the provisioner to clean up the node/client.
* `chef_environment` (string) - The name of the chef_environment sent to the
Chef server. By default this is empty and will not use an environment.
* `config_template` (string) - Path to a template that will be used for * `config_template` (string) - Path to a template that will be used for
the Chef configuration file. By default Packer only sets configuration the Chef configuration file. By default Packer only sets configuration
it needs to match the settings set in the provisioner configuration. If it needs to match the settings set in the provisioner configuration. If
@ -55,9 +58,6 @@ since it will allow the provisioner to clean up the node/client.
Server. This is optional and by defalt is empty. If you don't set this, Server. This is optional and by defalt is empty. If you don't set this,
Packer can't clean up the node from the Chef Server using knife. Packer can't clean up the node from the Chef Server using knife.
* `chef_environment` (string) - The name of the chef_environment sent to the
Chef server. By default this is empty and will not use an environment.
* `prevent_sudo` (boolean) - By default, the configured commands that are * `prevent_sudo` (boolean) - By default, the configured commands that are
executed to install and run Chef are executed with `sudo`. If this is true, executed to install and run Chef are executed with `sudo`. If this is true,
then the sudo will be omitted. then the sudo will be omitted.