| Commit message (Collapse) | Author |
|---|
|
It will help to switch to the generic ansible.builtin.package module; it
is also better to configure it globally anyway.
|
|
First, I don't think it's even necessary. If the service wasn't running,
then we don't need to restart it. If it was running, it'll continue
running fine with a new dependency; it'll be picked up on a future
restart.
Second, all of that doesn't even work due to (another) weird way Ansible
treats handlers:
https://github.com/ansible/ansible/issues/81722
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It should be better and more comprehensible.
|
|
|
|
|
|
|
|
I saw a good point somewhere that it should help with syntax
highlighting.
|
|
|
|
|
|
set_fact is stupid; they persist through multiple role executions; for
example, you cannot do this:
set_fact:
foo: '{{ foo | default("bar") }}'
If somebody calls the role and defines foo, it will always be set to
that value forever, even for subsequent role calls.
|
|
|
|
|
|
|
|
|
|
|
|
"warning" is too limiting; too many things get lost.
|
