5f652c7584
SELinux since 2012 use a configuration file to
convert boolean names from a old name to a new name,
for preserving backward compatibility.
However, this has to be done explicitely when using the python
bindings, and the module was not doing it.
Openshift ansible script use this construct to detect if
a boolean exist or not:
- name: Check for existence of virt_sandbox_use_nfs seboolean
command: getsebool virt_sandbox_use_nfs
register: virt_sandbox_use_nfs_output
failed_when: false
changed_when: false
- name: Set seboolean to allow nfs storage plugin access from containers(sandbox)
seboolean:
name: virt_sandbox_use_nfs
state: yes
persistent: yes
when: virt_sandbox_use_nfs_output.rc == 0
On a system where virt_sandbox_use_nfs do not exist, this work. But
on a system where virt_sandbox_use_nfs is a alias to virt_use_nfs (like
Fedora 24), this fail because the seboolean is not aware of the alias.
|
8 years ago | |
|---|---|---|
| .github | 8 years ago | |
| cloud | 8 years ago | |
| commands | 8 years ago | |
| database | 8 years ago | |
| files | 8 years ago | |
| inventory | 9 years ago | |
| network | 8 years ago | |
| packaging | 8 years ago | |
| source_control | 8 years ago | |
| system | 8 years ago | |
| test | 8 years ago | |
| utilities | 8 years ago | |
| web_infrastructure | 8 years ago | |
| windows | 8 years ago | |
| .gitignore | 10 years ago | |
| .travis.yml | 8 years ago | |
| CONTRIBUTING.md | 8 years ago | |
| COPYING | 10 years ago | |
| README.md | 9 years ago | |
| VERSION | 9 years ago | |
| __init__.py | 10 years ago | |
| shippable.yml | 8 years ago | |
| test-docs.sh | 9 years ago | |
| test-requirements.txt | 9 years ago | |
README.md
ansible-modules-core
This repo contains Ansible's most popular modules that are shipped with Ansible.
New module submissions for modules that do not yet exist should be submitted to ansible-modules-extras, rather than this repo.
Take care to submit tickets to the appropriate repo where modules are contained. The docs.ansible.com website indicates this at the bottom of each module documentation page.
Reporting bugs
Take care to submit tickets to the appropriate repo where modules are contained. The repo is mentioned at the bottom of module documentation page at docs.ansible.com.
Testing modules
Ansible module development guide contains the latest info about that.
License
As with Ansible, modules distributed with Ansible are GPLv3 licensed. User generated modules not part of this project can be of any license.
Installation
There should be no need to install this repo separately as it should be included in any Ansible install using the official documented methods.