Forge Home


Puppet module to manage coreutils


8,630 latest version

2.8 quality score

Version information

  • 0.0.15 (latest)
  • 0.0.14
  • 0.0.13
  • 0.0.12
  • 0.0.11
  • 0.0.10
  • 0.0.9
  • 0.0.8
  • 0.0.7
released Jun 8th 2015
This version is compatible with:
  • ,

Start using this module

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

Add this module to your Puppetfile:

mod 'bi-bi_coreutils', '0.0.15'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add bi-bi_coreutils
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install bi-bi_coreutils --version 0.0.15

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.



bi/bi_coreutils — version 0.0.15 Jun 8th 2015

Table of Contents

  1. Overview
  2. Module Description - What the module does and why it is useful
  3. Setup - The basics of getting started with coreutils
  4. Usage - Configuration options and additional functionality
  5. Reference - An under-the-hood peek at what the module is doing and how
  6. Limitations - OS compatibility, etc.
  7. Development - Guide for contributing to the module


This modules has to main purposes:

  • Manage the static data associated with the coreutils package
  • Provide a wrapper around binaries in the coretutils package that are useful inside Puppet configuration

Module Description

The static data associated with the binaries contained in the coretuils package are stored in a puppet module data Hiera store. This allows higer level Hiera lookups to override binary paths, configuration files, etc...


puppet module install bi-bi_coreutils -i /path/to/moudles


Consistent static data

To use the statc data (for instance in another class or define):

define my_define() {
    require bi_coreutils::install::touch
    require bi_coreutils::install::test
    exec {"$bi_coreutils::install::touch::exe_path /some/file":
        unless => "! $bi_coreutils::install::test::exe_path -d /some/file",

This allows an end user a consistent location to obtain the binary paths of executables that will be updated via the module data for each platform (or overridden for custom binaries).

Executable wrappers

The binary wrapper for useful programs contained in coreutils for example:

define my_define() {
    bi_coreutils::chmod { '/some/directory':
         mode => '755',
         recursive => true,


For more information see the projects wiki.



For more information see the projects wiki.