Forge Home


Most modules are designed to configure things. This one is designed to break them.


6,540 latest version

3.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.0.3 (latest)
  • 0.0.2
  • 0.0.1
released Sep 12th 2016
This version is compatible with:
  • Puppet Enterprise >=3.0.0
  • Puppet >=3.0.0 <5.0.0
  • , , , , , , , ,

Start using this module

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

Add this module to your Puppetfile:

mod 'binford2k-wreckit', '0.0.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add binford2k-wreckit
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install binford2k-wreckit --version 0.0.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.



binford2k/wreckit — version 0.0.3 Sep 12th 2016


Most modules are designed to configure things. This one is designed to break them.

  1. Overview
  2. Usage
  3. Contributing


This module is intended as a learning tool. It will allow the victim, I mean user, to identify, troubleshoot, and recover from known error cases. The experience will help build troubleshooting skills and practice recovery from disaster.

This is designed to apply a random subset of a curated list of misconfigurations on the node it's enforced on. You should select how many scenarios you want to be applied, and what context to choose from. By default, it will apply a single randomly chosen scenario having to do with Puppet.

If you have successfully recovered from a scenario, and you'd like to attempt another challenge, simply increment the count number. It defaults to 1, so bump it to 2 when you're ready for another.


Default usage:

include wreckit

Specify parameters:

class { 'wreckit':
  count   => 3,
  context => 'puppet',

You can also specify which scenario(s) you want to be applied:

class { 'wreckit':
  scenario => 'wreckit::scenario::puppet::server',
class { 'wreckit':
  scenario => ['wreckit::scenario::puppet::server', 'wreckit::scenario::puppet::ssl'],

Apply the examples/available_scenarios.pp manifest to see what scenarios you can choose from.


This will be most fun if community members contribute some misconfiguration scenarios. Simply submit a pull request with a new wreckit::scenario::<context>::<something> class. The default context is puppet, but you're free to create any other context you like. For example, you may want to create a network context with scenarios to remote the default route or set an invalid DNS server or the like.

To be accepted, your class should:

  • Not make any changes that are irretrievable. If you destroy files, you should always back them up first. The $wreckit::backups variable is defined as the backup root. You should create files and directories under it for backup purposes.
  • Be enforceable in a single run. Your class will only be enforced once.

Your class should set the following variables for documentation:

  • Define a $description variable with information about the misconfiguration and why it's significant, or why it's commonly seen, etc.
  • Define a $recovery variable with instructions on recovering from whatever shenanigans your class pulled.
  • Define a $backup variable with information about any files that you backed up before mucking with them. Set to undef if you don't use this variable.
  • Define a $urls variable with any URLs the end user can visit for more information about whatever your misconfiguration was. Set to undef if you don't use this variable.

See the existing scenarios for examples.


I take no liability for the use of this module. It's in early stages of development.