After you've installed Puppet Enterprise (PE), optimize it for your environment by configuring and tuning settings as needed. For example, you might want to add your own certificate to the whitelist, increase the max-threads setting for http and https requests, or configure the number of JRuby instances.
There are two main methods for configuring PE: using the console or adding a key to Hiera.
In general, use the console to apply and configure profile classes starting with puppet_enterprise::profile or when editing or adding any parameters in PE-managed configuration files. Parameter values set in the console override those you've manually set in the configuration files.
Use Hiera to apply and configure classes that aren't profile classes.
pe.conf only — not the console — to specify configuration parameters. Using pe.conf or Hiera ensures that configuration is applied to both your master and replica. Configure settings using the console
In general, use the console to apply and configure profile classes starting with puppet_enterprise::profile or when editing or adding any parameters in PE-managed configuration files.
Configure settings with Hiera
Use Hiera to apply and configure classes that aren't profile classes.
You can use Hiera to do things like increase or decrease the number of JRuby instances on the Puppet Server, or tune the number of max_requests_per_instance that will accept requests on the Puppet Server.
.yaml file, add the setting you're configuring. -
*nix:
/etc/puppetlabs/code/environments/<ENVIRONMENT>/data/common.yaml -
Windows:
%CommonAppData%\PuppetLabs\code\environments\<ENVIRONMENT>\data\common.yaml
hiera.yaml configuration to change location for data files (the datadir setting) or the path of the common data file (in the hierarchy section), look for the default .yaml file in the customized location.