We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
generally is not recommended to use shell module, if there is a native module in place.
shell
current state: https://github.com/dev-sec/ansible-os-hardening/blob/eb777fbe2f1f8677ff80b9cf5f37bedb9648476e/tasks/yum.yml#L13
using find module example:
- name: get yum-repository-files find: paths: '/etc/yum.repos.d' patterns: '*.repo' register: yum_repos
therefore in context:
- name: get yum-repository-files find: paths: '/etc/yum.repos.d' patterns: '*.repo' register: yum_repos - name: activate gpg-check for yum-repository-files replace: dest: '{{ item.path }}' regexp: '^\s*gpgcheck.*' replace: 'gpgcheck=1' with_items: - '{{ yum_repos.files | default([]) }}'
The text was updated successfully, but these errors were encountered:
Good find, you're totally right. Do you want to create a PR to fix that?
Sorry, something went wrong.
yeah, I will create it.
No branches or pull requests
generally is not recommended to use
shell
module, if there is a native module in place.current state:
https://github.com/dev-sec/ansible-os-hardening/blob/eb777fbe2f1f8677ff80b9cf5f37bedb9648476e/tasks/yum.yml#L13
using find module example:
therefore in context:
The text was updated successfully, but these errors were encountered: