puppet-apply

puppet apply [options] manifest

puppet apply executes Puppet manifests directly on the local system without requiring a Puppet server. It compiles and applies the specified manifest file, making it ideal for standalone configuration management, testing manifests during development, and bootstrapping systems before they join a Puppet infrastructure.The command accepts manifest files written in Puppet's declarative DSL or inline code via the -e flag. It supports --noop for dry-run previews of changes, --verbose and --debug for detailed execution output, and --modulepath for specifying where to find Puppet modules. Since it operates independently of a server, puppet apply is commonly used in container image builds, Vagrant provisioning, and one-off system configuration tasks.

MANIFEST

Puppet manifest file to compile and apply.

Dry run mode; shows what changes would be made without applying them.

Print extra information during execution.

Enable full debugging output.

Execute a specific piece of Puppet code instead of a manifest file.

Enable common testing options: verbose, detailed-exitcodes, and show_diff.

Provide extra information via exit codes (0=no changes, 2=changes applied, 4=failures, 6=both).

Where to send log messages (syslog, eventlog, console, or a file path). Defaults to console.

Apply a JSON catalog instead of compiling a manifest. Accepts a file path or stdin.

Load any stored classes from the classfile.

Module search path for resolving classes and defined types.

/etc/puppetlabs/puppet/puppet.conf

Configuration file controlling module paths, log level, environment settings, and other Puppet behavior for local apply runs.

Default module path searched when resolving classes and defined types referenced in manifests.

Requires Puppet installed. Operates without a Puppet server (masterless mode). Must be run as root to manage system resources.

puppet apply provides local Puppet manifest execution.

puppet(1), puppet-agent(1)