Forge Home


Puppet module for sudo


50,676 latest version

4.1 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

  • 2.0.19 (latest)
  • 2.0.18
  • 2.0.17
  • 2.0.16
  • 2.0.15
  • 2.0.14
  • 2.0.13
  • 2.0.12
  • 2.0.11
  • 2.0.10
  • 2.0.9
  • 2.0.8
released Aug 12th 2016
This module has been deprecated by its author since Oct 28th 2019.

The reason given was: No longer maintained

The author has suggested saz-sudo as its replacement.

Start using this module

Tags: sudo, example42


example42/sudo — version 2.0.19 Aug 12th 2016

Deprecation notice

This module was designed for Puppet versions 2 and 3. It should work also on Puppet 4 but doesn't use any of its features.

The current Puppet 3 compatible codebase is no longer actively maintained by example42.

Still, Pull Requests that fix bugs or introduce backwards compatible features will be accepted.

Puppet module: sudo

This is a Puppet module for sudo based on the second generation layout ("NextGen") of Example42 Puppet Modules.

Made by Alessandro Franceschi / Lab42

Based on the sudo module of CamptoCamp:

Official site:

Official git repository:

Released under the terms of Apache 2 License.

This module requires functions provided by the Example42 Puppi module (you need it even if you don't use and install Puppi)

For detailed info about the logic and usage patterns of Example42 modules check the DOCS directory on Example42 main modules set.


The configuration of the sudoers file(s) can be done following different approches:

  • Manage directly the /etc/sudoers file with the source, template or content arguments
  • Manage the whole /etc/sudoers.d/ directory content with the source_dir argument
  • Manage single entries in /etc/sudoers.d/ with the sudo::directive define (and eventually the main /etc/sudoers file with custom source/template)
  • Use custom sources for main config file

      class { 'sudo':
        source => [ "puppet:///modules/lab42/sudo/sudo.conf-${hostname}" , "puppet:///modules/lab42/sudo/sudo.conf" ], 
  • Use custom source directory for the whole configuration dir

      class { 'sudo':
        source_dir       => 'puppet:///modules/lab42/sudo/conf/',
        source_dir_purge => false, # Set to true to purge any existing file not present in $source_dir
  • Use custom template for main config file. Note that template and source arguments are alternative.

      class { 'sudo':
        template => 'example42/sudo/sudo.conf.erb',
  • Manage directly the content of the main config file. Note that template has precedence over content.

      class { 'sudo':
        content => inline_template(
          file( "$settings::modulepath/example42/templates/sudo/sudo.conf.erb-${hostname}",
                "$settings::modulepath/example42/templates/sudo/sudo.conf.erb" ) ),
  • Use default sudo class and specific sudo::directive entries

      sudo::directive { 'jenkins':
        content => "jenkins ALL=NOPASSWD: /usr/sbin/puppi \n", # Double quotes and newline (\n) are needed here
      sudo::directive { 'developers':
        content => template('example42/sudo/developers'), # Here is used a template
      sudo::directive { 'joe':
        source => 'puppet:///modules/example42/sudo/sudo-joe', # Here is used a static source
  • Automatically include a custom subclass

      class { 'sudo':
        my_class => 'sudo::example42',

Build Status