Puppet settings are highly dynamic, and their values can come from several different places. To see the actual settings values that a Puppet service will use, run the puppet config print command.
General usage
The puppet config print command loads and evaluates settings, and can imitate any of Puppet’s other commands and services when doing so. The --section and --environment options let you control how settings are loaded; for details, see the sections below on imitating different services.
root or Administrator. If you run puppet config print as some other user, Puppet might not use the system config file.sudo puppet config print <SETTING NAME> [--section <CONFIG SECTION>] [--environment <ENVIRONMENT>]<SETTING NAME>.sudo puppet config print <SETTING 1> <SETTING 2> [...] [--section <CONFIG SECTION>] [--environment <ENVIRONMENT>]name = value pairs for all requested settings.sudo puppet config print [--section <CONFIG SECTION>] [--environment <ENVIRONMENT>]name = value pairs for all settings.Config sections
--section option specifies which section of puppet.conf to use when finding settings. It is optional, and defaults to main. Valid sections are:
-
main(default) — used by all commands and services -
master— used by the Puppet master service and thepuppetserver cacommand -
agent— used by the Puppet agent service -
user— used by the Puppet apply command and most other commands
As usual, the other sections will override the main section if they contain a setting; if they don’t, the value from main will be used, or a default value if the setting isn’t present there.
Environments
The --environment option specifies which environment to use when finding settings. It is optional and defaults to the value of the environment setting in the user section (usually production, since it’s rare to specify an environment in user).
You can only specify environments that exist.
This option is primarily useful when looking up settings used by the master service, since it’s rare to use environment config sections for Puppet apply and Puppet agent.
Imitating Puppet master and puppetserver ca
To see the settings the Puppet master service and the puppetserver ca command would use:
-
Specify
--section master. -
Use the
--environmentoption to specify the environment you want settings for, or let it default toproduction. -
Remember to use
sudo. -
If your Puppet master is managed as a Rack application (for example, with Passenger), check the
config.rufile to make sure it’s using the confdir and vardir that you expect. If it’s using non-standard ones, you will need to specify them on the command line with the--confdirand--vardiroptions; otherwise you might not see the correct values for settings.
dev environment: sudo puppet config print modulepath --section master --environment dev/etc/puppetlabs/code/environments/dev/modules:/etc/puppetlabs/code/modules:/opt/puppetlabs/puppet/modulessudo puppet config print storeconfigs storeconfigs_backend --section master
storeconfigs = true
storeconfigs_backend = puppetdbImitating Puppet agent
-
Specify
--section agent. -
Remember to use
sudo. -
If you are seeing something unexpected, check your Puppet agent init script or cron job to make sure it is using the standard confdir and vardir, is running as root, and isn’t overriding other settings with command line options. If it’s doing anything unusual, you might have to set more options for the
config printcommand.
sudo puppet config print ordering --section agent
manifestImitating puppet apply
-
Specify
--sectionuser. -
Remember to use
sudo. -
If you are seeing something unexpected, check the cron job or script that is responsible for configuring the machine with Puppet apply. Make sure it is using the standard confdir and vardir, is running as root, and isn’t overriding other settings with command line options. If it’s doing anything unusual, you might have to set more options for the
config printcommand.
sudo puppet config print report reports --section user
report = true
reports = store,http