puppet

Apply manifest locally

$ puppet apply [manifest.pp]

$ puppet parser validate [manifest.pp]

$ puppet agent --test

$ puppet module list

$ puppet module generate [name]

puppet subcommand [options]

puppet is a configuration management tool that automates the provisioning and management of infrastructure using a declarative language. Administrators describe the desired state of systems through manifests written in Puppet's DSL, and the tool ensures machines converge to that state by installing packages, managing files, configuring services, and handling users.
Puppet operates in two modes: a client-server architecture where agents pull catalogs from a Puppet server, and a standalone mode using puppet apply for local manifest execution. The resource abstraction layer handles platform differences automatically, so the same manifest can manage packages across Debian, Red Hat, and other distributions without modification.
The ecosystem includes a module system for sharing reusable configuration code through Puppet Forge, Facter for gathering system facts, and Hiera for separating data from code. Puppet supports environments for testing changes before production rollout and provides detailed reporting on configuration drift and enforcement actions.

apply

Apply manifest.

Run puppet agent.

Parse manifests.

Manage modules.

Query resources.

Test run.

Dry run.

/etc/puppetlabs/puppet/puppet.conf

Main configuration file controlling server address, environment, run interval, certificate settings, and module paths.

Default location for site manifests that define node configurations in the production environment.

Module directory containing reusable Puppet modules with classes, defined types, and templates.

Environment variable specifying additional directories to search for custom Facter facts.

Requires Puppet installation. Master-agent or standalone.

Puppet was created by Puppet Labs for IT automation.

puppet-apply(1), ansible(1), chef(1)