Forge Home

oddjob

partner
Basic management for OddJob

12,632 downloads

722 latest version

3.1 quality score

Version information

  • 2.3.0 (latest)
  • 2.2.1
  • 2.2.0
  • 2.1.1
  • 2.1.0
  • 2.0.1
  • 2.0.0
  • 1.0.1
  • 1.0.0
released Jul 7th 2021
This version is compatible with:
  • Puppet Enterprise 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x
  • Puppet >= 6.22.1 < 8.0.0
  • CentOS
    ,
    RedHat
    ,
    OracleLinux

Start using this module

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

Add this module to your Puppetfile:

mod 'simp-oddjob', '2.3.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add simp-oddjob
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install simp-oddjob --version 2.3.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

simp/oddjob — version 2.3.0 Jul 7th 2021

License CII Best Practices Puppet Forge Puppet Forge Downloads Build Status

oddjob

Table of Contents

Module Description

This module ensures the oddjobd package is installed, service is running and configures oddjob-mkhomedir.

See REFERENCE.md for API details.

Setup

What oddjob affects

This module will ensure oddjob is installed and the service is running. Additionally, it will use a custom template to create the mkhomedir oddjob enforcing umask.

Setup Requirements

simp/oddjob requires simp/simplib if using the mkhomedir class.

Beginning with oddjob

include 'oddjob'

Usage

I want to set default user umask for home directories

include 'oddjob'
include 'oddjob::mkhomedir'

With Hieradata:

oddjob::mkhomedir::umask: '0077'

Limitations

SIMP Puppet modules are generally intended to be used on a Red Hat Enterprise Linux-compatible distribution.

Development

Please read our Contribution Guide.

If you find any issues, they can be submitted to our JIRA.

Acceptance tests

To run the system tests, you need Vagrant installed.

You can then run the following to execute the acceptance tests:

   bundle exec rake beaker:suites

Some environment variables may be useful:

   BEAKER_debug=true
   BEAKER_provision=no
   BEAKER_destroy=no
   BEAKER_use_fixtures_dir_for_modules=yes
  • BEAKER_debug: show the commands being run on the STU and their output.
  • BEAKER_destroy=no: prevent the machine destruction after the tests finish so you can inspect the state.
  • BEAKER_provision=no: prevent the machine from being recreated. This can save a lot of time while you're writing the tests.
  • BEAKER_use_fixtures_dir_for_modules=yes: cause all module dependencies to be loaded from the spec/fixtures/modules directory, based on the contents of .fixtures.yml. The contents of this directory are usually populated by bundle exec rake spec_prep. This can be used to run acceptance tests to run on isolated networks.