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

Backwards incompatible breaking change in PR279 #284

Closed
earthgecko opened this issue Jul 22, 2021 · 4 comments
Closed

Backwards incompatible breaking change in PR279 #284

earthgecko opened this issue Jul 22, 2021 · 4 comments
Labels

Comments

@earthgecko
Copy link
Contributor

Hi @mcgege

Sorry to inform you but that change that I added in #279 in not backwards compatible in terms of the puppet-agent version.
Any users that include os_hardening as an external module with r10k, etc that are running puppet-agent <= 6.22.0 will experience an error on a catalog compilation because puppet only introduced max_files in 6.23.0

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: no parameter named 'max_files' (file: /etc/puppetlabs/code/external_modules/production/modules/os_hardening/manifests/minimize_access.pp, line: 61) on File[/usr/local/games] (file: /etc/puppetlabs/code/external_modules/production/modules/os_hardening/manifests/minimize_access.pp, line: 61) on node example.org

Pull request incoming.

earthgecko added a commit to earthgecko/puppet-os-hardening that referenced this issue Jul 22, 2021
* Only allow max_files where puppet-agent >= 6.23.0
@earthgecko
Copy link
Contributor Author

@mcgege hold off, I will update PR to handle puppet 6 and puppet 7 as max_files was only introduced in 7.7.0

earthgecko added a commit to earthgecko/puppet-os-hardening that referenced this issue Jul 22, 2021
- Handle max_files where puppet-agent >= 6.23.0/7.7.0
@earthgecko
Copy link
Contributor Author

@mcgege will handle both puppet 6 and 7. Just be aware that the case selector testing the aio_agent_version is defaulting to true, based on the assumption that puppet 8.0.0 will have max_files from day 1.

Sorry for the inconvenience, I am glad puppet 5 was removed and glad I caught this before it possibly affects too many people.

@mcgege
Copy link
Member

mcgege commented Jul 22, 2021

@earthgecko Thanks a lot for spotting this ... if you have a current Puppet version it is all fine ... will merge this asap

@mcgege mcgege added the bug label Jul 22, 2021
mcgege pushed a commit that referenced this issue Jul 22, 2021
* Only allow max_files where puppet-agent >= 6.23.0
@mcgege mcgege closed this as completed Jul 22, 2021
@mcgege
Copy link
Member

mcgege commented Jul 22, 2021

Fixed with #285

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants