r10k subcommand reference

This version is out of date. For current versions, see Puppet Enterprise support lifecycle.

The following subcommands are available with r10k:

  • deploy: Performs operations on environments.
  • help: Shows the help page for r10k.
  • puppetfile: Performs operations on a Puppetfile.
  • version Prints the version of r10k you are using.

First-level subcommand options

Each subcommand allows the following options:

  • --color: Enables color coded log messages.
  • -h, --help: Shows help for this command.
  • -t, --trace: Displays stack traces on application crash.
  • -v, --verbose: Sets log verbosity. Valid values: fatal, error, warn, notice, info, debug, debug1, debug2.


The r10k deploy command accepts the following subcommands:

  • display: Displays a list of environments in your deployment.
    • To display a list of modules in the Puppetfile, add the -p flag to the command.
    • To display detailed information, add --detail to the command.
    • To update the environment sources, add --fetch to the command. This allows you to check for missing environments.
  • environment: Deploys environments and their dependent modules.
    • To update modules specified in the environment’s Puppetfile, add the -p flag to the command.
  • module: Deploys a module in all environments.
    • To update the modules in a particular environment, add the -e flag to the command.

See the Deploying environments with r10k for examples of r10k deploy command use.


Note that these subcommands must be run as the user with write access to that environment’s modules directory (or the moduledir directory, if you specified a different modules directory in the Puppetfile). These commands interact with the Puppetfile in the current working directory, so before running the subcommand, make sure you are in the directory of the Puppetfile you want to use.

The r10k puppetfile command accepts the following subcommands:

  • check: Verifies the Puppetfile syntax is correct.
  • install: Installs all modules from a Puppetfile.
    • To set a custom puppetfile path, add the --puppetfile flag to the command.
    • To set a custom moduledir location, add the --moduledir flag to the command.
  • purge: Purges unmanaged modules from a Puppetfile managed directory.
Puppet sites use proprietary and third-party cookies. By using our sites, you agree to our cookie policy.