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
NetBox can track the untagged and tagged VLANs of an interface. A VLAN may have custom fields and useful attributes to have as part of the inventory. Fetching interfaces only returns the brief details of an interface and not all these extra fields. It would like to fetch a lookup of VLANs, and insert the full VLAN object instead of the brief one into interfaces.
The text was updated successfully, but these errors were encountered:
Hi @DouglasHeriot. Adding detailed VLAN information to every interface will duplicate a lot of information across all interfaces. It could be thousands of times when pulling an inventory.
While its more work for the user, a separate lookup for the VLANs outside of the inventory will need to be done to get that information. This makes sense from a data structure point of view.
ISSUE TYPE
SOFTWARE VERSIONS
Ansible:
v2.9.7
Netbox:
v2.8.3
Collection:
v0.2.0
SUMMARY
NetBox can track the untagged and tagged VLANs of an interface. A VLAN may have custom fields and useful attributes to have as part of the inventory. Fetching interfaces only returns the brief details of an interface and not all these extra fields. It would like to fetch a lookup of VLANs, and insert the full VLAN object instead of the brief one into interfaces.
The text was updated successfully, but these errors were encountered: