This is a rebase of https://github.com/voxpupuli/puppet-yum/pull/118
Fixes #116
<!--
Thank you for contributing to this project!
-->
Allow to perform in needed case yum update
or/and yum upgrade
Way to use within hiera :
yum::update: true
yum::upgrade: true
```
COPR (Cool Other Package Repo) is a Fedora project for third-party package repositories, see:
https://copr.fedorainfracloud.org/
This PR adds support to manage COPR repositories via a new yum::copr
resource.
Documentation and test are included.
Fixes #149
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
<!--
Thank you for contributing to this project!
-->
Provide a parameter to deploy plugin config elements.
Fixes #254
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,
}
}
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~~ edit: did not fix this in my new rebase
- I merge the fact package_provider
with the facts provided by every OS
<!--
Thank you for contributing to this project!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
<!--
Thank you for contributing to this project!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
<!--
Thank you for contributing to this project!
-->
<!--
Replace this comment with a description of your pull request.
-->
<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->
<!--
Thank you for contributing to this project!
-->
Handles differences in yum group definitions. We found if the upstream comps.xml is changed in the repository that yum::group resources would not issue an install regardless whether ensure is set to present or latest.
Not sure if this is an issue for others. But, we found the current behavior unexpected. If comps.xml is updated upstream and yum::group is set to latest I expect puppet to resolve those differences and install the missing packages.