starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow plugins to inject sub-tabs on object detail views #6316

New Issue
Closed
opened 2025-12-29 19:39:17 +01:00 by adam · 3 comments
adam commented 2025-12-29 19:39:17 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Apr 7, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

Object detail views typically have several tabs: the primary object details, the object change log, and the journal, for example. Some objects have additional tabs. This proposal (borne from discussion in WG8333) seeks to allow plugins to inject arbitrary additional tabs for particular objects.

The exact implementation is open for discussion, but it seems reasonable to assume that a plugin could register one or more (name, view) tuples to specific NetBox models identified by their app label and model name.

One likely blocker here is that we'll need to come up with a way to programmatically declare sub-tabs under a view, but this would serve the existing changelog & journal views as well.

Use case

Provides a greater degree of integration with core NetBox models and more convenient navigation for the user.

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Apr 7, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.0 ### Feature type New functionality ### Proposed functionality Object detail views typically have several tabs: the primary object details, the object change log, and the journal, for example. Some objects have additional tabs. This proposal (borne from discussion in WG8333) seeks to allow plugins to inject arbitrary additional tabs for particular objects. The exact implementation is open for discussion, but it seems reasonable to assume that a plugin could register one or more (name, view) tuples to specific NetBox models identified by their app label and model name. One likely blocker here is that we'll need to come up with a way to programmatically declare sub-tabs under a view, but this would serve the existing changelog & journal views as well. ### Use case Provides a greater degree of integration with core NetBox models and more convenient navigation for the user. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featuretopic: plugins labels 2025-12-29 19:39:17 +01:00
adam closed this issue 2025-12-29 19:39:17 +01:00
adam commented 2025-12-29 19:39:18 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 7, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 7, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:39:18 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Oct 7, 2022):

Such a good addition to the plugin API!

@kkthxbye-code commented on GitHub (Oct 7, 2022): Such a good addition to the plugin API!
adam commented 2025-12-29 19:39:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 7, 2022):

Not only that, it also allows us to clean up quite a bit of cruft and redundancy internally!

@jeremystretch commented on GitHub (Oct 7, 2022): Not only that, it also allows us to clean up quite a bit of cruft and redundancy internally!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted topic: plugins type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6316
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?