Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ansible-<x> config attributes seem to be ignored during workflow playbook steps #379

Open
Timbus opened this issue Jul 9, 2024 · 0 comments

Comments

@Timbus
Copy link

Timbus commented Jul 9, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant