Forge Home


Backport package_settings feature to older puppet versions


7,072 latest version

4.4 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

  • 0.0.3 (latest)
  • 0.0.2
  • 0.0.1
released Sep 16th 2016

Start using this module

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

Add this module to your Puppetfile:

mod 'ptomulik-backport_package_settings', '0.0.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add ptomulik-backport_package_settings
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install ptomulik-backport_package_settings --version 0.0.3

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.



ptomulik/backport_package_settings — version 0.0.3 Sep 16th 2016


Build Status


This project is no longer developed. Use ptomulik-backports instead.

Table of Contents

  1. Overview
  2. Setup
  3. Development


Backport package_settings to older versions of Puppet.

The package resource has a package_settings feature and property in Puppet 3.5.0 and later. The property, however, is missing in older puppet versions. This module brings the package_settings feature back to any older version of Puppet if it doesn't have one.


Setup Requirements

You must enable pluginsync in your puppet.conf.

Beginning with backport_package_settings

To backport package_settings put the following line in front of your package provider:

require 'puppet/backport/type/package/package_settings'

To use package_settings, your provider should implement at least these methods:

  • package_settings
  • package_settings=(value)
  • package_settings_insync?(should,is)

It may also optionally implement the following methods:

  • package_settings_validate(value),
  • package_settings_munge(value),
  • package_settings_should_to_s(should,newvalue),
  • package_settings_is_to_s(should,currentvalue),
  • package_settings_change_to_s(currentvalue,newvalue)


The project is held at github: