Would a
- meta: flush_handlers
task, immediately after the copy task (or whatever populates /etc/aliases,
and does the notify), do what you want in this case? It still wouldn't
help if the SSH connection dies immediately after the copy task, but
there's not a whole lot you *can* do in that case. If it's important
enough, maybe come up with a single shell task that populates the file and
runs the handler, so the whole thing will happen even if SSH dies after
the task, but that seems ugly unless it's essential that a particular
task+handler combo be as close to atomic as possible.
-Josh ([email protected])
(apologies for the automatic corporate disclaimer that follows)
This email is intended for the person(s) to whom it is addressed and may
contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use,
distribution, copying, or disclosure by any person other than the addressee(s)
is strictly prohibited. If you have received this email in error, please notify
the sender immediately by return email and delete the message and any
attachments from your system.
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/22240.12720.827541.197783%40gargle.gargle.HOWL.
For more options, visit https://groups.google.com/d/optout.
