/path not /trace on front and rear ports

[marcelb98]

On front and rear ports the API provides /path and not /trace which is currently usable by the .trace() function on TracableRecords (which front and rear ports seem to be at the moment).

Calling the .trace() function on rear ports actually leads to an AttributeError (as there is no /trace provided by the Netbox API).

Maybe this changed from some older versions of Netbox…

[markkuleinio]

NetBox 2.10 release notes (https://netbox.readthedocs.io/en/stable/release-notes/version-2.10/) say:

dcim.FrontPort:
Replaced the /trace/ endpoint with /paths/, which returns a list of cable paths

dcim.RearPort:
Replaced the /trace/ endpoint with /paths/, which returns a list of cable paths

It also says:

circuits.CircuitTermination:
Added the /trace/ endpoint

dcim.PowerFeed:
Added the /trace/ endpoint

In pynetbox, these all models inherit from TraceableRecord (that defines the trace() method):

• Interfaces
• PowerOutlets
• PowerPorts
• ConsolePorts
• ConsoleServerPorts
• FrontPorts
• RearPorts

Maybe just copying TraceableRecord.trace() to TraceableRecord.paths() (with /paths request path in the code instead of /trace) (in pynetbox/models/dcim.py) could do? @marcelb98 are you able to test it with your data?

[marcelb98]

Just copying the trace() to paths() and changing the requested URL doesn't work, as the /paths endpoint returns a different datastructure. While the /trace for interfaces returns a list of (Endpoint, Cable, Endpoint) tuples, the /paths returns a list of related paths, each with an origin and destination Endpoint and the path from origin to endpoint as a list of Interfaces, Front/RearPorts and Cables.

I've implemented a paths() function in PR #440.