--- layout: "docs" page_title: "Puppet Server Provisioner" --- # Puppet Server Provisioner Type: `puppet-server` The `puppet-server` provisioner provisions Packer machines with Puppet by connecting to a Puppet master.
{
"type": "puppet-server",
"options": "--test --pluginsync",
"facter": {
"server_role": "webserver"
}
}
## Configuration Reference
The reference of available configuration options is listed below.
The provisioner takes various options. None are strictly
required. They are listed below:
* `client_cert_path` (string) - Path to the client certificate for the
node on your disk. This defaults to nothing, in which case a client
cert won't be uploaded.
* `client_private_key_path` (string) - Path to the client private key for
the node on your disk. This defaults to nothing, in which case a client
private key won't be uploaded.
* `facter` (hash) - Additional Facter facts to make available to the
Puppet run.
* `options` (string) - Additional command line options to pass
to `puppet agent` when Puppet is ran.
* `puppet_node` (string) - The name of the node. If this isn't set,
the fully qualified domain name will be used.
* `puppet_server` (string) - Hostname of the Puppet server. By default
"puppet" will be used.
* `prevent_sudo` (boolean) - By default, the configured commands that are
executed to run Puppet are executed with `sudo`. If this is true,
then the sudo will be omitted.
* `staging_directory` (string) - This is the directory where all the configuration
of Puppet by Packer will be placed. By default this is "/tmp/packer-puppet-server".
This directory doesn't need to exist but must have proper permissions so that
the SSH user that Packer uses is able to create directories and write into
this folder. If the permissions are not correct, use a shell provisioner
prior to this to configure it properly.