Closes #20564: Many-to-many pass-through port mappings #838

New Issue

MrUnknownDE · 2026-04-05T18:05:31+02:00

MrUnknownDE commented

2026-04-05 18:05:31 +02:00

Originally created by @jeremystretch on 11/20/2025

Closes: #20564

Note: Any changes made for FrontPort or RearPort are also made for their corresponding template models, FrontPortTemplate and RearPortTemplate, unless otherwise notes.

Introduce the PortMapping model to map port & position pairs between FrontPorts and RearPorts
- This model establishes a mappings relation on both FrontPort & RearPort
Add a positions IntegerField on FrontPort to match the existing positions field on RearPort
Remove the rear_port ForeignKey and rear_port_position IntegerField from FrontPort
Update REST API serializers
- Add front_ports on RearPortSerializer
- Add rear_ports on FrontPortSerializer
Extend device instantiation logic to replicate all front/rear port mappings from a DeviceType to a newly created Device
- Introduce the create_port_mappings() function for this purpose
Update cable tracing logic to respect positions mapped between front & rear ports
Update FrontPort & RearPort tables
- Remove rear_port and rear_port_position columns from FrontPortTable
- Add mappings column to both FrontPortTable and RearPortTable
Add a front_port_id filter for RearPort and update FrontPort's rear_port_id filter
Add positions filter for FrontPort and FrontPortTemplate
GraphQL API
- Replace rear_port field on FrontPortType with mappings
- Add mappings to RearPortType
Update all tests to use PortMapping for front/rear port mapping
Add debug logging for cable path tracing

TODO

Add FKs direct to Device/DeviceType on port mappings
Finish adapting GraphQL API (e.g. add PortMappingTemplateFilter)
Support mapping of front/rear ports via bulk import
Support port template mapping via device type import
Update logic for detecting split paths
Test setting front/rear mappings via REST API
Add tests to verify cable paths are updated correctly when front/rear port mappings change
Clean up debugging code under Cable.from_origin()

*Originally created by @jeremystretch on 11/20/2025* ### Closes: #20564 **Note:** Any changes made for FrontPort or RearPort are also made for their corresponding template models, FrontPortTemplate and RearPortTemplate, unless otherwise notes. - Introduce the `PortMapping` model to map port & position pairs between FrontPorts and RearPorts - This model establishes a `mappings` relation on both FrontPort & RearPort - Add a `positions` IntegerField on FrontPort to match the existing `positions` field on RearPort - Remove the `rear_port` ForeignKey and `rear_port_position` IntegerField from FrontPort - Update REST API serializers - Add `front_ports` on RearPortSerializer - Add `rear_ports` on FrontPortSerializer - Extend device instantiation logic to replicate all front/rear port mappings from a DeviceType to a newly created Device - Introduce the `create_port_mappings()` function for this purpose - Update cable tracing logic to respect positions mapped between front & rear ports - Update FrontPort & RearPort tables - Remove `rear_port` and `rear_port_position` columns from FrontPortTable - Add `mappings` column to both FrontPortTable and RearPortTable - Add a `front_port_id` filter for RearPort and update FrontPort's `rear_port_id` filter - Add `positions` filter for FrontPort and FrontPortTemplate - GraphQL API - Replace `rear_port` field on FrontPortType with `mappings` - Add `mappings` to RearPortType - Update all tests to use PortMapping for front/rear port mapping - Add debug logging for cable path tracing ### TODO - [x] Add FKs direct to Device/DeviceType on port mappings - [x] Finish adapting GraphQL API (e.g. add PortMappingTemplateFilter) - [ ] Support mapping of front/rear ports via bulk import - [x] Support port template mapping via device type import - [x] Update logic for detecting split paths - [x] Test setting front/rear mappings via REST API - [x] Add tests to verify cable paths are updated correctly when front/rear port mappings change - [x] Clean up debugging code under `Cable.from_origin()`

MrUnknownDE closed this issue

2026-04-05 18:05:31 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

No Label

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#838