Docs Grey arrow pointing right Puppet Enterprise Grey arrow pointing right Managing and deploying Puppet code Grey arrow pointing right Managing code with r10k Grey arrow pointing right Deploying environments with r10k Grey arrow pointing right

Deploying environments with r10k

Sections

Deploy environments on the command line with the r10k command.

The first time you run r10k, deploy all environments and modules by running:
r10k deploy environmentCopied!
This command:
  1. Checks your control repository to see which branches are present.
  2. Maps those branches to the Puppet directory environments.
  3. Clones your Git repo, and either creates (if this is your first run) or updates (if it is a subsequent run) your directory environments with the contents of your repo branches.
Restriction: When running commands to deploy code on your primary server, r10k needs write access to your environment path. Run r10k as the pe-puppet user, as root, or use sudo. Running as root requires access control to the root user.

Updating environments

To update environments with r10k, use the deploy environment command.

Updating all environments

The deploy environment command updates all existing environments and recursively creates new environments.

This command updates modules only on the first deployment of a given environment. On subsequent updates, it only updates the environment.

From the command line, run r10k deploy environment

Updating all environments and modules

With the --modules flag, the deploy environment command updates all environments and modules.

This command:

  • Updates all sources.
  • Creates new environments.
  • Deletes old environments.
  • Recursively updates all environment modules specified in each environment's Puppetfile.

This command does the maximum possible work, and is therefore the slowest method for r10k deployments. Usually, you must use the less resource-intensive commands for updating environments and modules.

From the command line, run r10k deploy environment --modules

Updating a single environment

To update a single environment, specify the environment name with the deploy environment command.

This command updates modules only on the first deployment of the specified environment. On subsequent updates, it only updates the environment.

If you are actively developing on a given environment, running the following command is the quickest way to deploy your changes:

r10k deploy environment <MY_WORKING_ENVIRONMENT>

Updating a single environment and its modules

To update both a single given environment and all of the modules contained in that environment's Puppetfile, add the --modules flag to your command. This is useful if you want to make sure that a given environment is fully up to date.

On the command line, run r10k deploy environment <MY_WORKING_ENVIRONMENT> --modules

Installing and updating modules

To update modules, use the r10k deploy module subcommand. This command installs or updates the modules specified in each environment's Puppetfile.

If the specified module is not described in a given environment's Puppetfile, that environment is skipped.

Updating specific modules across all environments

To update specific modules across all environments, specify the modules with the deploy module command.

Important: You must run the r10k deploy environment command without the --modules flag before you update modules across all environments. This command fetches any updates to the applicable Puppetfile.

You can specify a single module or multiple modules. For example, to update the apache, jenkins, and java modules, run r10k deploy module apache jenkins java

Updating one or more modules in a single environment

To update specific modules in a single environment, specify both the environment and the modules.

Important: You must run the r10k deploy <environment> command without the --modules flag before you update modules in a single environment. This command fetches any updates to the applicable Puppetfile.

On the command line, run r10k deploy module with:

  • The environment option -e.
  • The name of the environment.
  • The names of the modules you want to update in that environment.

For example, to install the apache, jenkins, and java modules in the production environment, run r10k deploy module -e production apache jenkins java

Viewing environments with r10k

Display information about your environments and modules with the r10k deploy display subcommand. This subcommand does not deploy environments, but only displays information about the environments and modules r10k is managing.

This command can return varying levels of detail about the environments.

  • To display all environments being managed by r10k, use the deploy display command. From the command line, run r10k deploy display
  • To display all managed environments and Puppetfile modules, use the Puppetfile flag, -m. From the command line, run r10k deploy display -m
  • To get detailed information about module versions, use the -m (Puppetfile) and --detail flags. This provides both the expected and actual versions of the modules listed in each environment's Puppetfile. From the command line, run r10k deploy display -m --detail
  • To get detailed information about the modules only in specific environments, limit your query with the environment names. This provides both the expected and actual versions of the modules listed in the Puppetfile in each specified environment. For example, to see details on the modules for environments called production, vmwr, and webrefactor, run: 
    r10k deploy display -m --detail production vmwr webrefactorCopied!
Was this page helpful?