From c6d0f1c035eb8ce555097bc481fc62ef3b15c20c Mon Sep 17 00:00:00 2001
From: Oliver Gorwits <oliver@cpan.org>
Date: Wed, 26 Jul 2017 13:51:23 +0100
Subject: [PATCH] add doc note on accessing transports

---
 .../Netdisco/Manual/WritingBackendDrivers.pod | 27 ++++++++++++++++++-
 1 file changed, 26 insertions(+), 1 deletion(-)

diff --git a/lib/App/Netdisco/Manual/WritingBackendDrivers.pod b/lib/App/Netdisco/Manual/WritingBackendDrivers.pod
index 0f2e27e2..c613866b 100644
--- a/lib/App/Netdisco/Manual/WritingBackendDrivers.pod
+++ b/lib/App/Netdisco/Manual/WritingBackendDrivers.pod
@@ -126,7 +126,32 @@ Remember that a driver is only run if it matches the hardware platform of the
 target device and the user's configuration, and is not also excluded by the
 user's configuration.
 
-=head1 Database Connections
+=head2 Accessing Transports
+
+From your driver you will want to connect to a device to gather data. This is
+done using a transport protocol session (SNMP, SSH, etc). Transports are
+singleton objects instantiated on demand, so they can be shared among a series
+of action phases that are accessing the same device.
+
+See the documentation for each transport to find out how to access it:
+
+=over 4
+
+=item *
+
+L<App::Netdisco::Core::Transport::SNMP>
+
+=item *
+
+L<App::Netdisco::Core::Transport::HTTPS>
+
+=item *
+
+L<App::Netdisco::Core::Transport::SSH>
+
+=back
+
+=head2 Database Connections
 
 The Netdisco database is available via the C<netdisco> schema key, as below.
 You can also use the C<external_databases> configuration item to set up