Skip to content
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

yum::versionlock causes configuration loss #90

Closed
vchepkov opened this issue Mar 24, 2018 · 1 comment
Closed

yum::versionlock causes configuration loss #90

vchepkov opened this issue Mar 24, 2018 · 1 comment
Labels
wont-fix This will not be worked on

Comments

@vchepkov
Copy link

yum::versionlock should only manage relevant configuration and do not 'purge' existing configuration.
imagine if 'host' resource did the same. Since resource uses 'concat' for implementation it overrides all existing configuration. augeas or file_line would be more appropriate

@traylenator
Copy link

There is a trade off. It is useful to have things purged when they are un-configured.

Given this file is by default empty and not managed anyway other way letting puppet control the file fully is useful. The solution is not to add lines to the file any other way.
So this would be a close won't fix from me.

@juniorsysadmin juniorsysadmin added the wont-fix This will not be worked on label May 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wont-fix This will not be worked on
Projects
None yet
Development

No branches or pull requests

3 participants