In Puppet 4.0, we changed the locations of a lot of important config files and directories. We also changed Puppet’s packaging to install different things in different places.
This page is a summary, to quickly orient users arriving from Puppet 3.
On managed *nix systems, install
puppet-agent instead of
puppet. (This package also provides
puppet apply, suitable for standalone Puppet systems.)
This is a new name for a new thing. Instead of using package dependencies to bring in tools like Facter, Hiera, and Ruby, it includes private versions of all of them. It also includes MCollective.
On Windows, use the same package as before. The open source package now includes MCollective.
On *nix platforms, the main executables moved to
/opt/puppetlabs/bin. This means Puppet and related tools aren’t included in your PATH by default. You’ll need to either:
/opt/puppetlabs/binto your PATH
/opt/puppetlabs/bin/puppet applywhen running Puppet commands
On Windows, executables stayed in the same location, and the MSI package still adds Puppet’s tools to the PATH.
The executables in
/opt/puppetlabs/bin are just the “public” applications that make up Puppet. Private supporting commands like
gem are in
/opt/puppetlabs/puppet/bin, to keep them from accidentally overriding system tools if you add the public bin dir to your PATH.
confdir (used by
root and the
puppet user) is now
/etc/puppetlabs/puppet, instead of
/etc/puppet. Open source Puppet 4.0 and newer use the same
confdir as Puppet Enterprise.
confdir is the directory that holds config files like
On Windows, this stayed the same. It’s still in the
COMMON_APPDATA folder, defaulting to
C:\ProgramData\PuppetLabs\puppet\etc on modern Windows versions.
On some Linux distros, our default config in Puppet 3.x set Puppet’s
$vardir/ssl instead of
$confdir/ssl. Since Puppet 4.x, the default location is in the
confdir on all platforms.
Other related configurations were also moved into the
/etc/puppetlabs directory in Puppet 4.0. Puppet Server now uses
/etc/puppetlabs/puppetserver, and MCollective uses
codedirholds all modules, manifests, and data
All of the content that Puppet uses to configure nodes was moved into a new directory, named
codedir. In Puppet 3.x, this content was in the
codedir location is:
<USER DIRECTORY>/.puppetlabs/etc/codeif you’re running as a non-root user
The main contents of the
modulesdirectory. Use this location only for modules you want deployed in all environments.
Since Puppet 4.0, directory environments are always enabled.
$codedir/environments. Upon installation, Puppet creates a directory for the default
If you’re starting from scratch:
You can still put global modules in
$codedir/modules, and can configure a global main manifest with the
Hiera’s default settings now use an environment-specific datadir for the YAML and JSON backends. For example, the
production environment’s default Hiera data directory would be
puppet agenthas moved, and is now separate from Puppet Server’s
rundir, where the service PID files go, has moved:
/var/run/puppetlabs. (Puppet Server has a
puppetserverdirectory in this directory.)
C:\ProgramData\PuppetLabs\puppet\var\run— this is the same as before, but it’s now outside the main