Netbox/Nautobot data in templates

[mngan]

Peering Manager version

1.7.4

Feature type

New functionality

Proposed functionality

Not sure how useful people would find this. But if you have linked your router to a device in Netbox/Nautobot, you could potentially have that data available in the templates.

The problem is figuring out how much information a user wants. One potential way to do this is to call a saved graphql query on Netbox/Nautobot for a device, then the user can define however much information they want to retrieve. Otherwise, you could just provide all the top level device information, plus the interface info and IP assignments. Adding the config context will make things a bit more expensive, but if you are just doing a single device, it probably isn't too bad.

Use case

With this you could access information you are maintaining in Netbox/Nautobot for say the session interface or router state. Or you could try to access the config context for the Netbox/Nautobot device to give you more information you could use to build your templates.

This could potentially save people from trying to keep data synced between the systems.

Database changes

None?

External dependencies

For graphQL, there will be a min version of Nautobot/Netbox required, and probably a min version (v6.0.0?) of the pynetbox package.