rt

pdk
Module manages Request Tracker(https://bestpractical.com/rt-and-rtir/)

28,249 downloads

1,124 latest version

5.0 quality score

Version information

  • 0.1.3 (latest)
  • 0.1.2
  • 0.1.1
  • 0.1.0
released Aug 20th 2021
This version is compatible with:
  • Puppet Enterprise 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
  • Puppet >= 6.21.0 < 8.0.0
  • RedHat
    ,
    CentOS

Start using this module

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

Add this module to your Puppetfile:

mod 'abaranov-rt', '0.1.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add abaranov-rt
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install abaranov-rt --version 0.1.3

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

abaranov/rt — version 0.1.3 Aug 20th 2021

Puppet-RT Build Status

Table of Contents

  1. Description
  2. Setup - The basics of getting started 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