to support multiple ansible versions (and python) it would be nice if:
either we could define a host on which to run the ansible command on instead of localhost
and/or we could define a "custom" "ansible" and "ansible-playbook" which gets used (i.e: ansible2.9/ansible-playbook2.9) instead of the hardcoded ansible/ansible-playbook.
This would help migrating to newer versions of ansible/python and allow for delegations to dedicated nodes...
I understand that especially the first variant will be complicated from the perspective of gathering of node infos (because we would need to copy the ansible script to the new host and copy the results back to the host that runs rundeck).
Only workaround right now is to use the shell executor, but then we loose the means to select nodes in rundeck and run those nodes in parallel or handle errors on a per host basis...
jasenj1
commented
10 months ago
to support multiple ansible versions (and python) it would be nice if:
This would help migrating to newer versions of ansible/python and allow for delegations to dedicated nodes...
I understand that especially the first variant will be complicated from the perspective of gathering of node infos (because we would need to copy the ansible script to the new host and copy the results back to the host that runs rundeck).
Only workaround right now is to use the shell executor, but then we loose the means to select nodes in rundeck and run those nodes in parallel or handle errors on a per host basis...