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

Apply all registered request processors when running custom scripts #10575

New Issue
Closed
opened 2025-12-29 21:33:18 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:33:18 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Dec 12, 2024).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.1.8

Feature type

Change to existing functionality

Triage priority

I volunteer to perform this work (if approved)

Proposed functionality

When a custom script is run (as a background job), currently only the event_tracking request processor is employed:

e63fe23af8/netbox/extras/jobs.py (L101-L104)

All registered request processors should be applied here, not just event_tracking.

Use case

FR #18211 recently introduced the ability to dynamically register request processors (a planned feature for the plugins API). This change will ensure that any additional registered processors are run when executing custom scripts as well as when servicing requests.

Database changes

N/A

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Dec 12, 2024). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.1.8 ### Feature type Change to existing functionality ### Triage priority I volunteer to perform this work (if approved) ### Proposed functionality When a custom script is run (as a background job), currently only the [`event_tracking`](https://github.com/netbox-community/netbox/blob/e63fe23af859d69c5960095ed812c99f782e5476/netbox/netbox/context_managers.py#L10) request processor is employed: https://github.com/netbox-community/netbox/blob/e63fe23af859d69c5960095ed812c99f782e5476/netbox/extras/jobs.py#L101-L104 All registered request processors should be applied here, not just `event_tracking`. ### Use case FR #18211 recently introduced the ability to dynamically register request processors (a planned feature for the plugins API). This change will ensure that any additional registered processors are run when executing custom scripts as well as when servicing requests. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:33:18 +01:00
adam closed this issue 2025-12-29 21:33:19 +01:00
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 complexity: low status: accepted 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#10575
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?