puppetdb

Table of Contents

1. Overview - What is the PuppetDB module?
2. Module Description - What does the module do?
3. Setup - The basics of getting started with PuppetDB module
4. Upgrading - Guide for upgrading from older revisions of this module
5. Usage - The classes and parameters available for configuration
6. Implementation - An under-the-hood peek at what the module is doing
7. Limitations - OS compatibility, etc.
8. Development - Guide for contributing to the module
9. Release Notes - Notes on the most recent updates to the module

Overview

By guiding puppetdb setup and configuration with a Puppet master, the PuppetDB module provides fast, streamlined access to data on puppetized infrastructure.

Module Description

The PuppetDB module provides a quick way to get started using PuppetDB, an open source inventory resource service that manages storage and retrieval of platform-generated data. The module will install PostgreSQL and PuppetDB if you don't have them, as well as set up the connection to Puppet master. The module will also provide a dashboard you can use to view the current state of your system.

For more information about PuppetDB please see the official PuppetDB documentation.

Setup

What PuppetDB affects:

• package/service/configuration files for PuppetDB
• package/service/configuration files for PostgreSQL (optional, but set as default)
• Puppet master's runtime (via plugins)
• Puppet master's configuration
  • note: Using the puppetdb::master::config class will cause your routes.yaml file to be overwritten entirely (see Usage below for options and more information )
• system firewall (optional)
• listened-to ports

Introductory Questions

To begin using PuppetDB, you’ll have to make a few decisions:

• Should I run the database on the same node that I run PuppetDB on?
• Should I run PuppetDB on the same node that I run my master on?

The answers to those questions will be largely dependent on your answers to questions about your Puppet environment:

• How many nodes are you managing?
• What kind of hardware are you running on?
• Is your current load approaching the limits of your hardware?

Depending on your answers to all of the questions above, you will likely fall under one of these set-up options:

1. Single Node (Testing and Development)
2. Multiple Node (Recommended)

Single Node Setup

This approach assumes you will use our default database (PostgreSQL) and run everything (PostgreSQL, PuppetDB, Puppet master) all on the same node. This setup will be great for a testing or experimental environment. In this case, your manifest will look like:

node <hostname> {
  # Configure puppetdb and its underlying database
  class { 'puppetdb': }
  
  # Configure the Puppet master to use puppetdb
  class { 'puppetdb::master::config': }
}

You can provide some parameters for these classes if you’d like more control, but that is literally all that it will take to get you up and running with the default configuration.

Multiple Node Setup

This approach is for those who prefer not to install PuppetDB on the same node as the Puppet master. Your environment will be easier to scale if you are able to dedicate hardware to the individual system components. You may even choose to run the puppetdb server on a different node from the PostgreSQL database that it uses to store its data. So let’s have a look at what a manifest for that scenario might look like:

This is an example of a very basic 3-node setup for PuppetDB.

$puppetdb_host = 'puppetdb.example.lan'
$postgres_host = 'postgres.example.lan'
node 'master.example.lan' {
  # Here we configure the Puppet master to use PuppetDB,
  # telling it the hostname of the PuppetDB node
  class { 'puppetdb::master::config':
    puppetdb_server => $puppetdb_host,
  }
}
node 'postgres.example.lan' {
  # Here we install and configure PostgreSQL and the PuppetDB
  # database instance, and tell PostgreSQL that it should
  # listen for connections to the `$postgres_host`
  class { 'puppetdb::database::postgresql':
    listen_addresses => $postgres_host,
  }
}
node 'puppetdb.example.lan' {
  # Here we install and configure PuppetDB, and tell it where to
  # find the PostgreSQL database.
  class { 'puppetdb::server':
    database_host => $postgres_host,
  }
}

This should be all it takes to get a 3-node, distributed installation of PuppetDB up and running. Note that, if you prefer, you could easily move two of these classes to a single node and end up with a 2-node setup instead.

Enable SSL connections

To use SSL connections for the single node setup, use the following manifest:

