Single-system Puppetized configuration utility

Puppet Labs TSE Team



6,325 latest version

5.0 quality score

Version information

  • 0.7.1 (latest)
  • 0.7.0
  • 0.6.4
  • 0.6.3
  • 0.6.2
  • 0.6.1
  • 0.6.0
  • 0.5.2
  • 0.5.1
  • 0.5.0
released Feb 16th 2016
This version is compatible with:
  • Puppet Enterprise >=2015.2.0
  • Puppet >=4.2.1
  • RedHat

Start using this module


tse/nimbus — version 0.7.1 Feb 16th 2016


This module provides a new Puppet command, puppet nimbus.

When puppet nimbus apply is run, Puppet will set the runtime $environmentpath to $nimbus_environmentpath, set the runtime $environment to $nimbus_environment, and read $nimbus_config. A custom node terminus will be switched to that reads classes from the classes config key. A custom data terminus will be used to bind data from the data config key. The $nimbus_environment will be populated to match the modules defined in the modules config key. With this configuration primed, Puppet will be run.

The end result is that users may define a single text file or set of text files to be merged that list all the modules they want, the data they want, and the classes they want applied to their local machine. They may then use the puppet nimbus command to easily puppetize their system from that input.

Note that alternatively, a confdir may be specified, in which case all .conf files inside the confdir will be read and merged into a compositional configuration. This allows for things such as starting from a common configuration and adding in personal customization by including an additional file.

New users can get started with a config provided by their company or team.



Assume that the Puppet AIO package has just been installed and nothing else. This is an example of bootstrapping a nimbus configuration. Try it!

puppet module install tse/nimbus
curl -Lo example.conf
puppet nimbus install_modules example.conf
puppet nimbus apply example.conf


puppet module install tse/nimbus
puppet nimbus install_modules
puppet nimbus apply

Or just:

puppet module install tse/nimbus
puppet nimbus apply

Note on OSX: due to it is necessary to update root CA bundles used by Puppet to get the module tool working (to install modules). The following can be used to do that:

export OPENSSL=/opt/puppetlabs/puppet/bin/openssl
sudo /opt/puppetlabs/puppet/bin/c_rehash /opt/puppetlabs/puppet/lib/ruby/2.1.0/rubygems/ssl_certs
export SSL_CERT_DIR=/opt/puppetlabs/puppet/lib/ruby/2.1.0/rubygems/ssl_certs

As long as SSL_CERT_DIR is set correctly any Puppet command that needs access to the > Forge will work.

With Existing Modules

In the event an r10k control repo is used to define the environment, nimbus may be used for classification and data while referencing the environment r10k sets up.

r10k puppetfile install /path/to/prod/Puppetfile
puppet module install tse/nimbus
curl -Lo example.conf

r10k of course isn't strictly necessary. Any means of populating the modules will work.

After the modules have been configured, use one of:

puppet nimbus apply example.conf --modulepath=/path/to/prod/modules


puppet nimbus apply example.conf --environmentpath=/path/to --environment=prod

Directory structure

|-- environments/
`-- nimbus_environments/    # $nimbus_environmentpath
    `-- default                  # $nimbus_environment
        |-- manifests/
        |   `-- site.pp
        |-- modules/
        `-- hieradata/

`-- nimbus/               # $nimbus_confdir
    `-- nimbus.conf         # $nimbus_config

Configuration File

# nimbus.conf (hocon)
classes: [

data: {
  "nimbus::test::arg1": "example",
  "nimbus::test::arg2": "like hiera data",

modules: {
  "puppetlabs/stdlib": {
    "version": "4.9.0",
  "tse/nimbus": {
    "version": "0.5.0",
  "lwf/remote_file": {
    "type": "tarball",
    "source": "",
    "version": "1.0.1",