Add Aruba AOS-CX to the Netmiko and Hier Config library mappers - #874
Add Aruba AOS-CX to the Netmiko and Hier Config library mappers#874dspatig-gdx wants to merge 3 commits into
Conversation
|
Adds `aruba_aoscx` → `aruba_aoscx` to `NETMIKO_LIB_MAPPER` and `HIERCONFIG_LIB_MAPPER` (and their reverses) so netutils resolves the Netmiko and hier_config driver names for Aruba AOS-CX. netmiko already exposes an `aruba_aoscx` device type; hier_config's v2→v3 resolver reads `network_driver_mappings["hier_config"]` and now gets AOS-CX instead of falling back to GENERIC. Docs tables were regenerated via `python development_scripts.py`, and a changelog fragment is included." |
|
Previously aruba_aoscx was added in the section for non netmiko drivers |
|
The main reason for the addition is that heir_config now has aruba_aoscx support. Netmiko does as well and this has been tested when setting network drivers to {"netmiko": {"aruba_aoscx": "aruba_aoscx"}, "hier_config": {"aruba_aoscx": "aruba_aoscx"}} |
|
can you remove this line netutils/netutils/lib_mapper.py Line 698 in 8d4ab67 |
Now that aruba_aoscx is in NETMIKO_LIB_MAPPER, MAIN_LIB_MAPPER inherits it via the netmiko deep copy, so the explicit override is no longer needed. Addresses review feedback on networktocode#874.
|
Done in 7fc57dd — dropped the explicit _MAIN_LIB_MAPPER["aruba_aoscx"] line. MAIN_LIB_MAPPER now picks it up from the netmiko deep-copy, verified it still resolves and all tests pass. |
…nto add-aruba-aoscx-hier-config-mapper # Conflicts: # netutils/lib_mapper.py
Closes #873