node <hostname> {
  # Here we configure puppetdb and PostgreSQL to use ssl connections
  class { 'puppetdb':
    postgresql_ssl_on => true,
    database_host => '<hostname>',
    database_listen_address => '0.0.0.0'
  }
  
  # Configure the Puppet master to use puppetdb
  class { 'puppetdb::master::config': }

To use SSL connections for the multiple nodes setup, use the following manifest:

$puppetdb_host = 'puppetdb.example.lan'
$postgres_host = 'postgres.example.lan'

node 'master.example.lan' {
  # Here we configure the Puppet master to use PuppetDB,
  # telling it the hostname of the PuppetDB node.
  class { 'puppetdb::master::config':
    puppetdb_server => $puppetdb_host,
  }
}

node 'postgres.example.lan' {
  # Here we install and configure PostgreSQL and the PuppetDB
  # database instance, and tell PostgreSQL that it should
  # listen for connections to the `$postgres_host`. 
  # We also enable SSL connections.
  class { 'puppetdb::database::postgresql':
    listen_addresses => $postgres_host,
    postgresql_ssl_on => true,
    puppetdb_server => $puppetdb_host
  }
}

node 'puppetdb.example.lan' {
  # Here we install and configure PuppetDB, and tell it where to
  # find the PostgreSQL database. We also enable SSL connections.
  class { 'puppetdb::server':
    database_host => $postgres_host,
    postgresql_ssl_on => true
  }
}

Beginning with PuppetDB

Whether you choose a single node development setup or a multi-node setup, a basic setup of PuppetDB will cause: PostgreSQL to install on the node if it’s not already there; PuppetDB postgres database instance and user account to be created; the postgres connection to be validated and, if successful, PuppetDB to be installed and configured; PuppetDB connection to be validated and, if successful, the Puppet master config files to be modified to use PuppetDB; and the Puppet master to be restarted so that it will pick up the config changes.

If your logging level is set to INFO or finer, you should start seeing PuppetDB-related log messages appear in both your Puppet master log and your puppetdb log as subsequent agent runs occur.

Cross-node Dependencies

It is worth noting that there are some cross-node dependencies, which means that the first time you add the module's configurations to your manifests, you may see a few failed puppet runs on the affected nodes.

PuppetDB handles cross-node dependencies by taking a sort of "eventual consistency" approach. There’s nothing that the module can do to control the order in which your nodes check in, but the module can check to verify that the services it depends on are up and running before it makes configuration changes--so that’s what it does.

When your Puppet master node checks in, it will validate the connectivity to the puppetdb server before it applies its changes to the Puppet master config files. If it can’t connect to puppetdb, then the puppet run will fail and the previous config files will be left intact. This prevents your master from getting into a broken state where all incoming puppet runs fail because the master is configured to use a puppetdb server that doesn’t exist yet. The same strategy is used to handle the dependency between the puppetdb server and the postgres server.

Hence the failed puppet runs. These failures should be limited to 1 failed run on the puppetdb node, and up to 2 failed runs on the Puppet master node. After that, all of the dependencies should be satisfied and your puppet runs should start to succeed again.

You can also manually trigger puppet runs on the nodes in the correct order (Postgres, PuppetDB, Puppet master), which will avoid any failed runs.

Upgrading

Upgrading from 4.x to 5.x

Significant parameter changes are listed below:

• The PuppetDB module defaults to Puppet 4 pathing and assumes puppetserver is the master service by default
• The PuppetDB module manages Postgres repos by default. To turn this behavior off, set manage_package_repo to false.
• To specify a specific version of PuppetDB to manage, you'll need to use the puppetdb::globals class to set the version of PuppetDB you're using explicitly. The ability to configure the version in the puppetdb::server and puppetdb class have been removed.

For example if your config looked like this before:

class {'puppetdb':
    puppetdb_version => '3.2.4-1.el7',
}
class { 'puppetdb::master::config': }

and you'd still like to use the module with PuppetDB 3.2.4, all you'd have to change would be:

class { 'puppetdb::globals':
    version => '3.2.4-1.el7',
}
class { 'puppetdb' : }
class { 'puppetdb::master::config' : }

The globals class above takes into account the following PuppetDB 3 and Puppet 4 related changes:

* The `puppetdb::master:puppetdb_conf` class has added a `$legacy_terminus`
  to support the PuppetDB 2.x terminus configuration.
* The default `test_url` for the `PuppetDBConnValidator` has also been
  changed to `/pdb/meta/v1/version` but will default to `/v3/version` when
  using a PuppetDB 2.x version.
* The configuration pathing for Puppet and PuppetDB has changed with Puppet
  4 and PuppetDB 3, using PuppetDB 2.x or older assumes the old
  configuration pathing.

See the CHANGELOG file for more detailed information on changes for each release.

Upgrading from 3.x to 4.x

For this release, all dependency versions have been bumped to their latest. Significant parameter changes are listed below:

• The PuppetDB module now only supports Puppet 3.7.1 or later
• puppetlabs/postgresql 4.0.0 or later is now required
• puppetlabs/inifile 1.1.3 or later is now required
• puppetlabs/firewall 1.1.3 or later is now required
• puppetlabs/stdlib 4.2.2 or later is now required
• The parameter manage_firewall for the class puppetdb::database::postgresql has now been removed, since the PostgreSQL module no longer supports this.
• The parameter open_postgres_port for the class puppetdb has also been removed, due to PostgreSQL changes.

See the CHANGELOG file for more detailed information on changes for each release.

Upgrading from 2.x to 3.x

For this release a major dependency has changed. The module pupppetlabs/postgresql must now be version 3.x. Upgrading the module should upgrade the puppetlabs/postgresql module for you, but if another module has a fixed dependency that module will have to be fixed before you can continue.

Some other changes include:

• The parameter manage_redhat_firewall for the class puppetdb has now been removed completely in favor of open_postgres_port and open_ssl_listen_port.
• The parameter manage_redhat_firewall for the class puppetdb::database::postgresql, has now been renamed to manage_firewall.
• The parameter manage_redhat_firewall for the class puppetdb::server has now been removed completely in favor of open_listen_port and open_ssl_listen_port.
• The internal class: puppetdb::database::postgresql_db has been removed. If you were using this, it is now defunct.
• The class puppetdb::server::firewall has been marked as private, do not use it directly.
• The class puppetdb::server::jetty_ini and puppetdb::server::database_ini have been marked as private, do not use it directly.

Upgrading from 1.x to 2.x

A major dependency has been changed, so now when you upgrade to 2.0 the dependency cprice404/inifile has been replaced with puppetlabs/inifile. This may interfere with other modules as they may depend on the old cprice404/inifile instead, so upgrading should be done with caution. Check that your other modules use the newer puppetlabs/inifile module as interoperation with the old cprice404/inifile module will no longer be supported by this module.

Depending on how you install your modules, changing the dependency may require manual intervention. Double check your modules contain the newer puppetlabs/inifile after installing this latest module.

Otherwise, all existing parameters from 1.x should still work correctly.

Usage

PuppetDB supports a large number of configuration options for both configuring the puppetdb service and connecting that service to the Puppet master.

puppetdb::globals

The puppetdb::globals class is intended to provide similar functionality to the postgresql::globals class in the puppetlabs-postgresql module by exposing a top-level entry-point into the module so that we can properly set defaults for the puppetdb::params class based on the version of puppetdb you are using. This setting defaults to present.

You must declare the class to use it:

class { 'puppetdb::globals': }

puppetdb

The puppetdb class is intended as a high-level abstraction (sort of an 'all-in-one' class) to help simplify the process of getting your puppetdb server up and running. It wraps the slightly-lower-level classes puppetdb::server and puppetdb::database::*, and it'll get you up and running with everything you need (including database setup and management) on the server side. For maximum configurability, you may choose not to use this class. You may prefer to use the puppetdb::server class directly, or manage your puppetdb setup on your own.

You must declare the class to use it:

class { 'puppetdb': }

puppetdb::server

The puppetdb::server class manages the PuppetDB server independently of the underlying database that it depends on. It will manage the PuppetDB package, service, config files, etc., but will still allow you to manage the database (e.g. PostgreSQL) however you see fit.

class { 'puppetdb::server':
  database_host => 'pg1.mydomain.com',
}

puppetdb::master::config

The puppetdb::master::config class directs your Puppet master to use PuppetDB, which means that this class should be used on your Puppet master node. It’ll verify that it can successfully communicate with your PuppetDB server, and then configure your master to use PuppetDB.

Using this class allows the module to manipulate the puppet configuration files puppet.conf and routes.yaml. The puppet.conf changes are supplemental and should not affect any of your existing settings, but the routes.yaml file will be overwritten entirely. If you have an existing routes.yaml file, you will want to take care to use the manage_routes parameter of this class to prevent the module from managing that file, and you’ll need to manage it yourself.

class { 'puppetdb::master::config':
  puppetdb_server => 'my.host.name',
  puppetdb_port   => 8081,
}

puppetdb::database::postgresql

The puppetdb::database::postgresql class manages a PostgreSQL server for use by PuppetDB. It can manage the PostgreSQL packages and service, as well as creating and managing the PuppetDB database and database user accounts.

class { 'puppetdb::database::postgresql':
  listen_addresses => 'my.postgres.host.name',
}

Implementation

Resource overview

In addition to the classes and variables mentioned above, PuppetDB includes:

puppetdb::master::routes

Configures the Puppet master to use PuppetDB as the facts terminus. WARNING: the current implementation simply overwrites your routes.yaml file; if you have an existing routes.yaml file that you are using for other purposes, you should not use this.

class { 'puppetdb::master::routes':
  puppet_confdir => '/etc/puppet'
}

The optional parameter routes can be used to specify a custom route configuration. For example to configure routes for masterless puppet.

class { 'puppetdb::master::routes':
  routes => {
    'apply' => {
      'facts' => {
        'terminus' => 'facter',
        'cache'    => 'puppetdb_apply',
      }
    }
  }
}

puppetdb::master::storeconfigs

Configures the Puppet master to enable storeconfigs and to use PuppetDB as the storeconfigs backend.

class { 'puppetdb::master::storeconfigs':
  puppet_conf => '/etc/puppet/puppet.conf'
}

puppetdb::server::validate_db

Validates that a successful database connection can be established between the node on which this resource is run and the specified PuppetDB database instance (host/port/user/password/database name).

puppetdb::server::validate_db { 'validate my puppetdb database connection':
  database_host     => 'my.postgres.host',
  database_username => 'mydbuser',
  database_password => 'mydbpassword',
  database_name     => 'mydbname',
}

Custom Types

puppetdb_conn_validator

Verifies that a connection can be successfully established between a node and the PuppetDB server. Its primary use is as a precondition to prevent configuration changes from being applied if the PuppetDB server cannot be reached, but it could potentially be used for other purposes such as monitoring.

Limitations

Currently, PuppetDB is compatible with:

Puppet Version: 4.10+

Platforms:

• EL 5, 6, 7
• Debian 6, 7
• Ubuntu 10.04, 12.04, 14.04

Community Maintained Platforms:

• Archlinux
• OpenBSD 5.6-current and newer
• SLES 11 SP1

Development

Puppet Labs modules on the Puppet Forge are open projects, and community contributions are essential for keeping them great. We can’t access the huge number of platforms and myriad of hardware, software, and deployment configurations that Puppet is intended to serve.

We want to keep it as easy as possible to contribute changes so that our modules work in your environment. There are a few guidelines that we need contributors to follow so that we can have a chance of keeping on top of things.

You can read the complete contribution guide.

Reference

Table of Contents

Classes

Public Classes

• puppetdb: manage PuppetDB
• puppetdb::database::postgresql: create the PuppetDB postgresql database
• puppetdb::globals: global configuration class for PuppetDB
• puppetdb::master::config: manage the puppet configuration on the primary
• puppetdb::server: manage the PuppetDB server

Private Classes

• puppetdb::database::ssl_configuration: configure SSL for the PuppetDB postgresql database
• puppetdb::master::puppetdb_conf: manage the puppetdb.conf file on the puppet primary
• puppetdb::master::report_processor: manage the installation of the report processor on the primary
• puppetdb::master::routes: manages the routes configuration file on the master
• puppetdb::master::storeconfigs: configure the puppet master to enable storeconfigs and to use puppetdb as the storeconfigs backend
• puppetdb::params: default configuration settings
• puppetdb::server::command_processing: manage puppetdb config ini
• puppetdb::server::database: manage puppetdb database ini
• puppetdb::server::firewall: manage puppetdb firewall rules
• puppetdb::server::global: manage puppetdb global setting
• puppetdb::server::jetty: configures puppetdb jetty ini
• puppetdb::server::puppetdb: manage puppetdb ini
• puppetdb::server::read_database: manage puppetdb read_database ini
• puppetdb::server::validate_db: validates the database connection
• puppetdb::server::validate_read_db: validates the read only database connection

Defined types

Private Defined types

• puppetdb::database::default_read_grant: grant read permissions to $database_read_only_username by default, for new tables created by $database_username
• puppetdb::database::postgresql_ssl_rules: manage the pg_ident.conf and pg_hba.conf files
• puppetdb::database::read_grant: grant read-only permissions to $database_read_only_username for all objects in $schema of $database_name
• puppetdb::database::read_only_user: manage the creation of a read-only postgres users

Resource types

• puppetdb_conn_validator: Verify that a connection can be successfully established between a node and the puppetdb server. Its primary use is as a precondition to pre

Functions

• puppetdb::create_subsetting_resource_hash
• puppetdb::flatten_java_args

Data types

• Puppetdb::Ttl

Classes

puppetdb

manage PuppetDB

Parameters

The following parameters are available in the puppetdb class:

• listen_address
• listen_port
• disable_cleartext
• open_listen_port
• ssl_listen_address
• ssl_listen_port
• disable_ssl
• open_ssl_listen_port
• ssl_protocols
• postgresql_ssl_on
• postgresql_ssl_folder
• postgresql_ssl_cert_path
• postgresql_ssl_key_path
• postgresql_ssl_ca_cert_path
• cipher_suites
• migrate
• manage_dbserver
• manage_database
• manage_package_repo
• postgres_version
• database_host
• database_port
• database_username
• database_password
• manage_db_password
• database_name
• jdbc_ssl_properties
• database_listen_address
• database_validate
• node_ttl
• node_purge_ttl
• report_ttl
• facts_blacklist
• gc_interval
• node_purge_gc_batch_limit
• conn_max_age
• conn_lifetime
• puppetdb_package
• puppetdb_service
• puppetdb_service_status
• puppetdb_user
• puppetdb_group
• puppetdb_server
• confdir
• vardir
• java_args
• merge_default_java_args
• max_threads
• read_database_host
• read_database_port
• read_database_username
• read_database_password
• manage_read_db_password
• read_database_jdbc_ssl_properties
• read_database_validate
• read_database_name
• read_conn_max_age
• read_conn_lifetime
• ssl_dir
• ssl_set_cert_paths
• ssl_cert_path
• ssl_key_pk8_path
• ssl_key_path
• ssl_ca_cert_path
• ssl_deploy_certs
• ssl_key
• ssl_cert
• ssl_ca_cert
• manage_firewall
• command_threads
• concurrent_writes
• store_usage
• temp_usage
• disable_update_checking
• certificate_whitelist_file
• certificate_whitelist
• database_max_pool_size
• read_database_max_pool_size
• automatic_dlo_cleanup
• cleanup_timer_interval
• dlo_max_age
• java_bin
• postgresql_password_encryption

listen_address

Data type: Any

The address that the web server should bind to for HTTP requests. Defaults to localhost. Set to 0.0.0.0 to listen on all addresses.

Default value: $puppetdb::params::listen_address

listen_port

Data type: Any

The port on which the puppetdb web server should accept HTTP requests. Defaults to 8080.

Default value: $puppetdb::params::listen_port

disable_cleartext

Data type: Any

If true, the puppetdb web server will only serve HTTPS and not HTTP requests (defaults to false).

Default value: $puppetdb::params::disable_cleartext

open_listen_port

Data type: Any

If true, open the http_listen_port on the firewall. Defaults to false.

Default value: $puppetdb::params::open_listen_port

ssl_listen_address

Data type: Any

The address that the web server should bind to for HTTPS requests. Defaults to 0.0.0.0 to listen on all addresses.

Default value: $puppetdb::params::ssl_listen_address

ssl_listen_port

Data type: Any

The port on which the puppetdb web server should accept HTTPS requests. Defaults to 8081.

Default value: $puppetdb::params::ssl_listen_port

disable_ssl

Data type: Any

If true, the puppetdb web server will only serve HTTP and not HTTPS requests. Defaults to false.

Default value: $puppetdb::params::disable_ssl

open_ssl_listen_port

Data type: Any

If true, open the ssl_listen_port on the firewall. Defaults to undef.

Default value: $puppetdb::params::open_ssl_listen_port

ssl_protocols

Data type: Any

Specify the supported SSL protocols for PuppetDB (e.g. TLSv1, TLSv1.1, TLSv1.2.)

Default value: $puppetdb::params::ssl_protocols

postgresql_ssl_on

Data type: Any

If true, it configures SSL connections between PuppetDB and the PostgreSQL database. Defaults to false.

Default value: $puppetdb::params::postgresql_ssl_on

postgresql_ssl_folder

Data type: Any

Path to the Postgresql SSL folder.

Default value: $puppetdb::params::postgresql_ssl_folder

postgresql_ssl_cert_path

Data type: Any

Path to the Postgresql SSL certificate.

Default value: $puppetdb::params::postgresql_ssl_cert_path

postgresql_ssl_key_path

Data type: Any

Path to the Postgresql SSL key.

Default value: $puppetdb::params::postgresql_ssl_key_path

postgresql_ssl_ca_cert_path

Data type: Any

Path to the Postgresql SSL CA.

Default value: $puppetdb::params::postgresql_ssl_ca_cert_path

cipher_suites

Data type: Any

Configure jetty's supported cipher-suites (e.g. SSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384). Defaults to undef.

Default value: $puppetdb::params::cipher_suites

migrate

Data type: Any

If true, puppetdb will automatically migrate to the latest database format at startup. If false, if the database format supplied by this version of PuppetDB doesn't match the version expected (whether newer or older), PuppetDB will exit with an error status. Defaults to true.

Default value: $puppetdb::params::migrate

manage_dbserver

Data type: Any

If true, the PostgreSQL server will be managed by this module. Defaults to true.

Default value: $puppetdb::params::manage_dbserver

manage_database

Data type: Any

If true, the PostgreSQL database will be managed by this module. Defaults to true.

Default value: $puppetdb::params::manage_database

manage_package_repo

Data type: Any

If true, the official postgresql.org repo will be added and postgres won't be installed from the regular repository. Defaults to true.

Default value: $puppetdb::params::manage_pg_repo

postgres_version

Data type: Any

If the postgresql.org repo is installed, you can install several versions of postgres. Defaults to 11 with PuppetDB version 7.0.0 or newer, and 9.6 in older versions.

Default value: $puppetdb::params::postgres_version

database_host

Data type: Any

Hostname to use for the database connection. For single case installations this should be left as the default. Defaults to localhost.

Default value: $puppetdb::params::database_host

database_port

Data type: Any

The port that the database server listens on. Defaults to 5432.

Default value: $puppetdb::params::database_port

database_username

Data type: Any

The name of the database user to connect as. Defaults to puppetdb.

Default value: $puppetdb::params::database_username

database_password

Data type: Any

The password for the database user. Defaults to puppetdb.

Default value: $puppetdb::params::database_password

manage_db_password

Data type: Any

Whether or not the database password in database.ini will be managed by this module. Set this to false if you want to set the password some other way. Defaults to true

Default value: $puppetdb::params::manage_db_password

database_name

Data type: Any

The name of the database instance to connect to. Defaults to puppetdb.

Default value: $puppetdb::params::database_name

jdbc_ssl_properties

Data type: Any

The text to append to the JDBC connection URI. This should begin with a '?' character. For example, to use SSL for the PostgreSQL connection, set this parameter's value to ?ssl=true.

Default value: $puppetdb::params::jdbc_ssl_properties

database_listen_address

Data type: Any

A comma-separated list of hostnames or IP addresses on which the postgres server should listen for incoming connections. This defaults to localhost. This parameter maps directly to PostgreSQL's listen_addresses config option. Use a * to allow connections on any accessible address.

Default value: $puppetdb::params::postgres_listen_addresses

database_validate

Data type: Any

If true, the module will attempt to connect to the database using the specified settings and fail if it is not able to do so. Defaults to true.

Default value: $puppetdb::params::database_validate

node_ttl

Data type: Any

The length of time a node can go without receiving any new data before it's automatically deactivated. (defaults to '7d', which is a 7-day period. Set to '0d' to disable auto-deactivation). This option is supported in PuppetDB >= 1.1.0.

Default value: $puppetdb::params::node_ttl

node_purge_ttl

Data type: Any

The length of time a node can be deactivated before it's deleted from the database. (defaults to '14d', which is a 14-day period. Set to '0d' to disable purging). This option is supported in PuppetDB >= 1.2.0.

Default value: $puppetdb::params::node_purge_ttl

report_ttl

Data type: Any

The length of time reports should be stored before being deleted. (defaults to 14d, which is a 14-day period). This option is supported in PuppetDB >= 1.1.0.

Default value: $puppetdb::params::report_ttl

facts_blacklist

Data type: Optional[Array]

A list of fact names to be ignored whenever submitted.

Default value: $puppetdb::params::facts_blacklist

gc_interval

Data type: Any

This controls how often (in minutes) to compact the database. The compaction process reclaims space and deletes unnecessary rows. If not supplied, the default is every 60 minutes. This option is supported in PuppetDB >= 0.9.

Default value: $puppetdb::params::gc_interval

node_purge_gc_batch_limit

Data type: Any

Nodes will be purged in batches of this size, one batch per gc-interval.

Default value: $puppetdb::params::node_purge_gc_batch_limit

conn_max_age

Data type: Any

The maximum time (in minutes) for a pooled connection to remain unused before it is closed off.

If not supplied, we default to 60 minutes. This option is supported in PuppetDB >= 1.1.

Default value: $puppetdb::params::conn_max_age

conn_lifetime

Data type: Any

The maximum time (in minutes) a pooled connection should remain open. Any connections older than this setting will be closed off. Connections currently in use will not be affected until they are returned to the pool.

If not supplied, we won't terminate connections based on their age alone. This option is supported in PuppetDB >= 1.4.

Default value: $puppetdb::params::conn_lifetime

puppetdb_package

Data type: Any

The PuppetDB package name in the package manager. Defaults to present.

Default value: $puppetdb::params::puppetdb_package

puppetdb_service

Data type: Any

The name of the PuppetDB service. Defaults to puppetdb.

Default value: $puppetdb::params::puppetdb_service

puppetdb_service_status

Data type: Any

Sets whether the service should be running or stopped. When set to stopped the service doesn't start on boot either. Valid values are true, running, false, and stopped.

Default value: $puppetdb::params::puppetdb_service_status

puppetdb_user

Data type: Any

Puppetdb service user

Default value: $puppetdb::params::puppetdb_user

puppetdb_group

Data type: Any

Puppetdb service group

Default value: $puppetdb::params::puppetdb_group

puppetdb_server

Data type: Any

Puppetdb server hostname or IP address.

Default value: $puppetdb::params::puppetdb_server

confdir

Data type: Any

The PuppetDB configuration directory. Defaults to /etc/puppetdb/conf.d.

Default value: $puppetdb::params::confdir

vardir

Data type: Any

The parent directory for the MQ's data directory.

Default value: $puppetdb::params::vardir

java_args

Data type: Any

Java VM options used for overriding default Java VM options specified in PuppetDB package. Defaults to {}. See PuppetDB Configuration to get more details about the current defaults.

For example, to set -Xmx512m -Xms256m options use:

{
    '-Xmx' => '512m',
    '-Xms' => '256m',
}

Default value: $puppetdb::params::java_args

merge_default_java_args

Data type: Any

Sets whether the provided java args should be merged with the defaults, or should override the defaults. This setting is necessary if any of the defaults are to be removed. Defaults to true. If false, the java_args in the PuppetDB init config file will reflect only what is passed via the java_args param.

Default value: $puppetdb::params::merge_default_java_args

max_threads

Data type: Any

Jetty option to explicitly set max-threads. Defaults to undef, so the PuppetDB-Jetty default is used.

Default value: $puppetdb::params::max_threads

read_database_host

Data type: Any

This parameter must be set to use another PuppetDB instance for queries.

The hostname or IP address of the read database server. If set to undef, and manage_database is set to true, it will use the value of the database_host parameter. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_host

read_database_port

Data type: Any

The port that the read database server listens on. If read_database_host is set to undef, and manage_database is set to true, it will use the value of the database_port parameter. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_port

read_database_username

Data type: Any

The name of the read database user to connect as. Defaults to puppetdb-read. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_username

read_database_password

Data type: Any

The password for the read database user. Defaults to puppetdb-read. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_password

manage_read_db_password

Data type: Any

Whether or not the database password in read-database.ini will be managed by this module. Set this to false if you want to set the password some other way. Defaults to true

Default value: $puppetdb::params::manage_read_db_password

read_database_jdbc_ssl_properties

Data type: Any

The text to append to the JDBC connection URI. This should begin with a '?' character. For example, to use SSL for the PostgreSQL connection, set this parameter's value to ?ssl=true.

Default value: $puppetdb::params::read_database_jdbc_ssl_properties

read_database_validate

Data type: Any

If true, the module will attempt to connect to the database using the specified settings and fail if it is not able to do so. Defaults to true.

Default value: $puppetdb::params::read_database_validate

read_database_name

Data type: Any

The name of the read database instance to connect to. If read_database_host is set to undef, and manage_database is set to true, it will use the value of the database_name parameter. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_name

read_conn_max_age

Data type: Any

The maximum time (in minutes) for a pooled read database connection to remain unused before it is closed off.

If not supplied, we default to 60 minutes. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_conn_max_age

read_conn_lifetime

Data type: Any

The maximum time (in minutes) a pooled read database connection should remain open. Any connections older than this setting will be closed off. Connections currently in use will not be affected until they are returned to the pool.

If not supplied, we won't terminate connections based on their age alone. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_conn_lifetime

ssl_dir

Data type: Any

Base directory for PuppetDB SSL configuration. Defaults to /etc/puppetdb/ssl or /etc/puppetlabs/puppetdb/ssl for FOSS and PE respectively.

Default value: $puppetdb::params::ssl_dir

ssl_set_cert_paths

Data type: Any

A switch to enable or disable the management of SSL certificates in your jetty.ini configuration file.

Default value: $puppetdb::params::ssl_set_cert_paths

ssl_cert_path

Data type: Any

Path to your SSL certificate for populating jetty.ini.

Default value: $puppetdb::params::ssl_cert_path

ssl_key_pk8_path

Data type: Any

Path to the SSL pk8 key for populating jetty.ini, will be generated from the SSL key as needed automatically.

Default value: $puppetdb::params::ssl_key_pk8_path

ssl_key_path

Data type: Any

Path to your SSL key for populating jetty.ini.

Default value: $puppetdb::params::ssl_key_path

ssl_ca_cert_path

Data type: Any

Path to your SSL CA for populating jetty.ini.

Default value: $puppetdb::params::ssl_ca_cert_path

ssl_deploy_certs

Data type: Any

A boolean switch to enable or disable the management of SSL keys in your ssl_dir. Default is false.

Default value: $puppetdb::params::ssl_deploy_certs

ssl_key

Data type: Any

Contents of your SSL key, as a string.

Default value: $puppetdb::params::ssl_key

ssl_cert

Data type: Any

Contents of your SSL certificate, as a string.

Default value: $puppetdb::params::ssl_cert

ssl_ca_cert

Data type: Any

Contents of your SSL CA certificate, as a string.

Default value: $puppetdb::params::ssl_ca_cert

manage_firewall

Data type: Any

If true, puppet will manage your iptables rules for PuppetDB via the puppetlabs-firewall class.

Default value: $puppetdb::params::manage_firewall

command_threads

Data type: Any

The number of command processing threads to use. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::command_threads

concurrent_writes

Data type: Any

The number of threads allowed to write to disk at any one time. Defaults to undef, which uses the PuppetDB built-in default.

Default value: $puppetdb::params::concurrent_writes

store_usage

Data type: Any

The amount of disk space (in MB) to allow for persistent message storage. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::store_usage

temp_usage

Data type: Any

The amount of disk space (in MB) to allow for temporary message storage. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::temp_usage

disable_update_checking

Data type: Any

Setting this to true disables checking for updated versions of PuppetDB and sending basic analytics data to Puppet. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::disable_update_checking

certificate_whitelist_file

Data type: Any

The name of the certificate whitelist file to set up and configure in PuppetDB. Defaults to /etc/puppetdb/certificate-whitelist or /etc/puppetlabs/puppetdb/certificate-whitelist for FOSS and PE respectively.

Default value: $puppetdb::params::certificate_whitelist_file

certificate_whitelist

Data type: Any

Array of the X.509 certificate Common Names of clients allowed to connect to PuppetDB. Defaults to empty. Be aware that this permits full access to all Puppet clients to download anything contained in PuppetDB, including the full catalogs of all nodes, which possibly contain sensitive information. Set to [ $::servername ] to allow access only from your (single) Puppet master, which is enough for normal operation. Set to a list of Puppet masters if you have multiple.

Default value: $puppetdb::params::certificate_whitelist

database_max_pool_size

Data type: Any

When the pool reaches this size, and no idle connections are available, attempts to get a connection will wait for connection-timeout milliseconds before timing out. Note that PuppetDB will use one pool for writes and another for reads, so the total number of connections used will be twice this setting.

Default value: $puppetdb::params::database_max_pool_size

read_database_max_pool_size

Data type: Any

When the pool reaches this size, and no idle connections are available, attempts to get a connection will wait for connection-timeout milliseconds before timing out. Note that PuppetDB will use one pool for writes and another for reads, so the total number of connections used will be twice this setting.

Default value: $puppetdb::params::read_database_max_pool_size

automatic_dlo_cleanup

Data type: Boolean

PuppetDB creates Dead Letter Office. Those are reports of failed requests. They spill up the disk. This parameter is a boolean and defaults to false. You can enable automatic cleanup of DLO reports by setting this to true.

Default value: $puppetdb::params::automatic_dlo_cleanup

cleanup_timer_interval

Data type: String[1]

The DLO cleanup is a systemd timer if systemd is available, otherwise a cronjob. The variable configures the systemd.timer option onCalender. It defaults to *-*-* ${fqdn_rand(24)}:${fqdn_rand(60)}:00. This will start the cleanup service on a daily basis. The exact minute and hour is random per node based on the fqdn_rand method. On non-systemd systems, the cron runs daily and the $puppetdb_user needs to be able to run cron jobs. On systemd systems you need the camptocamp/systemd module, which is an optional dependency and not automatically installed!

Default value: $puppetdb::params::cleanup_timer_interval

dlo_max_age

Data type: Integer[1]

This is a positive integer. It describes the amount of days you want to keep the DLO reports. The default value is 90 days.

Default value: $puppetdb::params::dlo_max_age

java_bin

Data type: Optional[Stdlib::Absolutepath]

java binary path for PuppetDB. If undef, default will be used.

Default value: $puppetdb::params::java_bin

postgresql_password_encryption

Data type: Postgresql::Pg_password_encryption

PostgreSQL password authentication method, either md5 or scram-sha-256

Default value: $puppetdb::params::password_encryption

puppetdb::database::postgresql

create the PuppetDB postgresql database

Parameters

The following parameters are available in the puppetdb::database::postgresql class:

• listen_addresses
• puppetdb_server
• database_name
• database_username
• database_password
• database_port
• manage_database
• manage_server
• manage_package_repo
• postgres_version
• postgresql_ssl_on
• postgresql_ssl_cert_path
• postgresql_ssl_key_path
• postgresql_ssl_ca_cert_path
• read_database_username
• read_database_password
• read_database_host
• password_sensitive
• password_encryption

listen_addresses

Data type: Any

The listen_address is a comma-separated list of hostnames or IP addresses on which the postgres server should listen for incoming connections. This defaults to localhost. This parameter maps directly to PostgreSQL's listen_addresses config option. Use a * to allow connections on any accessible address.

Default value: $puppetdb::params::database_host

puppetdb_server

Data type: Any

Hostname or IP address to configure for SSL rules.

Default value: $puppetdb::params::puppetdb_server

database_name

Data type: Any

Sets the name of the database. Defaults to puppetdb.

Default value: $puppetdb::params::database_name

database_username

Data type: Any

Creates a user for access the database. Defaults to puppetdb.

Default value: $puppetdb::params::database_username

database_password

Data type: Any

Sets the password for the database user above. Defaults to puppetdb.

Default value: $puppetdb::params::database_password

database_port

Data type: Any

The port that the database server listens on. Defaults to 5432.

Default value: $puppetdb::params::database_port

manage_database

Data type: Any

If true, the PostgreSQL database will be managed by this module. Defaults to true.

Default value: $puppetdb::params::manage_database

manage_server

Data type: Any

Conditionally manages the PostgreSQL server via postgresql::server. Defaults to true. If set to false, this class will create the database and user via postgresql::server::db but not attempt to install or manage the server itself.

Default value: $puppetdb::params::manage_dbserver

manage_package_repo

Data type: Any

If true, the official postgresql.org repo will be added and postgres won't be installed from the regular repository. Defaults to true.

Default value: $puppetdb::params::manage_pg_repo

postgres_version

Data type: Any

If the postgresql.org repo is installed, you can install several versions of postgres. Defaults to 11 with PuppetDB version 7.0.0 or newer, and 9.6 in older versions.

Default value: $puppetdb::params::postgres_version

postgresql_ssl_on

Data type: Any

If true, it configures SSL connections between PuppetDB and the PostgreSQL database. Defaults to false.

Default value: $puppetdb::params::postgresql_ssl_on

postgresql_ssl_cert_path

Data type: Any

Path to the Postgresql SSL certificate.

Default value: $puppetdb::params::postgresql_ssl_cert_path

postgresql_ssl_key_path

Data type: Any

Path to the Postgresql SSL key.

Default value: $puppetdb::params::postgresql_ssl_key_path

postgresql_ssl_ca_cert_path

Data type: Any

Path to the Postgresql SSL CA.

Default value: $puppetdb::params::postgresql_ssl_ca_cert_path

read_database_username

Data type: Any

The name of the read database user to connect as. Defaults to puppetdb-read. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_username

read_database_password

Data type: Any

The password for the read database user. Defaults to puppetdb-read. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_password

read_database_host

Data type: Any

This parameter must be set to use another PuppetDB instance for queries.

The hostname or IP address of the read database server. If set to undef, and manage_database is set to true, it will use the value of the database_host parameter. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_host

password_sensitive

Data type: Boolean

Whether password should be of Datatype Sensitive[String]

Default value: false

password_encryption

Data type: Postgresql::Pg_password_encryption

PostgreSQL password authentication method, either md5 or scram-sha-256

Default value: $puppetdb::params::password_encryption

puppetdb::globals

global configuration class for PuppetDB

Parameters

The following parameters are available in the puppetdb::globals class:

• version
• puppet_confdir

version

Data type: Any

The version of the puppetdb package that should be installed. You may specify an explicit version number, 'present', or 'latest' (defaults to 'present').

Default value: 'present'

puppet_confdir

Data type: Stdlib::Absolutepath

Puppet's config directory. Defaults to /etc/puppetlabs/puppet.

Default value: $settings::confdir

puppetdb::master::config

manage the puppet configuration on the primary

Parameters

The following parameters are available in the puppetdb::master::config class:

• puppetdb_server
• puppetdb_port
• puppetdb_disable_ssl
• puppetdb_soft_write_failure
• manage_routes
• manage_storeconfigs
• manage_report_processor
• manage_config
• create_puppet_service_resource
• strict_validation
• enable_reports
• enable_storeconfigs
• puppet_confdir
• puppet_conf
• masterless
• terminus_package
• puppet_service_name
• puppetdb_startup_timeout
• test_url
• restart_puppet

puppetdb_server

Data type: Any

The dns name or ip of the PuppetDB server. Defaults to the hostname of the current node, i.e. $::fqdn.

Default value: fact('networking.fqdn')

puppetdb_port

Data type: Any

The port that the PuppetDB server is running on. Defaults to 8081.

Default value:

defined(Class['puppetdb']) ? {
    true    => $puppetdb::disable_ssl ? {
      true => 8080,
      default => 8081,
    },
    default => 8081

puppetdb_disable_ssl

Data type: Any

If true, use plain HTTP to talk to PuppetDB. Defaults to the value of disable_ssl if PuppetDB is on the same server as the Puppet Master, or else false. If you set this, you probably need to set puppetdb_port to match the HTTP port of the PuppetDB.

Default value:

defined(Class['puppetdb']) ? {
    true    => $puppetdb::disable_ssl,
    default => false

puppetdb_soft_write_failure

Data type: Any

Boolean to fail in a soft manner if PuppetDB is not accessible for command submission Defaults to false.

Default value: false

manage_routes

Data type: Any

If true, the module will overwrite the Puppet master's routes file to configure it to use PuppetDB. Defaults to true.

Default value: true

manage_storeconfigs

Data type: Any

If true, the module will manage the Puppet master's storeconfig settings. Defaults to true.

Default value: true

manage_report_processor

Data type: Any

If true, the module will manage the 'reports' field in the puppet.conf file to enable or disable the PuppetDB report processor. Defaults to false.

Default value: false

manage_config

Data type: Any

If true, the module will store values from puppetdb_server and puppetdb_port parameters in the PuppetDB configuration file. If false, an existing PuppetDB configuration file will be used to retrieve server and port values.

Default value: true

create_puppet_service_resource

Data type: Any

If true, AND if restart_puppet is true, then the module will create a service resource for puppet_service_name if it has not been defined. Defaults to true. If you are already declaring the puppet_service_name service resource in another part of your code, setting this to false will avoid creation of that service resource by this module, avoiding potential duplicate resource errors.

Default value: true

strict_validation

Data type: Any

If true, the module will fail if PuppetDB is not reachable, otherwise it will preconfigure PuppetDB without checking.

Default value: true

enable_reports

Data type: Any

Ignored unless manage_report_processor is true, in which case this setting will determine whether or not the PuppetDB report processor is enabled (true) or disabled (false) in the puppet.conf file.

Default value: false

enable_storeconfigs

Data type: Any

Ignored unless manage_storeconfigs is true, in which case this setting will determine whether or not client configuration storage is enabled (true) or disabled (false) in the puppet.conf file.

Default value: true

puppet_confdir

Data type: Any

Puppet's config directory. Defaults to /etc/puppetlabs/puppet.

Default value: $puppetdb::params::puppet_confdir

puppet_conf

Data type: Any

Puppet's config file. Defaults to ${puppet_confdir}/puppet.conf.

Default value: $puppetdb::params::puppet_conf

masterless

Data type: Any

A boolean switch to enable or disable the masterless setup of PuppetDB. Defaults to false.

Default value: $puppetdb::params::masterless

terminus_package

Data type: Any

Name of the package to use that represents the PuppetDB terminus code. Defaults to puppetdb-termini, when puppetdb_version is set to <= 2.3.x the default changes to puppetdb-terminus.

Default value: $puppetdb::params::terminus_package

puppet_service_name

Data type: Any

Name of the service that represents Puppet. You can change this to apache2 or httpd depending on your operating system, if you plan on having Puppet run using Apache/Passenger for example.

Default value: $puppetdb::params::puppet_service_name

puppetdb_startup_timeout

Data type: Any

The maximum amount of time that the module should wait for PuppetDB to start up. This is most important during the initial install of PuppetDB (defaults to 15 seconds).

Default value: $puppetdb::params::puppetdb_startup_timeout

test_url

Data type: Any

The URL to use for testing if the PuppetDB instance is running.

Default value: $puppetdb::params::test_url

restart_puppet

Data type: Any

If true, the module will restart the Puppet master when PuppetDB configuration files are changed by the module. Defaults to true. If set to false, you must restart the service manually in order to pick up changes to the config files (other than puppet.conf).

Default value: true

puppetdb::server

manage the PuppetDB server

Parameters

The following parameters are available in the puppetdb::server class:

• listen_address
• listen_port
• disable_cleartext
• open_listen_port
• ssl_listen_address
• ssl_listen_port
• disable_ssl
• open_ssl_listen_port
• ssl_protocols
• postgresql_ssl_on
• cipher_suites
• migrate
• manage_database
• database_host
• database_port
• database_username
• database_password
• manage_db_password
• database_name
• jdbc_ssl_properties
• database_validate
• node_ttl
• node_purge_ttl
• report_ttl
• facts_blacklist
• gc_interval
• node_purge_gc_batch_limit
• conn_max_age
• conn_lifetime
• puppetdb_package
• puppetdb_service
• puppetdb_service_status
• puppetdb_user
• puppetdb_group
• confdir
• vardir
• java_args
• merge_default_java_args
• max_threads
• read_database_host
• read_database_port
• read_database_username
• read_database_password
• manage_read_db_password
• read_database_jdbc_ssl_properties
• read_database_validate
• read_database_name
• read_conn_max_age
• read_conn_lifetime
• ssl_dir
• ssl_set_cert_paths
• ssl_cert_path
• ssl_key_pk8_path
• ssl_key_path
• ssl_ca_cert_path
• ssl_deploy_certs
• ssl_key
• ssl_cert
• ssl_ca_cert
• manage_firewall
• command_threads
• concurrent_writes
• store_usage
• temp_usage
• disable_update_checking
• certificate_whitelist_file
• certificate_whitelist
• database_max_pool_size
• read_database_max_pool_size
• automatic_dlo_cleanup
• cleanup_timer_interval
• dlo_max_age
• java_bin

listen_address

Data type: Any

The address that the web server should bind to for HTTP requests. Defaults to localhost. Set to 0.0.0.0 to listen on all addresses.

Default value: $puppetdb::params::listen_address

listen_port

Data type: Any

The port on which the puppetdb web server should accept HTTP requests. Defaults to 8080.

Default value: $puppetdb::params::listen_port

disable_cleartext

Data type: Any

If true, the puppetdb web server will only serve HTTPS and not HTTP requests (defaults to false).

Default value: $puppetdb::params::disable_cleartext

open_listen_port

Data type: Any

If true, open the http_listen_port on the firewall. Defaults to false.

Default value: $puppetdb::params::open_listen_port

ssl_listen_address

Data type: Any

The address that the web server should bind to for HTTPS requests. Defaults to 0.0.0.0 to listen on all addresses.

Default value: $puppetdb::params::ssl_listen_address

ssl_listen_port

Data type: Any

The port on which the puppetdb web server should accept HTTPS requests. Defaults to 8081.

Default value: $puppetdb::params::ssl_listen_port

disable_ssl

Data type: Any

If true, the puppetdb web server will only serve HTTP and not HTTPS requests. Defaults to false.

Default value: $puppetdb::params::disable_ssl

open_ssl_listen_port

Data type: Any

If true, open the ssl_listen_port on the firewall. Defaults to undef.

Default value: $puppetdb::params::open_ssl_listen_port

ssl_protocols

Data type: Any

Specify the supported SSL protocols for PuppetDB (e.g. TLSv1, TLSv1.1, TLSv1.2.)

Default value: $puppetdb::params::ssl_protocols

postgresql_ssl_on

Data type: Any

If true, it configures SSL connections between PuppetDB and the PostgreSQL database. Defaults to false.

Default value: $puppetdb::params::postgresql_ssl_on

cipher_suites

Data type: Any

Configure jetty's supported cipher-suites (e.g. SSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384). Defaults to undef.

Default value: $puppetdb::params::cipher_suites

migrate

Data type: Any

If true, puppetdb will automatically migrate to the latest database format at startup. If false, if the database format supplied by this version of PuppetDB doesn't match the version expected (whether newer or older), PuppetDB will exit with an error status. Defaults to true.

Default value: $puppetdb::params::migrate

manage_database

Data type: Any

If true, the PostgreSQL database will be managed by this module. Defaults to true.

Default value: $puppetdb::params::manage_database

database_host

Data type: Any

Hostname to use for the database connection. For single case installations this should be left as the default. Defaults to localhost.

Default value: $puppetdb::params::database_host

database_port

Data type: Any

The port that the database server listens on. Defaults to 5432.

Default value: $puppetdb::params::database_port

database_username

Data type: Any

The name of the database user to connect as. Defaults to puppetdb.

Default value: $puppetdb::params::database_username

database_password

Data type: Any

The password for the database user. Defaults to puppetdb.

Default value: $puppetdb::params::database_password

manage_db_password

Data type: Any

Whether or not the database password in database.ini will be managed by this module. Set this to false if you want to set the password some other way. Defaults to true

Default value: $puppetdb::params::manage_db_password

database_name

Data type: Any

The name of the database instance to connect to. Defaults to puppetdb.

Default value: $puppetdb::params::database_name

jdbc_ssl_properties

Data type: Any

The text to append to the JDBC connection URI. This should begin with a '?' character. For example, to use SSL for the PostgreSQL connection, set this parameter's value to ?ssl=true.

Default value: $puppetdb::params::jdbc_ssl_properties

database_validate

Data type: Any

If true, the module will attempt to connect to the database using the specified settings and fail if it is not able to do so. Defaults to true.

Default value: $puppetdb::params::database_validate

node_ttl

Data type: Any

The length of time a node can go without receiving any new data before it's automatically deactivated. (defaults to '7d', which is a 7-day period. Set to '0d' to disable auto-deactivation). This option is supported in PuppetDB >= 1.1.0.

Default value: $puppetdb::params::node_ttl

node_purge_ttl

Data type: Any

The length of time a node can be deactivated before it's deleted from the database. (defaults to '14d', which is a 14-day period. Set to '0d' to disable purging). This option is supported in PuppetDB >= 1.2.0.

Default value: $puppetdb::params::node_purge_ttl

report_ttl

Data type: Any

The length of time reports should be stored before being deleted. (defaults to 14d, which is a 14-day period). This option is supported in PuppetDB >= 1.1.0.

Default value: $puppetdb::params::report_ttl

facts_blacklist

Data type: Optional[Array]

A list of fact names to be ignored whenever submitted.

Default value: $puppetdb::params::facts_blacklist

gc_interval

Data type: Any

This controls how often (in minutes) to compact the database. The compaction process reclaims space and deletes unnecessary rows. If not supplied, the default is every 60 minutes. This option is supported in PuppetDB >= 0.9.

Default value: $puppetdb::params::gc_interval

node_purge_gc_batch_limit

Data type: Any

Nodes will be purged in batches of this size, one batch per gc-interval.

Default value: $puppetdb::params::node_purge_gc_batch_limit

conn_max_age

Data type: Any

The maximum time (in minutes) for a pooled connection to remain unused before it is closed off.

If not supplied, we default to 60 minutes. This option is supported in PuppetDB >= 1.1.

Default value: $puppetdb::params::conn_max_age

conn_lifetime

Data type: Any

The maximum time (in minutes) a pooled connection should remain open. Any connections older than this setting will be closed off. Connections currently in use will not be affected until they are returned to the pool.

If not supplied, we won't terminate connections based on their age alone. This option is supported in PuppetDB >= 1.4.

Default value: $puppetdb::params::conn_lifetime

puppetdb_package

Data type: Any

The PuppetDB package name in the package manager. Defaults to present.

Default value: $puppetdb::params::puppetdb_package

puppetdb_service

Data type: Any

The name of the PuppetDB service. Defaults to puppetdb.

Default value: $puppetdb::params::puppetdb_service

puppetdb_service_status

Data type: Any

Sets whether the service should be running or stopped. When set to stopped the service doesn't start on boot either. Valid values are true, running, false, and stopped.

Default value: $puppetdb::params::puppetdb_service_status

puppetdb_user

Data type: Any

Puppetdb service user

Default value: $puppetdb::params::puppetdb_user

puppetdb_group

Data type: Any

Puppetdb service group

Default value: $puppetdb::params::puppetdb_group

confdir

Data type: Any

The PuppetDB configuration directory. Defaults to /etc/puppetdb/conf.d.

Default value: $puppetdb::params::confdir

vardir

Data type: Any

The parent directory for the MQ's data directory.

Default value: $puppetdb::params::vardir

java_args

Data type: Any

Java VM options used for overriding default Java VM options specified in PuppetDB package. Defaults to {}. See PuppetDB Configuration to get more details about the current defaults.

For example, to set -Xmx512m -Xms256m options use:

{
    '-Xmx' => '512m',
    '-Xms' => '256m',
}

Default value: $puppetdb::params::java_args

merge_default_java_args

Data type: Any

Sets whether the provided java args should be merged with the defaults, or should override the defaults. This setting is necessary if any of the defaults are to be removed. Defaults to true. If false, the java_args in the PuppetDB init config file will reflect only what is passed via the java_args param.

Default value: $puppetdb::params::merge_default_java_args

max_threads

Data type: Any

Jetty option to explicitly set max-threads. Defaults to undef, so the PuppetDB-Jetty default is used.

Default value: $puppetdb::params::max_threads

read_database_host

Data type: Any

This parameter must be set to use another PuppetDB instance for queries.

The hostname or IP address of the read database server. If set to undef, and manage_database is set to true, it will use the value of the database_host parameter. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_host

read_database_port

Data type: Any

The port that the read database server listens on. If read_database_host is set to undef, and manage_database is set to true, it will use the value of the database_port parameter. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_port

read_database_username

Data type: Any

The name of the read database user to connect as. Defaults to puppetdb-read. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_username

read_database_password

Data type: Any

The password for the read database user. Defaults to puppetdb-read. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_password

manage_read_db_password

Data type: Any

Whether or not the database password in read-database.ini will be managed by this module. Set this to false if you want to set the password some other way. Defaults to true

Default value: $puppetdb::params::manage_read_db_password

read_database_jdbc_ssl_properties

Data type: Any

The text to append to the JDBC connection URI. This should begin with a '?' character. For example, to use SSL for the PostgreSQL connection, set this parameter's value to ?ssl=true.

Default value: $puppetdb::params::read_database_jdbc_ssl_properties

read_database_validate

Data type: Any

If true, the module will attempt to connect to the database using the specified settings and fail if it is not able to do so. Defaults to true.

Default value: $puppetdb::params::read_database_validate

read_database_name

Data type: Any

The name of the read database instance to connect to. If read_database_host is set to undef, and manage_database is set to true, it will use the value of the database_name parameter. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_database_name

read_conn_max_age

Data type: Any

The maximum time (in minutes) for a pooled read database connection to remain unused before it is closed off.

If not supplied, we default to 60 minutes. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_conn_max_age

read_conn_lifetime

Data type: Any

The maximum time (in minutes) a pooled read database connection should remain open. Any connections older than this setting will be closed off. Connections currently in use will not be affected until they are returned to the pool.

If not supplied, we won't terminate connections based on their age alone. This option is supported in PuppetDB >= 1.6.

Default value: $puppetdb::params::read_conn_lifetime

ssl_dir

Data type: Stdlib::Absolutepath

Base directory for PuppetDB SSL configuration. Defaults to /etc/puppetdb/ssl or /etc/puppetlabs/puppetdb/ssl for FOSS and PE respectively.

Default value: $puppetdb::params::ssl_dir

ssl_set_cert_paths

Data type: Boolean

A switch to enable or disable the management of SSL certificates in your jetty.ini configuration file.

Default value: $puppetdb::params::ssl_set_cert_paths

ssl_cert_path

Data type: Stdlib::Absolutepath

Path to your SSL certificate for populating jetty.ini.

Default value: $puppetdb::params::ssl_cert_path

ssl_key_pk8_path

Data type: Stdlib::Absolutepath

Path to the SSL pk8 key for populating jetty.ini, will be generated from the SSL key as needed automatically.

Default value: $puppetdb::params::ssl_key_pk8_path

ssl_key_path

Data type: Stdlib::Absolutepath

Path to your SSL key for populating jetty.ini.

Default value: $puppetdb::params::ssl_key_path

ssl_ca_cert_path

Data type: Stdlib::Absolutepath

Path to your SSL CA for populating jetty.ini.

Default value: $puppetdb::params::ssl_ca_cert_path

ssl_deploy_certs

Data type: Boolean

A boolean switch to enable or disable the management of SSL keys in your ssl_dir. Default is false.

Default value: $puppetdb::params::ssl_deploy_certs

ssl_key

Data type: Any

Contents of your SSL key, as a string.

Default value: $puppetdb::params::ssl_key

ssl_cert

Data type: Any

Contents of your SSL certificate, as a string.

Default value: $puppetdb::params::ssl_cert

ssl_ca_cert

Data type: Any

Contents of your SSL CA certificate, as a string.

Default value: $puppetdb::params::ssl_ca_cert

manage_firewall

Data type: Any

If true, puppet will manage your iptables rules for PuppetDB via the puppetlabs-firewall class.

Default value: $puppetdb::params::manage_firewall

command_threads

Data type: Any

The number of command processing threads to use. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::command_threads

concurrent_writes

Data type: Any

The number of threads allowed to write to disk at any one time. Defaults to undef, which uses the PuppetDB built-in default.

Default value: $puppetdb::params::concurrent_writes

store_usage

Data type: Any

The amount of disk space (in MB) to allow for persistent message storage. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::store_usage

temp_usage

Data type: Any

The amount of disk space (in MB) to allow for temporary message storage. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::temp_usage

disable_update_checking

Data type: Any

Setting this to true disables checking for updated versions of PuppetDB and sending basic analytics data to Puppet. Defaults to undef, using the PuppetDB built-in default.

Default value: $puppetdb::params::disable_update_checking

certificate_whitelist_file

Data type: Any

The name of the certificate whitelist file to set up and configure in PuppetDB. Defaults to /etc/puppetdb/certificate-whitelist or /etc/puppetlabs/puppetdb/certificate-whitelist for FOSS and PE respectively.

Default value: $puppetdb::params::certificate_whitelist_file

certificate_whitelist

Data type: Any

Array of the X.509 certificate Common Names of clients allowed to connect to PuppetDB. Defaults to empty. Be aware that this permits full access to all Puppet clients to download anything contained in PuppetDB, including the full catalogs of all nodes, which possibly contain sensitive information. Set to [ $::servername ] to allow access only from your (single) Puppet master, which is enough for normal operation. Set to a list of Puppet masters if you have multiple.

Default value: $puppetdb::params::certificate_whitelist

database_max_pool_size

Data type: Any

When the pool reaches this size, and no idle connections are available, attempts to get a connection will wait for connection-timeout milliseconds before timing out. Note that PuppetDB will use one pool for writes and another for reads, so the total number of connections used will be twice this setting.

Default value: $puppetdb::params::database_max_pool_size

read_database_max_pool_size

Data type: Any

When the pool reaches this size, and no idle connections are available, attempts to get a connection will wait for connection-timeout milliseconds before timing out. Note that PuppetDB will use one pool for writes and another for reads, so the total number of connections used will be twice this setting.

Default value: $puppetdb::params::read_database_max_pool_size

automatic_dlo_cleanup

Data type: Boolean

PuppetDB creates Dead Letter Office. Those are reports of failed requests. They spill up the disk. This parameter is a boolean and defaults to false. You can enable automatic cleanup of DLO reports by setting this to true.

Default value: $puppetdb::params::automatic_dlo_cleanup

cleanup_timer_interval

Data type: String[1]

The DLO cleanup is a systemd timer if systemd is available, otherwise a cronjob. The variable configures the systemd.timer option onCalender. It defaults to *-*-* ${fqdn_rand(24)}:${fqdn_rand(60)}:00. This will start the cleanup service on a daily basis. The exact minute and hour is random per node based on the fqdn_rand method. On non-systemd systems, the cron runs daily and the $puppetdb_user needs to be able to run cron jobs. On systemd systems you need the camptocamp/systemd module, which is an optional dependency and not automatically installed!

Default value: $puppetdb::params::cleanup_timer_interval

dlo_max_age

Data type: Integer[1]

This is a positive integer. It describes the amount of days you want to keep the DLO reports. The default value is 90 days.

Default value: $puppetdb::params::dlo_max_age

java_bin

Data type: Optional[Stdlib::Absolutepath]

java binary path for PuppetDB. If undef, default will be used.

Default value: $puppetdb::params::java_bin

Resource types

puppetdb_conn_validator

Verify that a connection can be successfully established between a node and the puppetdb server. Its primary use is as a precondition to prevent configuration changes from being applied if the puppetdb server cannot be reached, but it could potentially be used for other purposes such as monitoring.

Properties

The following properties are available in the puppetdb_conn_validator type.

ensure

Valid values: present, absent

The basic property that the resource should be in.

Default value: present

Parameters

The following parameters are available in the puppetdb_conn_validator type.

• name
• provider
• puppetdb_port
• puppetdb_server
• test_url
• timeout
• use_ssl

name

namevar

An arbitrary name used as the identity of the resource.

provider

The specific backend to use for this puppetdb_conn_validator resource. You will seldom need to specify this --- Puppet will usually discover the appropriate provider for your platform.

puppetdb_port

The port that the puppetdb server should be listening on.

puppetdb_server

The DNS name or IP address of the server where puppetdb should be running.

test_url

URL to use for testing if the PuppetDB database is up

timeout

The max number of seconds that the validator should wait before giving up and deciding that puppetdb is not running; defaults to 15 seconds.

Default value: 15

use_ssl

Whether the connection will be attempted using https

Default value: true

Functions

puppetdb::create_subsetting_resource_hash

Type: Ruby 4.x API

The puppetdb::create_subsetting_resource_hash function.

puppetdb::create_subsetting_resource_hash(Hash $java_args, Any $params)

The puppetdb::create_subsetting_resource_hash function.

Returns: Any

java_args

Data type: Hash

params

Data type: Any

puppetdb::flatten_java_args

Type: Ruby 4.x API

The puppetdb::flatten_java_args function.

puppetdb::flatten_java_args(Optional[Hash] $java_args)

The puppetdb::flatten_java_args function.

Returns: String

java_args

Data type: Optional[Hash]

Data types

Puppetdb::Ttl

The Puppetdb::Ttl data type.

Alias of Pattern[/^\d+(d|h|m|s|ms)$/]

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

v8.0.1 - 2024-05-02

Full Changelog

Fixed

• Fix lower bound the of puppetlabs-postgresql dependency #402 (smortex)

v8.0.0 - 2024-04-30

Full Changelog

Changed

• Drop support for Ubuntu 16 and Scientific Linux 7 #384 (h0tw1r3)
• Drop support for puppet < 7 #383 (h0tw1r3)
• Change default postgres version to 14 #379 (jonathannewman)
• Update firewall manifests to use jump instead of action #372 (david22swan)
• Remove obsolete database config options #357 (smokris)

Added

• Allow puppetlabs/firewall 8.x #395 (gcoxmoz)
• Make puppet_confdir configurable #376 (h0tw1r3)

Fixed

• Support scram-sha-256 password_encryption method #400 (deric)
• Fix custom database port support #392 (h0tw1r3)
• Correct clientcert value in pg_hba.conf for Postgresql >= 12 #380 (jhunt-steds)
• Unterminated quoted string when creating read user #371 (waipeng)
• Fix FreeBSD support #342 (smortex)

7.14.0 - 2023-10-09

Full Changelog

Changed

• Drop EoL Debian 8/9 #347 (bastelfreak)
• Drop EoL CentOS 6 #346 (bastelfreak)

Added

• Relax dependency requirements #367 (smortex)
• Allow newer dependencies #364 (saz)
• Set owner of server config.ini to root #358 (ekohl)

Fixed

• Fix "has no parameter named 'puppetdb_user'" #369 (cocker-cc)

7.13.0 - 2023-04-19

Full Changelog

Fixed

• (PDB-5611) Update legacy facts to structured form #362 (austb)

7.12.0 - 2022-12-13

Full Changelog

7.11.0 - 2022-12-12

Full Changelog

Added

• (PDB-5559) Grant read user to write user #361 (austb)
• Mark as compatible with puppetlabs/postgresql 8.x #353 (ekohl)

Fixed

• Fix legacy fact usage #355 (smortex)

7.10.0 - 2021-12-16

Full Changelog

Added

• (maint) Allow stdlib 8.0.0 #335 (smortex)
• (maint) Add support for Debian 11 #334 (smortex)
• (PDB-5052) Install PostgreSQL 11 for PDB > 7.0.0 #333 (oanatmaria)

Fixed

• Fix minimum version of puppetlabs/postgresql #332 (alexjfisher)

7.9.0 - 2021-06-24

Full Changelog

Added

• (maint) Add read-only user. #330 (Filipovici-Andrei)
• allow current versions of inifile, firewall, stdlib #327 (kenyon)

7.8.0 - 2021-03-25

Full Changelog

Added

• (SERVER-2500) Allow puppetlabs-postgresql 7.x #323 (Zak-Kent)
• (PDB-4764) Agent SSL certificates are used for communication with PostgreSQL #322 (Filipovici-Andrei)

7.7.1 - 2020-12-15

Full Changelog

Fixed

• Fix MODULES-10876 - use new client platform #315 (duritong)

7.7.0 - 2020-11-05

Full Changelog

Added

• (PDB-4945) Default to json fact cache #312 (joshcooper)
• Add options to set the source of the ssl certs #258 (edestecd)

7.6.0 - 2020-09-02

Full Changelog

Added

• Database migrate option #311 (csmithATsquiz)

7.5.0 - 2020-06-10

Full Changelog

Added

• Allow custom JAVA_BIN path #307 (bastelfreak)
• (MODULES-10675) enable facts-blacklist parameter in database.ini #305 (maxadamo)
• Add node-purge-gc-batch-limit as configurable #303 (synical)
• (PDB-2578) Allow the database password to be unmanaged #301 (natemccurdy)
• Support CentOS 8, OracleLinux 8 and Debian 10 & support pl/inifile 4.x #300 (ekohl)
• Create enable_storeconfigs option for puppet::master::config #298 (gcoxmoz)

7.4.0 - 2019-08-06

Full Changelog

Added

• Add possibilty to skip database creation in the module #296 (jhooyberghs)

7.3.0 - 2019-06-14

Full Changelog

Added

• allow newer versions of dependencies #295 (mmoll)

7.2.0 - 2019-05-17

Full Changelog

Added

• Allow inifile 3.x and postgresql 7.x #290 (ekohl)

7.1.0 - 2018-10-02

Full Changelog

Added

• (PDB-4092) Use vardir prefix for DLO path #285 (austb)

7.0.1 - 2018-07-30

Full Changelog

7.0.0 - 2018-07-26

Full Changelog

Changed

• Setup for 7.0.0 release #279 (Zak-Kent)

Added

• Add support for DLO automatic cleanup #278 (bastelfreak)

Fixed

• (FIX) Switch DLO to Puppet cron from cron::job #281 (austb)

6.0.2 - 2017-11-06

Full Changelog

Added

• (PDB-3654) bump version and ini file dep #274 (Zak-Kent)
• add explicit dependency db -> extension. #272 (pgassmann)
• (maint) bump inifile dependency #268 (eputnam)

6.0.1 - 2017-07-05

Full Changelog

6.0.0 - 2017-07-05

Full Changelog

Changed

• Default to postgres 9.6 #265 (mullr)

Added

• (PDB-3587) Add puppetlabs-postgresql 5.x support and integrate rspec-puppetfacts #260 (dhollinger)
• Add disable-update-checking parameter #257 (baurmatt)
• (PDB-3318) Better defaults for node-ttl, node-purge-ttl #254 (mullr)
• enable the master service when it is not defined #253 (tampakrap)
• add option to customize cipher suites in jetty #247 (selyx)
• Add support for Ruby 2.3.1 #246 (ghoneycutt)
• (PDB-3060) Add concurrent-writes parameter. #244 (aperiodic)
• set mode 0644 for routes.yaml #238 (tampakrap)
• (PDB-2660) Restart Puppet master after enabling reporting #234 (ajroetker)
• Manage the pool size configuration parameters in database.ini #232 (kpaulisse)
• (PDB-2571) Ensure puppetdb.ini file has correct permissions #228 (kbarber)
• Update postgresql.pp with postgresql contrib package #225 (PascalBourdier)

Fixed

• Fix duplicate resource errors for puppet service due to parse order #250 (kpaulisse)
• FIX: Unbreak on OpenBSD #233 (buzzdeee)
• (PDB-2696) Remove the dependency cycle cause by typo #231 (ajroetker)

5.1.2 - 2016-03-14

Full Changelog

5.1.1 - 2016-02-09

Full Changelog

5.1.0 - 2016-02-09

Full Changelog

Added

• Restrict access to the Puppet master by default #215 (michaelweiser)
• Add option to disable cleartext HTTP port #214 (michaelweiser)
• (PDB-1430) overwritable java_args #210 (wkalt)
• (PDB-1913) manage vardir #209 (wkalt)
• (PDB-1415) Add jdbc_ssl_properties parameter #206 (mullr)

Fixed

• MODULES-2488 Use dport instead of the now deprecated port parameter #205 (roman-mueller)
• Fix unmanaged postgresql database port #204 (earsdown)

5.0.0 - 2015-07-08

Full Changelog

4.3.0 - 2015-06-26

Full Changelog

Changed

• (PDB-1657) Manage Postgres repos by default #197 (ajroetker)
• (PDB-1035) Add default PuppetDB root context #181 (ajroetker)

Added

• (PDB-1455) Provide mechanism for modifying default HSQLDB path #185 (kbarber)
• Enable the module to manage entries in $confdir/config.ini #176 (buzzdeee)

Fixed

• (PDB-1467) Ordering problem with read_database_ini #180 (kbarber)

4.2.1 - 2015-04-08

Full Changelog

4.2.0 - 2015-04-02

Full Changelog

Added

• (PDB-1353) Use settings::confdir for puppet_confdir #172 (johnduarte)
• add FreeBSD support #171 (mmoll)
• Allow puppetdb to be configure for masterless conf #163 (Spredzy)
• add ability to manage postgres repo #162 (bastelfreak)
• Restart the service if certificates change #158 (dalen)
• Make database validation optional #157 (robinbowes)
• Show scheme (http/https) in puppetdb connection errors #155 (sathieu)

Fixed

• (bugfix) Use test_url in connection validator for puppetdb #169 (ajroetker)
• Fix separator in module name in metadata.json #164 (njm506)
• Remove unused parameters #161 (ekohl)
• add missing param manage_firewall #160 (bastelfreak)

4.1.0 - 2014-11-17

Full Changelog

Added

• Allow only TLS - Fixes POODLE CVE-2014-3566 #150 (ghoneycutt)

Fixed

• Remove invisible unicode character to prevent "invalid byte sequence in ... #149 (stefanandres)
• Fix detection of a PE-based PuppetDB #146 (seanmil)

4.0.0 - 2014-09-16

Full Changelog

Changed

• do not manage firewall for postgres, puppetlabs/postgres module from #135 (buzzdeee)

Added

• OpenBSD support #136 (buzzdeee)
• Add read-database support #132 (tdevelioglu)
• Allow set manage_server in init class #131 (baurmatt)
• implement max_threads option for jetty #130 (stefanandres)
• Allow more flexible routes configuration #127 (dalen)
• Add strict_variables support when puppetdb is not on puppetmaster #126 (mcanevet)
• Use $is_pe for PE determination #122 (reidmv)
• Parameter to not manage postgresql server #121 (jantman)
• Adding option to disable management of the firewall #119 (nibalizer)

Fixed

• Fixed read-database parameters in class puppetdb #134 (tdevelioglu)
• Ensure db and db users created before validation #125 (rickerc)
• Fix is_pe declaration so it works without is_pe #123 (kbarber)

3.0.1 - 2014-02-11

Full Changelog

Changed

• Use the /v2 metrics endpoint instead of /metrics #116 (kbarber)

Added

• Define parameter in puppetdb class to define postgres listen address #112 (adrianlzt)
• Concat update #101 (jhoblitt)

Fixed

• Fix puppetlabs#106 and one other bug when disable_ssl = true #107 (ebarrere)
• fix validation regular expressions #100 (ScottDuckworth)

3.0.0 - 2013-10-28

Full Changelog

Added

• (GH-93) Switch to using puppetlabs-postgresql 3.x #94 (kbarber)
• (GH-91) Update to use rspec-system-puppet 2.x #92 (kbarber)
• Add soft_write_failure to puppetdb.conf #89 (ghoneycutt)
• Add switch to configure database SSL connection #80 (stdietrich)

2.0.0 - 2013-10-18

Full Changelog

Added

• Enable service control for puppetdb #81 (ak0ska)
• add archlinux support #79 (aboe76)
• Make database_password an optional parameter #78 (nicklewis)

Fixed

• (GH-73) Switch to puppetlabs/inifile from cprice/inifile #74 (kbarber)

1.5.1 - 2013-08-12

Full Changelog

1.6.0 - 2013-08-09

Full Changelog

Added

• Add missing parameters for 1.4.0 release #76 (kbarber)

1.5.0 - 2013-07-18

Full Changelog

Changed

• Fix dependency for stdlib for 'downcase' #70 (kbarber)

Added

• Minor tweaks to make the module support SUSE #71 (cprice404)
• Allow puppetdb conn validation when ssl is disabled #68 (bodepd)
• Add support for enabling puppetdb report processor #64 (cprice404)

1.4.0 - 2013-05-28

Full Changelog

Changed

• Use fqdn for ssl listen address instead of clientcert #63 (cprice404)
• Increase default report-ttl to 14d #60 (cprice404)

Added

• Add support for enabling puppetdb report processor #64 (cprice404)
• Separate DB instance and DB user creation #61 (dalen)
• Add option to disable SSL in Jetty #52 (christianberg)
• allows for 0 _ttl's without time signifier and enables tests #50 (ghoneycutt)
• Support for remote puppetdb #41 (fhrbek)
• Added support for Java VM options #37 (kbrezina)

1.2.1 - 2013-04-08

Full Changelog

Added

• Add unit suffix to TTL settings to avoid issue #20099 #45 (domcleal)

1.2.0 - 2013-04-07

Full Changelog

Added

• Add params and ini_settings for node/report/purge ttls #35 (nicklewis)

1.1.5 - 2013-04-04

Full Changelog

Added

• Configuration improvements #36 (kbrezina)
• Bug/master/manage redhat firewall #30 (cprice404)

1.1.4 - 2013-01-17

Full Changelog

1.1.3 - 2013-01-15

Full Changelog

Added

• 17594 - PuppetDB - Add ability to set standard host listen address and open firewall to standard port #22 (dblessing)

1.1.2 - 2012-10-26

Full Changelog

1.1.1 - 2012-10-26

Full Changelog

1.1.0 - 2012-10-24

Full Changelog

Added

• Fix embedded db setup in Puppet Enterprise #19 (reidmv)
• Make puppetdb startup timeout configurable #18 (cprice404)
• Add condition to detect PE installations and provide different parameters #15 (hunner)
• Add parameters to enable usage of enterprise versions of PuppetDB #11 (cprice404)
• Add a parameter for restarting puppet master #9 (cprice404)

1.0.3 - 2012-09-23

Full Changelog

Added

• Add a parameter for restarting puppet master #9 (cprice404)

1.0.2 - 2012-09-21

Full Changelog

1.0.1 - 2012-09-20

Full Changelog

Fixed

• Fix duplicate stanza in database_ini.pp #8 (cprice404)
• Bug/master/db ini wrong db name #6 (cprice404)

1.0 - 2012-09-19

Full Changelog