-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Plugin Version
0.4.0
Proposed functionality
NetBox Version
4.4.4
Python Version
3.12
Current Behavior:
Create a custom object type X with fields Name (as type text), devices, sites and vlans (as type multiple object)
Add custom object of "Name: Y" to custom object type X, add required devices and vlans shows up great.
Add custom field to DCIM > Devices as type "single object" pointing to custom object Y.
Add custom field to DCIM > Site as type "single object" pointing to custom object Y.
Add custom field to IPAM > VLANs as type "single object" pointing to custom object Y.
Create a new Device, Site or VLAN and select custom object Y under the custom field.
This shows Y under the custom field as a link to the custom object but does not add the new Device/Site/VLAN in the custom object meaning mapping new objects is a two-step process.
Example Desired Behavior:
Create a custom object type X with fields Name (as type text), devices, sites and vlans (as type multiple object)
Add custom object of "Name: Y" to custom object type X.
Add custom field to DCIM > Devices as type "single object" pointing to custom object Y > Devices.
Add custom field to DCIM > Site as type "single object" pointing to custom object Y > Sites.
Add custom field to IPAM > VLANs as type "single object" pointing to custom object Y > VLANs.
Create a Device, Site or VLAN and select custom object Y under the custom field.
The Device/Site/VLAN appears under the mapped field in the custom object.
Use case
This would remove the need to double handle data when adding new devices meaning links and references could be added in both directions avoiding user error in mapping attributes to custom objects.
External dependencies
No response