-
-
Notifications
You must be signed in to change notification settings - Fork 13
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
Change Management Behavoir for Repositories #6
Comments
Currently params like manage_epel always manage the repository resource and manage_* enable or disable the repo. Rework to manage the resources and NOT to enable/disable repos. |
@fionera if you like you can test branch fix/manage-repos-6 |
I currently have it set to my fork but since you took the same approach it should be fine :) Thank you |
Ok, of course I did more. Especially the same for the other supported plattforms. I will perform acceptence tests and build a release tomorrow or maybe later today. |
Thank you very much |
Currently when I include the class by enabling manage_repo, the
epel
Repo gets defined even whenmanage_epel
is set to false. This collides with the following: https://forge.puppet.com/modules/puppet/epelThe text was updated successfully, but these errors were encountered: