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

Include snapshots in event data sent to scripts #9730

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

Originally created by @Mailstorm-ctrl on GitHub (May 23, 2024).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v4.0.3

Feature type

Change to existing functionality

Proposed functionality

When you set up an event rule and send it to a webhook, the webhook data will include snapshots of pre and post change items of the object. However, when you change to script, you lose the snapshots that made some additional logic possible with webhooks.

I think it would be beneficial if data received to a script contained the same information as a webhook would receive.

Use case

If you wanted to use pre-change data in a script, you'd have to get that prechange data yourself. Not the end of the world but an unnecessary step. My use case is when adding a tag to a device, it gets added to NAGIOS. The pre and post change fields determine exactly what I need to do without unnecessary API calls to nagios (Checking to see if device exists in nagios or not + other data in nagios)

Database changes

None

External dependencies

No response

Originally created by @Mailstorm-ctrl on GitHub (May 23, 2024). Originally assigned to: @DanSheps on GitHub. ### NetBox version v4.0.3 ### Feature type Change to existing functionality ### Proposed functionality When you set up an event rule and send it to a webhook, the webhook data will include snapshots of pre and post change items of the object. However, when you change to script, you lose the snapshots that made some additional logic possible with webhooks. I think it would be beneficial if data received to a script contained the same information as a webhook would receive. ### Use case If you wanted to use pre-change data in a script, you'd have to get that prechange data yourself. Not the end of the world but an unnecessary step. My use case is when adding a tag to a device, it gets added to NAGIOS. The pre and post change fields determine exactly what I need to do without unnecessary API calls to nagios (Checking to see if device exists in nagios or not + other data in nagios) ### Database changes None ### External dependencies _No response_
adam added the status: duplicate label 2025-12-29 21:21:43 +01:00
adam closed this issue 2025-12-29 21:21:43 +01:00
adam commented 2025-12-29 21:21:44 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (May 27, 2024):

Duplicate of #14884

@DanSheps commented on GitHub (May 27, 2024): Duplicate of #14884
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
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#9730
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?