ansible_ssh_password missing from mitogen
#1106
Labels
affects-0.3
Issues related to 0.3.X Mitogen releases
bug
Code feature that hinders desired execution outcome
Comments
madsi1m
added
affects-0.3
|
Created PR that fixes it #1107 |
moreati
added a commit
to moreati/mitogen
that referenced
this issue
Oct 6, 2024
…h_password This switches `ansible_mitogen.transport_config.PlayContextSpec.password()` to Ansible's plugin option framework. As a result - The relatively recent `ansible_ssh_password` variable is now respected. - The SSH connection password can be templated and specified as a play variable. Task variables will probably also work, but testing was blocked by mitogen-hq#1132. There is a chance this change will cause a regression in another connection plugin (e.g. mitogen_docker), but nothing turned up in the test suite. I intend ot migrate other connection configuration to `ansible_mitogen.transport_config.PlayContextSpec._connect_option()`, the next candidate is the remote port. fixes mitogen-hq#1106
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please drag-drop large logs as text file attachments.
Feel free to write an issue in your preferred format, however if in doubt, use
the following checklist as a guide for what to include.
Which version of Ansible are you running?
2.14
Is your version of Ansible patched in any way?
No
Are you running with any custom modules, or
module_utilsloaded?No
Have you tried the latest master version from Git?
No
Do you have some idea of what the underlying problem may be?
https://mitogen.networkgenomics.com/ansible_detailed.html#common-problems has
instructions to help figure out the likely cause and how to gather relevant
logs.
ansible_ssh_passwordis not considered in code but it is documented as valid in current ansible documentationMention your host and target OS and versions
Mention your host and target Python versions
If reporting a performance issue, mention the number of targets and a rough
description of your workload (lots of copies, lots of tiny file edits, etc.)
If reporting a crash or hang in Ansible, please rerun with -vvv and include
200 lines of output around the point of the error, along with a full copy of
any traceback or error text in the log. Beware "-vvv" may include secret
data! Edit as necessary before posting.
If reporting any kind of problem with Ansible, please include the Ansible
version along with output of "ansible-config dump --only-changed".
The text was updated successfully, but these errors were encountered: