-
Notifications
You must be signed in to change notification settings - Fork 524
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
Contradictions in documentation about paramiko
being the default
#1042
Comments
Thanks for your Ansible docs contribution! We talk about Ansible documentation on matrix at #docs:ansible.im and on libera IRC at #ansible-docs if you ever want to join us and chat about the docs! We meet there on Tuesdays (see the Ansible calendar) and welcome additions to our weekly agenda items - scroll down to find the upcoming agenda and add a comment to put something new on that agenda. |
Thanks for reporting this and providing all the details @dilyanpalauzov I've added the DaWGs label so we can discuss it tomorrow. You're welcome to join us on Matrix at https://matrix.to/#/#docs:ansible.com |
Labelling this as a good first issue after discussion in DaWGs. If any contributors are interested in working on this, and need some guidance on how to proceed, get in touch on Matrix at https://matrix.to/#/#docs:ansible.com |
This blog post could be helpful in resolving this issue: https://www.ansible.com/blog/new-libssh-connection-plugin-for-ansible-network |
Yeah, this doc is out of date. paramiko is no longer the default; the ssh connection plugin is. |
It should be "SSH protocols types are |
I also submitted ansible/ansible#82594 to fix this spelling error. |
Estimated effort: S (MUNI tech writers) |
Hello! I would like to work with this issue. I am from the MUNI tech writing course |
Hello @Devids10 and welcome! I've assigned the issue to you now. Please feel free to ask any questions here or head over to the docs channel on Matrix. |
MUNI_TECH_WRITERS: Paramiko contradictions, issue #1042
Should in examples/scripts/uptime.py this also be updated? context.CLIARGS = ImmutableDict(connection='smart', …) |
Thanks for catching this @dilyanpalauzov I've fixed it in a follow up PR and also removed another |
(cherry picked from commit e16dbd3)
(cherry picked from commit e16dbd3)
(cherry picked from commit e16dbd3)
(cherry picked from commit e16dbd3)
(cherry picked from commit e16dbd3) Co-authored-by: Don Naro <[email protected]>
(cherry picked from commit e16dbd3) Co-authored-by: Don Naro <[email protected]>
(cherry picked from commit e16dbd3) Co-authored-by: Don Naro <[email protected]>
(cherry picked from commit e16dbd3) Co-authored-by: Don Naro <[email protected]>
https://docs.ansible.com/ansible/latest/reference_appendices/glossary.html#term-paramiko contains:
This means, that unless explicitly changed, Paramiko is used by default. But https://docs.ansible.com/ansible/latest/inventory_guide/connection_details.html#controlpersist-and-paramiko states the opposite: prefer openssh over paramiko and there is no explicit configuration necessary to get openssh over paramiko.
Also https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_9.html#id20 says for Ansible-core 2.9:
But https://docs.ansible.com/ansible/latest/dev_guide/developing_plugins.html#connection-plugins still contains:
without stating that
smart
is gone.Finally https://docs.ansible.com/ansible/latest/inventory_guide/intro_inventory.html#connecting-to-hosts-behavioral-inventory-parameters says for
ansible_connection
:So
smart
does not exist, but is the default foransible_connection
.The text was updated successfully, but these errors were encountered: