Forge Home

cfpuppetserver

Post-setup configuration to live in peace with cfnetwork and cfsystem modules

21,500 downloads

1,641 latest version

3.6 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.3.1 (latest)
  • 1.3.0
  • 1.1.0
  • 1.0.2
  • 1.0.1
  • 1.0.0
  • 0.12.3
  • 0.12.2
  • 0.12.1
  • 0.12.0
  • 0.11.4
  • 0.11.2
  • 0.11.1
  • 0.11.0
  • 0.10.5
  • 0.10.4
  • 0.10.3
  • 0.10.2
  • 0.10.1
  • 0.10.0
  • 0.9.7
  • 0.9.6
  • 0.9.5
  • 0.9.4
  • 0.9.3
  • 0.9.2
  • 0.9.1
  • 0.9.0
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Feb 11th 2016
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=4.0.0 <5.0.0
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'codingfuture-cfpuppetserver', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add codingfuture-cfpuppetserver
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install codingfuture-cfpuppetserver --version 0.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.

Download

Documentation

codingfuture/cfpuppetserver — version 0.1.0 Feb 11th 2016

cfpuppetserver

Description

Functionality of this package is not complete. It's primary purpose is to live in peace with cfsystem and cfnetwork packages.

However, it also provides a handy tool to initalize new puppet client hosts:

~#  /root/genclientinit.sh 
Usage: ./genclientinit.sh <certname> [<cflocation> [<cflocationpool> [<http_proxy>]]

Setup

If r10k is used until RK-3 is solved, make sure to have the following lines in Puppetfile:

mod 'puppetlabs/stdlib', '4.11.0'
mod 'puppetlabs/apt', '2.2.1'
mod 'codingfuture/cfnetwork'
mod 'codingfuture/cfsystem'

cfpuppetserver class

  • puppet_host - puppet server address
  • deployuser = 'deploypuppet' - user name for auto deploy user for VCS hook
  • deployuser_auth_keys = undef - list of ssh_authorized_keys configurations
  • puppet_git_host = undef - if set, adds require firewall rules to deploy from VCS
  • puppetsever = true - if true, assume Puppet Server lives on this host (affects firewall)
  • puppetdb = true - if true, assume Puppet DB lives on this host (affects firewall)
  • service_face = 'any' - cfnetwork::iface name to listen for incoming client connections