Forge Home

tlsfiles

Transport Layer Security (TLS) Files

26,496 downloads

477 latest version

5.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.6 (latest)
  • 1.0.5
  • 1.0.4
  • 1.0.3
  • 1.0.2
  • 1.0.1
  • 1.0.0
  • 0.3.0
  • 0.2.0
released Jun 11th 2024
This version is compatible with:
  • Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >=2.7.20 < 9.0.0
  • , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'thias-tlsfiles', '1.0.6'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add thias-tlsfiles
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install thias-tlsfiles --version 1.0.6

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

thias/tlsfiles — version 1.0.6 Jun 11th 2024

puppet-tlsfiles

Overview

This module is used to manage Private Key Infrastructure (PKI) Transport Layer Security (TLS) files. Typically these are Secure Socket Layer (SSL) X.509 private keys and certificates.

The module supports installing intermediate certificates as well as optionally joining keys and certificates into single files.

  • tlsfiles : Manage key and certificate
  • tlsfiles::dehydrated : Manage key and certificate from Dehydrated.

Parameters

  • $crtpath = '/etc/pki/tls/certs'
  • $keypath = '/etc/pki/tls/private'
  • $crtmode = '0644'
  • $keymode = '0600'
  • $owner = 'root'
  • $group = 'root'
  • $intcert = false
  • $intjoin = false
  • $pem = false
  • $srcdir = 'tlsfiles'
  • $crtdir = 'crt'
  • $keydir = 'key'
  • crtname = "${title}.crt"
  • keyname = "${title}.key"

Examples

To install keys and certificates present under :

  • mymodulename/templates/tlsfiles/crt/www.example.com.crt
  • mymodulename/templates/tlsfiles/key/www.example.com.key
  • mymodulename/templates/tlsfiles/crt/IntermediateCA.crt

In site.pp to centralize all of your files :

Tlsfiles { srcdir => 'mymodulename/tlsfiles' }

Install key and certificate files to the default locations :

tlsfiles { 'www.example.com': }

Install a PEM file containing key and certificate to a custom location (it will be called www.example.com.pem) :

tlsfiles { 'www.example.com':
  keypath => '/etc/foo',
  pem     => true,
}

The same as the above, but including the intermediate CA certificate :

tlsfiles { 'www.example.com':
  keypath => '/etc/foo',
  intcert => 'IntermediateCA',
  pem     => true,
}

Dehydrated

The similar tlsfiles::dehydrated definition is better when using source files generated by Dehydrated.

Just make sure your mymodule/templates/certs/ directory is where Dehydrated manages its certificates (a symlink will do), and use something like:

tlsfiles::dehydrated { 'wildcard.example.com':
  srcdir => 'mymodule/certs',
}