You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an issue that is similar to issue #282 where I would like to orchestrate some ansible steps between nodes, instead of relying on rundeck to orchestrate it.
This should be possible using the playbook 'workflow' step, but it seems like the ansible- config attributes are ignored when using it. To be more precise: the generated inventory is half-working for the step, but it's using the default user + auth to initiate ssh instead of ansible-ssh-user etc.
It's also probably important to note that we use the EC2 inventory plugin and not the ansible one. It doesn't seem to cause problems for the node steps.
The most straightforward fix I can think of would be to add the appropriate ansible_ssh_x variables for each host in the generated inventory when starting the workflow step. Does this seem feasible?
The text was updated successfully, but these errors were encountered:
I have an issue that is similar to issue #282 where I would like to orchestrate some ansible steps between nodes, instead of relying on rundeck to orchestrate it.
This should be possible using the playbook 'workflow' step, but it seems like the
ansible-
config attributes are ignored when using it. To be more precise: the generated inventory is half-working for the step, but it's using the default user + auth to initiate ssh instead ofansible-ssh-user
etc.It's also probably important to note that we use the EC2 inventory plugin and not the ansible one. It doesn't seem to cause problems for the node steps.
The most straightforward fix I can think of would be to add the appropriate ansible_ssh_x variables for each host in the generated inventory when starting the workflow step. Does this seem feasible?
The text was updated successfully, but these errors were encountered: