Thanks for the role!
I had some problems using the latest changes from your dev branch with Ansible 2.7.
I fixed the issues on my fork and perhaps you want to integrate this into your role.
Jinja2 syntax.
Ansible complained for example about {% nut_ups_extra %} and it did not work.
It is the first time I stumpbled this kind of syntax for rendering a value in a template. Is this working on your side? I changed the syntax to {{ VARIABLE }}.
Add support for NOTIFYCMD
You can either only specify a path to an existing script (nut_upsmon_notifycmd), or use nut_upsmon_notifycmd_content to place a script in the path specified by the nut_upsmon_notifycmd property.
Use list based package installation
In the more recent versions of Ansible it is possible (and recommended) to use the list based installation feature of packages. Package installation using with_items takes more time and produces more log output.
Hi @ntd!
Thanks for the role! I had some problems using the latest changes from your dev branch with Ansible 2.7. I fixed the issues on my fork and perhaps you want to integrate this into your role.
Ansible complained for example about
{% nut_ups_extra %}
and it did not work. It is the first time I stumpbled this kind of syntax for rendering a value in a template. Is this working on your side? I changed the syntax to{{ VARIABLE }}
.NOTIFYCMD
You can either only specify a path to an existing script (
nut_upsmon_notifycmd
), or usenut_upsmon_notifycmd_content
to place a script in the path specified by thenut_upsmon_notifycmd
property.In the more recent versions of Ansible it is possible (and recommended) to use the list based installation feature of packages. Package installation using
with_items
takes more time and produces more log output.Feedback is appreciated :)