GitHub puppet-yum
Puppet module for Yum

Repo Checks ( 21 of 28 successfull )
Metadata Valid
No translation
passed
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_SUPPORT_RANGE}
passed
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
passed
With Operatingsystem Support
No translation
passed
Operatingsystems
No translation
passed
Supports Only Current Redhat
No translation
passed
Supports Latest Redhat
No translation
passed
Supports Only Current Rocky
No translation
passed
Supports Latest Rocky
No translation
failed
Supports Only Current Centos
No translation
passed
Supports Latest Centos
No translation
failed
Supports Only Current Scientific
No translation
passed
Supports Latest Scientific
No translation
failed
Supports Only Current Oraclelinux
No translation
passed
Supports Latest Oraclelinux
No translation
failed
Supports Only Current Virtuozzolinux
No translation
passed
Supports Latest Virtuozzolinux
No translation
failed
Supports Only Current Amazon
No translation
passed
Supports Latest Amazon
No translation
failed
Supports Only Current Almalinux
No translation
passed
Supports Latest Almalinux
No translation
failed
In Modulesync Repo
Is listed as a module managed using modulesync_config
passed
Synced
Has a .msync.yml file
passed
Latest Modulesync
Has been synchronized with the latest tagged version of modulesync_config
passed
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
passed
Released
Is in modulesync_config and in forge releases.
passed
Valid Sync File
If a (optional) sync file is present, it must not contain a `.travis.yml` entry.
passed
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.
passed

Open Pull Requests

Add function to properly import gpg keys
enhancement
tests-fail
Revert #258, which added purge_unmanaged_repos
bug
backwards-incompatible

This method of purging unmanaged yum repo configs does not work. This is because the repo configs are managed by puppetlabs/yumrepo_core as native yumrepo types, not file resources.

Fixes #285

Open PR in GitHub
feat(yum): add yum update and upgrade
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

Allow to perform in needed case yum update or/and yum upgrade

Way to use within hiera :

```

yum::update: true
yum::upgrade: true
```

Open PR in GitHub
README: fix typos in /etc/pki/rpm-gpg paths
Add yum::copr resource to handle COPR repositories.
enhancement

COPR (Cool Other Package Repo) is a Fedora project for third-party package repositories, see:
https://copr.fedorainfracloud.org/

Pull Request (PR) description

This PR adds support to manage COPR repositories via a new yum::copr resource.
Documentation and test are included.

This Pull Request (PR) fixes the following issues

Fixes #149

Open PR in GitHub
[needs validation] allow RpmNameGlob for versionlock entries
bug
needs-tests

As stated in the manpage [1] yum versionlock supports package-wildcard
and does not require exact matches for package-names.
The following is valid versionlock.list content:

libvirt*-0:7.6.0-*.*
qemu*-0:6.1.0-*.*

This commit swaps Yum::RpmName with Yum::RpmNameGlob for the
versionlock assert_type() and thus allowing the above mentioned
examples.

[1] https://man7.org/linux/man-pages/man1/yum-versionlock.1.html

Open PR in GitHub
Option to disable display of diff in the puppet log
enhancement

Pull Request (PR) description

In addition to https://github.com/voxpupuli/puppet-yum/pull/275
There is conditions where the sensitive information is displayed in the logs. This add option to completely disable output in the logs.


class example {
class { 'yum' :
show_diff => false,
}
}

Tests

I’m not a pro in the tests suite alley, feel free to comment on any other way I could have fixed the tests… It took me way longer to fix the tests than to add the new config.

As the yum::config now includes yum to retreive yum::show_diff, the tests are done on every supported OS for the variables to be set correctly.

I had to modify the versionlock tests to make them pass. The diff is quite hard to read, so here the summary of what I did:
- The tests are now run on every supported OS.
- I moved the context 'with a simple, well-formed package name title bash and a version' in the context 'with package_provider set to yum' as they were duplicated facts definition
- I merge the fact package_provider with the facts provided by every OS

Open PR in GitHub