Forge Home

pbug

Debugging configurations for Puppet services

1,018 downloads

1,018 latest version

2.5 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.0 (latest)
released Mar 16th 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.16.0 < 8.0.0
  • , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'sharpie-pbug', '0.2.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add sharpie-pbug
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install sharpie-pbug --version 0.2.0

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

sharpie/pbug — version 0.2.0 Mar 16th 2021

PBUG

This project contains a Puppet module that automates the application of debugging configurations to Puppet and Puppet Enterprise services.

See the usage section for more details.

Requirements

This module is compatible with Puppet 6.16.0 and newer, which translates to PE 2019.8 and newer. Older versions of PE may work, but have not been tested.

Usage

pbug::mitmproxy

This class configures a SystemD service that uses mitmproxy to capture SSL traffic generated by local PE services for inspection.

Start the service with systemctl start mitmproxy and then visit http://<node ip address>:9080 to view captured traffic. Stop the service when debugging is finished, otherwise it will buffer traffic and consume resources until halted.