ananace

class profiles::raspberry_pi::fake_aio {
  file {
    default:
      ensure => file;

    '/etc/facter/facts.d/aio_agent_version.txt':
      content => "aio_agent_version=${fact('puppetversion')}";
    '/etc/facter/facts.d/aio_fake_agent.txt':
      content => "aio_fake_agent=true";
  }

chadh

#!/usr/bin/env bash

set -euo pipefail

PUPPET_CRL=$(/opt/puppetlabs/bin/puppet config print hostcrl)
PUPPET_CRL_DIR=$(dirname "$PUPPET_CRL")
PUPPET_CA_CRL=$(/opt/puppetlabs/bin/puppet config print cacrl)
PUPPET_CA_CRL_DIR=$(dirname "$PUPPET_CA_CRL")
if [[ -d $PUPPET_CA_CRL_DIR ]]; then
  SERVER="yes"

chadh

Here are the set of steps I ultimately came up with when trying to set up Puppet 6 servers in AWS using an ACM private CA for the Root.

1. Create Private CA in AWS Certificate Manager

   • Type: Root
   • Common Name: domain.int (whatever you want)
   • Key Algorithm: RSA 2048
   • provide S3 Bucket for storing CRL

2. Generate Private Key and CSR for each Puppet Server’s Intermediate CA certificate:

   • configuration for openssl command (certreq.cnf):

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"