You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another use case could be using an example like the above in an Ansible filter. That would allow you to write a filter utilizing whichever automation library you needed without having to store the driver for each one in your Source of Truth.
40
40
41
+
There is also a dynamically built mapping that gives you all of the libraries given a normalized name, here is a condensed snippet to understand the data structure of `NAME_TO_ALL_LIB_MAPPER`:
42
+
43
+
```python
44
+
{
45
+
"cisco_ios": {
46
+
"ansible": "cisco.ios.ios",
47
+
"napalm": "ios",
48
+
},
49
+
"cisco_nxos": {
50
+
"ansible": "cisco.nxos.nxos",
51
+
"napalm": "nxos",
52
+
}
53
+
}
54
+
```
41
55
42
56
## Aerleon Mapper
43
57
44
-
--8<-- "docs/user/lib_mapper/aerleon.md
58
+
--8<-- "docs/user/lib_mapper/aerleon.md"
45
59
46
60
## Reverse Aerleon Mapper
47
61
48
-
--8<-- "docs/user/lib_mapper/aerleon_reverse.md
62
+
--8<-- "docs/user/lib_mapper/aerleon_reverse.md"
49
63
50
64
## Ansible Mapper
51
65
@@ -57,19 +71,19 @@ Another use case could be using an example like the above in an Ansible filter.
0 commit comments