Plugin Version
0.6.0
Proposed functionality
Add an option to each Custom Object Type (COT) to enable or disable its appearance in the "Custom Objects linking to this object" panel introduced in PR #482.
Currently, every COT that references an object is automatically displayed in the Object Links panel.
With this feature, each COT should be be able to control whether its links are shown in the panel.
- By default, Object Links remain enabled to preserve the current behavior.
- If disabled, links created by that COT remain fully functional and accessible through the API and the COT itself, but they are omitted from the "Custom Objects linking to this object" panel.
Related PR:
#482
Use case
Custom Object Types can serve as the data model for custom plugins or application-specific extensions built on top of the Custom Objects framework.
In these scenarios, relationships to NetBox objects are required for the data model, but the reverse links shown on object detail pages are often not relevant to users of the plugin. Displaying every relationship in the "Custom Objects linking to this object" panel can therefore create unnecessary visual clutter.
Allowing Object Links to be enabled or disabled per COT gives plugin authors and administrators control over which relationships are exposed in the user interface while preserving the underlying data model and all object relationships.
External dependencies
None
Plugin Version
0.6.0
Proposed functionality
Add an option to each Custom Object Type (COT) to enable or disable its appearance in the "Custom Objects linking to this object" panel introduced in PR #482.
Currently, every COT that references an object is automatically displayed in the Object Links panel.
With this feature, each COT should be be able to control whether its links are shown in the panel.
Related PR:
#482
Use case
Custom Object Types can serve as the data model for custom plugins or application-specific extensions built on top of the Custom Objects framework.
In these scenarios, relationships to NetBox objects are required for the data model, but the reverse links shown on object detail pages are often not relevant to users of the plugin. Displaying every relationship in the "Custom Objects linking to this object" panel can therefore create unnecessary visual clutter.
Allowing Object Links to be enabled or disabled per COT gives plugin authors and administrators control over which relationships are exposed in the user interface while preserving the underlying data model and all object relationships.
External dependencies
None