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
But ansible:lib/ansible/playbook/attribute.py line 187 still handles the smart connection type, falling back to paramiko, when the latter is installed. So this type is not removed, but deprecated.
Despite connection type smart, introduced in Ansible 2.1 and removed per Porting Guide 9, in Ansible 1.2.1 the logic was to select intelligently between ssh and paramiko. The current documentation still hints that the intelligent selection between ssh and paramiko is done:
documentation:docs/docsite/rst/inventory_guide/connection_details.rst line 12 says “If your control machine uses an older version of OpenSSH that does not support ControlPersist, Ansible will fall back to a Python implementation of OpenSSH called 'paramiko'.” → implies smart connection.
Switch your default connection type in the configuration file to ``ssh``, or use ``-c ssh`` to use
Native OpenSSH for connections instead of the python paramiko library. In Ansible 1.2.1 and later, ``ssh`` will be used
by default if OpenSSH is new enough to support ControlPersist as an option.
We keep paramiko as the default as if you are first installing Ansible on these enterprise operating systems, it offers a better experience for new users.
The above states twice, that the default is paramiko, or after Ansible 1.2.1 the default is what smart does.
ansible:lib/ansible/config/base.yml line 1054: “There is also a (DEPRECATED) special 'smart' option, that will toggle between 'ssh' and 'paramiko' depending on controller OS and ssh versions.” → No, the option is not deprecated, it is removed per porting_guide_9, but ansible/utils/ssh_functions.py still checks for this value.
All that said, the documentation is not very clear on what is the default: ssh and fallback to paramiko, or ssh, letting users willing paramiko to be explicit. It is also unclear if connection type smart is removed or deprecated.
The text was updated successfully, but these errors were encountered:
the ‘smart’ option for setting a connection plugin is being removed as its main purpose (choosing between ssh and paramiko) is now irrelevant. is part of the "Deprecated Features" portion of the porting guide, indicating that it is a deprecation. Final removal would be listed in the "Removed Features" section.
#1042 ⇔ #1258 has removed some contradictions on connection types smart and paramiko.
https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_9.html#id45 says „the ‘smart’ option for setting a connection plugin is being removed as its main purpose (choosing between ssh and paramiko) is now irrelevant.“
But ansible:lib/ansible/playbook/attribute.py line 187 still handles the
smart
connection type, falling back to paramiko, when the latter is installed. So this type is not removed, but deprecated.Despite connection type
smart
, introduced in Ansible 2.1 and removed per Porting Guide 9, in Ansible 1.2.1 the logic was to select intelligently betweenssh
andparamiko
. The current documentation still hints that the intelligent selection betweenssh
andparamiko
is done:documentation:docs/docsite/rst/inventory_guide/connection_details.rst line 12 says “If your control machine uses an older version of OpenSSH that does not support ControlPersist, Ansible will fall back to a Python implementation of OpenSSH called 'paramiko'.” → implies smart connection.
documentation:docs/docsite/rst/reference_appendices/faq.rst:
The above states twice, that the default is
paramiko
, or after Ansible 1.2.1 the default is whatsmart
does.ansible:lib/ansible/config/base.yml line 1054: “There is also a (DEPRECATED) special 'smart' option, that will toggle between 'ssh' and 'paramiko' depending on controller OS and ssh versions.” → No, the option is not deprecated, it is removed per porting_guide_9, but ansible/utils/ssh_functions.py still checks for this value.
All that said, the documentation is not very clear on what is the default: ssh and fallback to paramiko, or
ssh
, letting users willingparamiko
to be explicit. It is also unclear if connection typesmart
is removed or deprecated.The text was updated successfully, but these errors were encountered: