Puppet-RT

Table of Contents

1. Description
2. Setup - The basics of getting started with puppet-rt
   • What puppet-rt affects
   • Setup requirements
   • Beginning with puppet-rt
3. Usage - Configuration options and additional functionality
4. Reference - An under-the-hood peek at what the module is doing and how
5. Limitations - OS compatibility, etc.

Overview

This module manages installation and configuration Request Tracker (RT) installation and configuration

Module Description

Module installs and configures RT.

Setup

What puppet-rt affects

• Module installs (including dependencies):

  • rt

  This can be overwritten using package parameter of rt class

• Modules manages files:

  • /etc/rt/RT_SiteConfig.pm
  • /etc/rt/RT_SiteConfig.d/*.pm

Setup Requirements

puppetlabs/stdlib

Beginning with puppet-rt

For a basic setup with a default configuration parameters it's just enough to declare rt class inside the manifest

include ::rt

Usage

To pass any configuration parameters the siteconfig hash parameter is used. siteconfig is merged with defaultsiteconfig from params.pp and pushed to /etc/rt/RT_SiteConfig.pm configuration file

siteconfig must be a hash that contains proper RT's configuration options:

rt::siteconfig:
  # Base configurations
  rtname: 'example.com'
  Organization: 'example'
  OwnerEmail: 'root@example.com'
  TimeZone: 'US/Pacific'
  # Web configurations
  WebPath: '/rt'
  WebDefaultStylesheet: 'web2'

include ::rt

The list of all options is available here: https://docs.bestpractical.com/rt/4.4.0/RT_Config.html

Configuration options can be managed using .pm files in /etc/rt/RTSiteConfig.d directory. This is implemented using _rt::siteconfig define.

rt::siteconfigs:
  rtname:
    value: 'example.com'
  WebPath:
    value: '/rt'

$siteconfigs = hiera('rt::siteconfigs', {})
validate_hash($siteconfigs)
create_resources('rt::siteconfig', $siteconfigs)

Reference

None

Limitations

• osfamily => RedHat
• if getenforce == Enforcing
  • setsebool -P httpd_can_sendmail 1 1