From 942b2646c2cd34c70499de13fa644ea145f591ba Mon Sep 17 00:00:00 2001 From: Sandra McCann Date: Mon, 25 Mar 2019 17:05:10 -0400 Subject: [PATCH] added attribution to author (#54356) --- .../rst/network/user_guide/network_best_practices_2.5.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst b/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst index b17cf426cf3..f1f4d7ad2c3 100644 --- a/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst +++ b/docs/docsite/rst/network/user_guide/network_best_practices_2.5.rst @@ -326,6 +326,8 @@ If `ansible-playbook` fails, please follow the debug steps in :ref:`network_debu Example 2: simplifying playbooks with network agnostic modules ============================================================== +(This example originally appeared in the `Deep Dive on cli_command for Network Automation `_ blog post by Sean Cavanaugh -`@IPvSean `_). + If you have two or more network platforms in your environment, you can use the network agnostic modules to simplify your playbooks. You can use network agnostic modules such as ``cli_command`` or ``cli_config`` in place of the platform-specific modules such as ``eos_config``, ``ios_config``, and ``junos_config``. This reduces the number of tasks and conditionals you need in your playbooks. .. note::