Currently my plugin's process has a Time To Live concept to keep data
during some customizable duration.
It's pretty similar to what *async* provides but the drawback is that
you need to know in advance how many time the execution will take, and
that's what I want to avoid.
Regards,
Daniel
Le 2022-07-26 10:57, Vladimir Botka a écrit :
On Tue, 26 Jul 2022 07:32:33 +0200
Daniel Gonçalves <[email protected]> wrote:
context: I have a custom lookup plugin that
initialize some data and execute a new process ...
I want to be able to send a SIGTERM signal to the process to
terminate it at the end of playbook execution.
This seems to be a candidate for *async*
https://docs.ansible.com/ansible/latest/user_guide/playbooks_async.html#run-tasks-concurrently-poll-0
--
Vladimir Botka
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/d2847c653de4e0c41a75b667d2b11d72%40lves.fr.
