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

Need ability to write plugins that contributes actions to objects. #9266

New Issue
Closed
opened 2025-12-29 20:47:40 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:47:40 +01:00
Owner
Copy Link

Originally created by @rkiss on GitHub (Feb 18, 2024).

NetBox version

v3.7.2

Feature type

New functionality

Proposed functionality

Quite often I need to perform an action or trigger an external process starting from a specific object or set of objects.
While this is perfectly possible with Netbox scripts or external scripts that use Netbox API I believe it will be much more intuitive and open Netbox to a whole new set of use cases if a plugin can contribute actions to objects.
Such actions should show every time a table with such objects are presented or when the such an object is viewed or edited.
Additionally, such plugins could specify certain limitations like it should be active only on devices of a particular device type or role.
When such an action is triggered the plugin can show a dialog where more information can be collected from user then it would execute a run method in a similar way a Netbox script works.

Use case

Possible applications:

  • Send emails to a set of tenants. The email could be based on a template.
  • Act upon a network range or device.
  • Trigger some sort of automation for one or more devices.
  • Trigger a "clone" operation over a device/location/site. Or a validation.

Database changes

No change in database

External dependencies

No extra dependencies needed. However, some plugins might require additional dependencies but that is not in scope.

Originally created by @rkiss on GitHub (Feb 18, 2024). ### NetBox version v3.7.2 ### Feature type New functionality ### Proposed functionality Quite often I need to perform an action or trigger an external process starting from a specific object or set of objects. While this is perfectly possible with Netbox scripts or external scripts that use Netbox API I believe it will be much more intuitive and open Netbox to a whole new set of use cases if a plugin can contribute actions to objects. Such actions should show every time a table with such objects are presented or when the such an object is viewed or edited. Additionally, such plugins could specify certain limitations like it should be active only on devices of a particular device type or role. When such an action is triggered the plugin can show a dialog where more information can be collected from user then it would execute a `run` method in a similar way a Netbox script works. ### Use case Possible applications: - Send emails to a set of tenants. The email could be based on a template. - Act upon a network range or device. - Trigger some sort of automation for one or more devices. - Trigger a "clone" operation over a device/location/site. Or a validation. ### Database changes No change in database ### External dependencies No extra dependencies needed. However, some plugins might require additional dependencies but that is not in scope.
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:47:40 +01:00
adam closed this issue 2025-12-29 20:47:40 +01:00
adam commented 2025-12-29 20:47:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 20, 2024):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Feb 20, 2024): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:47:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 29, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Feb 29, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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: revisions needed 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#9266
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?