Configuring Puppet Core
A newer version is available; see the version menu above for details.
All of puppet’s configuration files can be found in
/etc/puppetlabs/puppet/ on *nix systems. This is PE’s default
$confdir. Do not change this
$confdir location, as doing so will will break the functionality of your PE infrastructure.
On Windows, you can find them in Puppet’s data directory.
- For an exhaustive description of puppet’s configuration settings and auxiliary configuration files, refer to the Configuring Puppet Guide.
- For details, syntax and options for the available configuration settings, visit the configuration reference.
For details on how to configure access to Puppet’s pseudo-RESTful HTTP API, refer to the Access Control Guide.
Note: If you haven’t modified the
auth.conffile, it may occasionally be modified when upgrading between Puppet Enterprise versions. However, if you HAVE modified it, the upgrader will not automatically overwrite your changes, and you may need to manually update
auth.confto accommodate new Puppet Enterprise features. Be sure to read the upgrade notes when upgrading your Puppet master to new versions of PE.
Puppet in PE includes full Hiera support, including automatic class parameter lookup.
hiera.yamlfile is located at
/etc/puppetlabs/code/hiera.yamlon the Puppet master server.
- See the Hiera documentation for details about the
hiera.yamlconfig file format.
- To use Hiera with Puppet Enterprise, you must, at minimum, edit
hiera.yamlto set a
:yamlbackend, ensure that the hierarchy is a good fit for your deployment, and create data source files in the data directory.
To learn more about using Hiera, see the Hiera documentation.
Disabling Update Checking
When the Puppet master’s web server (
pe-puppetserver) starts or restarts, it checks for updates. To get the correct update info, the server will pass some basic, anonymous info to Puppet Labs’ servers. Specifically, it will transmit:
- the IP address of the client
- the type and version of the client’s OS
- the installed version of PE
There are two methods to disable update checking (e.g. if your company policy forbids transmitting this information), one of which is specific to platforms using systemd (currently RHEL-7 and SLES-12 only).
If your platform DOES NOT use systemd, you can disable update checks by adding the following line to the
Note: if you delete the
/etc/puppetlabs/installer/answers.installfile, update checking will resume.
If your platform uses systemd, you can disable updates by creating the following file:
As long as this file is present, Puppet Server will not check in for updates. (Note that this method will work on all platforms, not just those using systemd.)