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 additional form fields into a core object form (Edit, Delete, etc) #9848

New Issue
Closed
opened 2025-12-29 21:23:30 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:23:30 +01:00
Owner
Copy Link

Originally created by @DanSheps on GitHub (Jun 14, 2024).

NetBox version

v4.0.5

Feature type

New functionality

Proposed functionality

The proposed change would be to allow plugins to inject form fields into core object form views (Edit, Import, BulkEdit, Delete). How this is done could be implemented either on the view or within the view's own form.

There would need to be method to register the integration into a specific form as well as something in place to verify there are no conflicts between core fields and the plugin injected fields

Use case

Sometimes, the provided fields within a form are not enough to track certain types of information for an organization. Allowing plugins to extend the Edit, BulkEdit and Delete views to add additional form fields which are saved to the plugin(s) models allows more flexibility beyond custom fields.

An example would be with Interfaces and carrying more layer 2 configuration data compared to what is currently permitted on the model or allowing more advanced relationships to be defined.

This could also in theory allow plugins to integrate with other plugins.

Database changes

None, this would purely be a change to the way form views are rendered

External dependencies

None

Originally created by @DanSheps on GitHub (Jun 14, 2024). ### NetBox version v4.0.5 ### Feature type New functionality ### Proposed functionality The proposed change would be to allow plugins to inject form fields into core object form views (Edit, Import, BulkEdit, Delete). How this is done could be implemented either on the view or within the view's own form. There would need to be method to register the integration into a specific form as well as something in place to verify there are no conflicts between core fields and the plugin injected fields ### Use case Sometimes, the provided fields within a form are not enough to track certain types of information for an organization. Allowing plugins to extend the Edit, BulkEdit and Delete views to add additional form fields which are saved to the plugin(s) models allows more flexibility beyond custom fields. An example would be with Interfaces and carrying more layer 2 configuration data compared to what is currently permitted on the model or allowing more advanced relationships to be defined. This could also in theory allow plugins to integrate with other plugins. ### Database changes None, this would purely be a change to the way form views are rendered ### External dependencies None
adam added the type: featurestatus: duplicate labels 2025-12-29 21:23:30 +01:00
adam closed this issue 2025-12-29 21:23:30 +01:00
adam commented 2025-12-29 21:23:31 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jun 14, 2024):

I am an idiot, I already opened this

@DanSheps commented on GitHub (Jun 14, 2024): I am an idiot, I already opened this
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: duplicate 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#9848
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?