cfpuppetserver
Post-setup configuration to live in peace with cfnetwork and cfsystem modules
Version information
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
Add this module to your Puppetfile:
mod 'codingfuture-cfpuppetserver', '0.1.0'
Learn more about managing modules with a PuppetfileDocumentation
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 addressdeployuser = 'deploypuppet'
- user name for auto deploy user for VCS hookdeployuser_auth_keys = undef
- list of ssh_authorized_keys configurationspuppet_git_host = undef
- if set, adds require firewall rules to deploy from VCSpuppetsever = 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
Change Log
All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.
[0.9.0]
Initial release
Dependencies
- puppetlabs-stdlib (>= 4.11.0)
- puppetlabs-apt (>= 2.2.1)
- codingfuture-cfnetwork (>= 0.9.0)
- codingfuture-cfsystem (>= 0.9.0)