Cable paths are not updated when merging a branch with cable changes

[jeremystretch]

Plugin Version

v0.5.0

NetBox Version

v4.1.1

Python Version

3.10

Steps to Reproduce

This bug addresses a secondary problem raised in #98.

1. Create two devices, A and B.
2. Create interface 1 on device A and interfaces 1 & 2 on device B.
3. Create a cable between device A interface 1 and device B interface 1.
4. Create and activate a branch.
5. Edit the cable, and change the device B end from interface 1 to interface 2.
6. Merge the branch, committing changes.
7. Inspect the connection status of device A interface 1 and device B interface 2.

Expected Behavior

Either interface should show as connected to the other.

Observed Behavior

Although both interfaces show as connected to the same cable, no path is populated to show them as connected to each other.

As a workaround, manually retracing the cables path (manage.py trace_paths --force) corrects this condition.

[mrmrcoleman]

Another example of this came up.

NetBox: v4.3.2
Branching: 0.6.0

Same behaviour:

• Pre-merge the interfaces are connected to a cable, and have a valid 'connection'
• Post-merge the interfaces still show the correct cable, but the 'connection' is no longer there

API output

Before

"connected_endpoints": [
    { ... endpoint object ... }
],
"connected_endpoints_type": "dcim.interface",
"connected_endpoints_reachable": true

After

"connected_endpoints": null,
"connected_endpoints_type": null,
"connected_endpoints_reachable": null