package_verifiable

This is the package_verifiable module.

The idea is that we have a way to check within the catalog whether a package currently installed matches the one we want to install.

For that we place a custom fact that records the installed version and then we can use a function to verify whether there will be a change.

Usage

$pkg_version = hiera('some_package_version','1.0-1')
package_verifiable{
  'some-package':
    version => $pkg_version,
}

# $::package_some_package_version is undef if the package is not yet installed
if $::package_some_package_version and !verify_package_versions('some-package',$pkg_version) {
  exec{'systemctl stop some-service && rm -rf /opt/my_package/service':
    before => Package['some-package'],
  }
}

If the current deployed package does not match the version on the system the exec will be included into the catalog and hence triggered. By playing with before/require you will be able to add pre-/post-hooks to the package management.

If the package itself is managed in another module that should not be using the package module, we can simply add the wrapper here, without managing the package itself:

$pkg_version = hiera('some_package_version','1.0-1')
package_verifiable{
  'some-package':
    version        => $pkg_version,
    manage_package => false,
}

Support

Please log tickets and issues at our Projects site

MIT license, see LICENSE.md

Changelog

2.0.1 (2016-02-17)

• Add ordering Versionlock -> Package
• Sort manifest, formatting & Tests

2.0.0 (2016-02-08)

• Do the package -> file_line dependency by resource collection. This allows to install a package only once and from then on only the versionlock and the fact will be managed by puppet. A useful case is ie. ScaleIO where we absolutly don't want an upgrade by Puppet, as this would break the ScaleIO cluster and end in data loss. Example:

package_verifiable{'myPackage':
  version        => '1.32.4',
  manage_package => !$package_mypackage_version,
}