-
-
Notifications
You must be signed in to change notification settings - Fork 143
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow additional option for $cache parameter #169
Conversation
systemd is a classBreaking changes to this file WILL impact these 20 modules (exact match):
Breaking changes to this file MAY impact these 8 modules (near match):This module is declared in 8 of 576 indexed public
|
LGTM. Could you add a unit test for this please? |
Update the cache parameter on init class to match the allowed values for resolved.
Added testing around the cache variants. |
* Allow additional option for $cache parameter Update the cache parameter on init class to match the allowed values for resolved. * added tests for resolved cache variants
* Allow additional option for $cache parameter Update the cache parameter on init class to match the allowed values for resolved. * added tests for resolved cache variants
Support paramatized yum::versionlock
Correct acceptence tests for DNF (8) system Use the new versionlock specification from voxpupuli#169 on CentOS 8. Also test the new specification on 7 and 8 also. Finally test that if samba-devel is filtered at an impossible version it is no longer available. This for the yum case probably assumes that samba-devel is not
Update the cache parameter on init class to match the allowed values for
resolved.
This addresses the issue brought up here: #166
#140 initally added the ability to use the no-negative option for resolved, however it did not include the corresponding adjustment to allow controlling the value from the init class.