From 356cae9e5d4394e7649ce65d8d4292df4d6e997e Mon Sep 17 00:00:00 2001 From: Nathaniel Schaaf Date: Mon, 21 Sep 2015 09:59:28 -0500 Subject: [PATCH] Fix typo --- docsite/rst/developing_plugins.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docsite/rst/developing_plugins.rst b/docsite/rst/developing_plugins.rst index e1fda78cb0..2b0c2344d0 100644 --- a/docsite/rst/developing_plugins.rst +++ b/docsite/rst/developing_plugins.rst @@ -19,7 +19,7 @@ in playbooks and with /usr/bin/ansible to decide how you want to talk to remote are covered in the :doc:`intro_getting_started` section. Should you want to extend Ansible to support other transports (SNMP? Message bus? Carrier Pigeon?) it's as simple as copying the format of one of the existing modules and dropping it into the connection plugins directory. The value of 'smart' for a connection allows selection of paramiko or openssh based on system capabilities, and chooses -'ssh' if OpenSSH supports ControlPersist, in Ansible 1.2.1 an later. Previous versions did not support 'smart'. +'ssh' if OpenSSH supports ControlPersist, in Ansible 1.2.1 and later. Previous versions did not support 'smart'. More documentation on writing connection plugins is pending, though you can jump into `lib/ansible/plugins/connection `_ and figure things out pretty easily.