-
Notifications
You must be signed in to change notification settings - Fork 15
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
OS version checking #3
Comments
No, this Ansible role is tailored specifically to Debian 9 "Stretch". Sure it may work on Buster, but that needs to be tested thoroughly and also the CIS-CAT requirements for Buster may have changed. I suggest forking this repo and then tailoring the fork to Debian 10 "Buster". |
@rmbleeker, thanks for your reply. I tried to apply to playbook to Debian 10 Buster, I was expecting it to fail, but the playbook was actually applied. |
I see what you mean now, also the message still speaks of Ubuntu while the checks are for Debian. So I agree with your changes, you should probably make a pull request. |
Will do ASAP, thanks. |
Is the following line supposed to stop the playbook if applied to something different than Debian stretch?
https://github.com/florianutz/Debian9-CIS/blob/master/tasks/main.yml#L8
I'm running the playbook against Debian 10, Buster, there are a few weird things that I still need to triage, but the playbook gets applied.
I run the task through the debug, that's what I get:
Probably the code should look like:
The text was updated successfully, but these errors were encountered: