Forge Home


The te_agent module installs, configures, and manages the services of the Tripwire Enterprise Agent


6,658 latest version

4.3 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

  • 0.2.2 (latest)
  • 0.2.1
  • 0.2.0
released Sep 18th 2017
This version is compatible with:
  • Puppet Enterprise 2017.2.x, 2017.1.x, 2016.4.x
  • Puppet >= 4.9.0 < 5.0.0
  • RedHat, CentOS, Windows

Start using this module

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

Add this module to your Puppetfile:

mod 'tripwire-te_agent', '0.2.2'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add tripwire-te_agent
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install tripwire-te_agent --version 0.2.2

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.



tripwire/te_agent — version 0.2.2 Sep 18th 2017


Table of Contents

  1. Module Description - What the module does and why it is useful
  2. Setup - The basics of getting started with te_agent
  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.
  6. Development - Guide for contributing to the module

Module Description

The te_agent module installs, configures, and manages the services of the Tripwire Enterprise Agent.


Setup Requirements

The Tripwire Enterprise Agent needs a Tripwire Enterprise Console server to connect to. The server hostname and services passphrase are needed to configure the Agent.

The Agent install files must be staged somewhere on the target system. This can be a network drive, or you can use a separate file resource to manually copy the package files to the target system.

The MSI provider for Windows is a little more forgiving and may work with URLs or network drive paths.

Beginning with te_agent

At minimum, you must specify the hostname and services passphrase for the Tripwire Enterprise Console and the source path to the agent installer.

class { 'te_agent':
  package_source         => '/mnt/share/tripwire/te_agent.bin',
  te_server_host         => '',
  te_services_passphrase => 'correct horse battery staple',


All parameters for the te_agent module are contained within the main te_agent class, so for any function of the module, set the options you want. See the common usages below for examples.

Examples omit common parameters for brevity.

Staging the installer

file {'/tmp/te_agent.bin':
  ensure => file,
  mode   => '0700',
  source => ''
class { 'te_agent':
  package_source => '/tmp/te_agent.bin'

Setting Custom Tags

class { 'te_agent':
  tags => {
    'tagset_1' => 'tag1',
    'tagset_2' => ['tag2a', 'tag2b'],

Setting custom

class { 'te_agent':
  agent_properties => {
    'tw.launcher.debug'  => 'true',
    'tw.rmi.socketDebug' => 'true',


Available at

The full reference documentation can be generated with Puppet Strings:

$ bundle exec rake strings:generate

HTML documentation will be created under the ./doc/ directory.


The te_agent module was tested with Puppet 4.10, though it should work on 4.9 or later (or Puppet Enterprise 2017.1 or later).

The following Operating Systems have been tested with this module:

  • Red Hat 5, 6, 7
  • CentOS 5, 6, 7
  • Windows 7, 8.1, 10, Server 2008 R2, Server 2012 R2, Server 2016

Other versions may work if they are supported by both Puppet and the Tripwire Enterprise Agent.


See the contribution guidelines for more information.