Tests and juniper (#109)

* adding wireless tests

* renamed vendor names

* testing juniper file

* testing with rule_11.py

* updated the first rule

* adding EXAMPLES.md

* updated the URL for EXAMPLES.md

* TOC for EXAMPLES.md

* Tests and juniper (#96) (#97)

* adding wireless tests

* renamed vendor names

* testing juniper file

* testing with rule_11.py

* updated the first rule

* adding EXAMPLES.md

* updated the URL for EXAMPLES.md

---------

Co-authored-by: mailsanjayhere <mailsanjayhere@gmail.com>

* updating TOC

* updated for EXAMPLES.md

* removed example inside EXAMPLE.md

* Squashed commit of the following:

commit 8d3fe28
Author: Netpicker <156186606+netpicker@users.noreply.github.com>
Date:   Mon Aug 19 09:26:59 2024 +0200

    Tests and juniper (#100)

    * adding wireless tests

    * renamed vendor names

    * testing juniper file

    * testing with rule_11.py

    * updated the first rule

    * adding EXAMPLES.md

    * updated the URL for EXAMPLES.md

    * TOC for EXAMPLES.md

    * Tests and juniper (#96) (#97)

    * adding wireless tests

    * renamed vendor names

    * testing juniper file

    * testing with rule_11.py

    * updated the first rule

    * adding EXAMPLES.md

    * updated the URL for EXAMPLES.md

    ---------

    Co-authored-by: mailsanjayhere <mailsanjayhere@gmail.com>

    * updating TOC

    * updated for EXAMPLES.md

    ---------

    Co-authored-by: mailsanjayhere <mailsanjayhere@gmail.com>

* changed entire file contents

* fixed typo for devices

* update EXAMPLES.md README.md

* removed few items from TOC

* replaced : with = in commands check

* added 2nd example for multiple lines check

* updated example 2

* add 4th example

---------

Co-authored-by: mailsanjayhere <mailsanjayhere@gmail.com>

Author: netpicker

EXAMPLES.md

@@ -11,6 +11,7 @@ A set of common Netpicker compliance use-cases.
 1. [Format of the Rules](#format-of-the-rules)
 2. [Simple Examples](#simple-examples)
 3. [Multiple Lines](#multiple-lines)
+4. [Using Configuration and Commands](#configuration-commands)
 
 ## Format of the Rules
 
@@ -94,3 +95,22 @@ def rule_bgp_neighbors_up(commands):
     assert len(neighbors_down) == 0, f"BGP neighbors down: {', '.join([line.split()[0] for line in neighbors_down])}"
 ```
 *This example executes the `show ip bgp summary` command and checks the status of all BGP neighbors. If any neighbor is in an "Idle," "Active," or "Connect" state, the rule will fail, listing the IP addresses of the down neighbors.*
+
+## Using Configuration and Commands
+
+### Example: Conditional BGP Neighbor Status Check
+
+This rule first verifies whether BGP is configured on a Cisco IOS device. If BGP is configured, then it checks the status of BGP neighbors and reports if any neighbor is down.
+
+```python
+@medium(
+    name='rule_bgp_neighbors_status',
+    platform=['cisco_ios'],
+)
+def rule_bgp_neighbors_status(configuration, device):
+    if "router bgp" in configuration:
+        bgp_output = device.cli("show ip bgp summary")
+        neighbors_down = [line for line in bgp_output.splitlines() if 'Idle' in line or 'Active' in line or 'Connect' in line]
+        assert len(neighbors_down) == 0, f"BGP neighbors down: {', '.join([line.split()[0] for line in neighbors_down])}"
+```
+*This example looks for 'router bgp' in configuration and if found then executes the `show ip bgp summary` command and checks the status of all BGP neighbors. If any neighbor is in an "Idle," "Active," or "Connect" state, the rule will fail, listing the IP addresses of the down neighbors.*