Forge Home


Adds the functionality to use environment parameters from Puppet Enterprise Console


9,574 latest version

2.4 quality score

Version information

  • 2.1.0 (latest)
  • 2.0.0
  • 1.0.0
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Aug 14th 2014

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'jay-console_env', '2.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add jay-console_env
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install jay-console_env --version 2.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



jay/console_env — version 2.1.0 Aug 14th 2014



This is the console_env module. It was written with the sole purpose of adding the ability to specify environments in the console using key/value pairs.

This module is merely a temporary solution, to set environments without having to use an alternative ENC.


Include this module on your Console node:

include console_env

By default the ensure value for the console_env class is set to present

Under the hood the module is using an ruby script to curl the console and extract the value for the environment parameter if it exists, if the environment parameter is found it is appends it to the environment stanza at the bottom of what is returned via the ENC scripts curl.

Now you are able to specify the environment for individual nodes and groups in the console using the key value pair of:

environment => your_environment

Make sure to make all the proper adjustments in /etc/puppetlabs/puppet/puppet.conf specified in the environment guide

Note: In some cases you may need to restart pe-httpd for changes to take affect



Please submit any pull request to console-env repo