7c632352a0
The behaviour of the `include` module is badly defined (it try to choose between statically importing the tasks and dynamically including them) and can cause problems depending on any number of constraints (mostly if it choose the wrong behaviour). Replace it with the `import_tasks` (always statically import tasks) unless the `include` is in a loop in which case we replace it with `include_tasks` (always dynamically include tasks). |
||
|---|---|---|
| .. | ||
| defaults | ||
| files | ||
| handlers | ||
| meta | ||
| tasks | ||
| templates | ||
| tests | ||
| .kitchen.yml | ||
| README.md | ||
Apache
Install Apache
Tasks
Everything is in the tasks/main.yml file for now.
An ip_whitelist.yml standalone task file is available to update IP adresses whitelist without rolling the whole role.
Available variables
Main variables are :
apache_ipaddr_whitelist_present: list of IP addresses to have in the private whitelist ;apache_ipaddr_whitelist_absent: list of IP addresses not to have in the whitelist;apache_private_htpasswd_present: list of users to have in the private htpasswd ;apache_private_htpasswd_absent: list of users to not have in the private htpasswd.log2mail_alert_email: email address to send Log2mail messages to (default:general_alert_email).
The full list of variables (with default values) can be found in defaults/main.yml.