yum

deprecated
YUM utilities
CERIT Scientific Cloud

CERIT Scientific Cloud

ceritsc

5,988,192 downloads

5,713,483 latest version

3.1 quality score

Version information

  • 0.9.8 (latest)
  • 0.9.7
  • 0.9.6
  • 0.9.5
  • 0.9.4
  • 0.9.3
  • 0.9.2
  • 0.9.1
  • 0.9.0
released May 30th 2016
This version is compatible with:
  • Puppet Enterprise 3.3.x
  • Puppet 3.3
  • RedHat, CentOS, OracleLinux, Scientific, SLES, SLED
This module has been deprecated by its author since Jan 5th 2018.

The author has suggested puppet-yum as its replacement.

Start using this module

Tags: yum, package

Documentation

ceritsc/yum — version 0.9.8 May 30th 2016

Puppet yum module

Please note this module is deprecated, future maintenance took over the Puppet Community. Please use new https://forge.puppet.com/puppet/yum

This module provides helpful definitions for dealing with yum.

Requirements

Module has been tested on:

  • Puppet 3.7.x
  • CentOS 6, 7

Usage

yum

Manage main Yum configuration.

class { 'yum':
  keepcache         => false|true,
  debuglevel        => number,
  exactarch         => false|true,
  obsoletes         => false|true,
  gpgcheck          => false|true,
  installonly_limit => number,
  keep_kernel_devel => false|true,
}

If installonly_limit is changed, purging of old kernel packages is triggered.

yum::config

Manage yum.conf.

yum::config { 'installonly_limit':
  ensure => 2,
}

yum::config { 'debuglevel':
  ensure => absent,
}

yum::gpgkey

Import/remove GPG RPM signing key.

Key defined in recipe (inline):

yum::gpgkey { '/etc/pki/rpm-gpg/RPM-GPG-KEY-puppet-smoketest1':
  ensure  => present,
  content => '-----BEGIN PGP PUBLIC KEY BLOCK-----
...
-----END PGP PUBLIC KEY BLOCK-----',
}

Key stored on Puppet fileserver:

yum::gpgkey { '/etc/pki/rpm-gpg/RPM-GPG-KEY-elrepo.org':
  ensure => present,
  source => 'puppet:///modules/elrepo/RPM-GPG-KEY-elrepo.org',
}

yum::plugin

Install or remove yum plugin:

yum::plugin { 'versionlock':
  ensure => present,
}

yum::versionlock

Locks explicitly specified packages from updates. Package name must be precisely specified in format EPOCH:NAME-VERSION-RELEASE.ARCH. Wild card in package name is allowed or automatically appended, but be careful and always first check on target machine if your package is matched correctly! Following definitions create same configuration lines:

yum::versionlock { '0:bash-4.1.2-9.el6_2.*':
  ensure => present,
}

yum::versionlock { '0:bash-4.1.2-9.el6_2.':
  ensure => present,
}

Correct name for installed package can be easily get by running e.g.:

$ rpm -q bash --qf '%|EPOCH?{%{EPOCH}}:{0}|:%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n'
0:bash-4.2.45-5.el7_0.4.x86_64

yum::group

Install or remove yum package group:

yum::group { 'X Window System':
  ensure  => present,
  timeout => 600,
}

yum::install

Install or remove packages via yum install subcommand:

From URL:

yum::install { 'package-name':
  ensure => present,
  source => 'http://path/to/package/filename.rpm',
}

From local filesystem:

yum::install { 'package-name':
  ensure => present,
  source => '/path/to/package/filename.rpm',
}

Please note that resource name must be same as installed package name.

Contributors


CERIT Scientific Cloud, support@cerit-sc.cz