Skip to content

Commit a98264e

Browse files
authoredAug 14, 2023
Correct Netscaler parser slug (#340)
* refactor: 🚚 Rename slug used for Citrix Netscaler to align with netmiko driver To align with the other slugs used for platforms I've corrected it to use netscaler instead of citrix_netscaler. * test: Fix docs slug ordering for pytest * revert: ⏪️ Restore citrix_netscaler entry in parser_map
·
v1.14.1v1.6.0
1 parent b4227a2 commit a98264e

File tree

8 files changed

+3
-1
lines changed

8 files changed

+3
-1
lines changed
 

‎docs/dev/include_parser_list.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@
1515
| linux | netutils.config.parser.LINUXConfigParser |
1616
| mikrotik_routeros | netutils.config.parser.RouterOSConfigParser |
1717
| mrv_optiswitch | netutils.config.parser.OptiswitchConfigParser |
18+
| netscaler | netutils.config.parser.NetscalerConfigParser |
1819
| nokia_sros | netutils.config.parser.NokiaConfigParser |
1920
| paloalto_panos | netutils.config.parser.PaloAltoNetworksConfigParser |
2021
| ruckus_fastiron | netutils.config.parser.FastironConfigParser |

‎netutils/config/compliance.py

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,13 +12,14 @@
1212
"cisco_iosxr": parser.IOSXRConfigParser,
1313
"cisco_nxos": parser.NXOSConfigParser,
1414
"cisco_aireos": parser.AIREOSConfigParser,
15+
"citrix_netscaler": parser.NetscalerConfigParser,
1516
"linux": parser.LINUXConfigParser,
1617
"bigip_f5": parser.F5ConfigParser,
1718
"juniper_junos": parser.JunosConfigParser,
1819
"cisco_asa": parser.ASAConfigParser,
1920
"fortinet_fortios": parser.FortinetConfigParser,
2021
"nokia_sros": parser.NokiaConfigParser,
21-
"citrix_netscaler": parser.NetscalerConfigParser,
22+
"netscaler": parser.NetscalerConfigParser,
2223
"aruba_aoscx": parser.ArubaConfigParser,
2324
"mrv_optiswitch": parser.OptiswitchConfigParser,
2425
"extreme_netiron": parser.NetironConfigParser,

0 commit comments

Comments
 (0)
Please sign in to comment.