Forge Home

director

Directs puppet nodes to become a different node.

9,790 downloads

9,410 latest version

2.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.0.0 (latest)
  • 0.2.0
  • 0.1.2
released Sep 20th 2014

Start using this module

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

Add this module to your Puppetfile:

mod 'nekroze-director', '1.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add nekroze-director
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install nekroze-director --version 1.0.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.

Download

Documentation

nekroze/director — version 1.0.0 Sep 20th 2014

director

This is the director module. It allows you to have a node definition become a director for new machines.

A common VM workflow is to make a template and clone it when you need another machine. This module will allow you to specify what the next checked in clone will automatically become.

example

node base.nekroze.local {
  class { 'director':
    target => 'database.nekroze.local',
  }
}

This node definition will cause any puppet agent by the certname of base.nekroze.local to change its certname to database.nekroze.local.

What this means is that after the first puppet agent run (eg. puppet agent -t) this machine will start pulling the definition for database.nekroze.local.