spiped

contributions requested
spiped tunnel creator

10,478 downloads

7,621 latest version

4.3 quality score

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 1.1.1 (latest)
  • 1.0.1
released Jun 8th 2016

Start using this module

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

Add this module to your Puppetfile:

mod 'ckuehl-spiped', '1.1.1'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ckuehl-spiped
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ckuehl-spiped --version 1.1.1

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

ckuehl/spiped — version 1.1.1 Jun 8th 2016

puppet-spiped

Build Status

Puppet module for configuring spiped tunnels.

Requirements

  • Debian >= 8 / Ubuntu >= 15.04 / similar systems
  • systemd as init

The init requirement rules out many versions of Debian or Ubuntu. If you can't run systemd as init, this module is not useful to you.

Usage

For example, let's say we have a host redis-host which hosts a Redis database. Many clients will connect to it.

On redis-host, we would define a server tunnel:

spiped::tunnel::server { 'redis':
  source => '0.0.0.0:1234',
  dest   => '/var/run/redis.sock',
  secret => 'hunter2',
}

On clients, we would define a client tunnel:

spiped::tunnel::client { 'redis':
  source => '/var/run/redis.sock',
  dest   => 'redis-host:1234',
  secret => 'hunter2',
}

The secret is an arbitrarily-long shared symmetric key. The options above are the only supported; this module is kept as simple as possible.