Since the _haproxy_ role relies on other roles to provide drop-in configuration files for actual proxy configuration, we cannot start the service in the base role. If there are any issues with the drop-in files that are added later, the service will not be able to start, causing the playbook to fail and thus never be able to update the broken configuration. The dependent roles need to be responsible for starting the service once they have put their configuration files in place. |
||
---|---|---|
.. | ||
defaults | ||
files | ||
handlers | ||
tasks | ||
templates | ||
vars |