Forge Home

ping

Task to elicit a 'pong' from target systems

4,590 downloads

4,590 latest version

4.9 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

  • 1.0.0 (latest)
released Dec 10th 2018
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 4.7.0 < 7.0.0
  • Linux, Windows
Tasks:
  • ping

Start using this module

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

Add this module to your Puppetfile:

mod 'gabe-ping', '1.0.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add gabe-ping
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install gabe-ping --version 1.0.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

gabe/ping — version 1.0.0 Dec 10th 2018

Ping

This mind-bogglingly simple task simply replies to any invocation with a pong and an exit code of zero. The intention is to replace what you might have been using an mco ping for. Specifically, it's useful for validating that your transport and credentials (or RBAC) are valid, not just that the host is up or that its Puppet agent is checking in.

The output from Linux and Windows should be simply:

  {
    "reply": "pong"
  }