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

Include complete representation of object type in outbound webhook payload #11449

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

Originally created by @jeremystretch on GitHub (Aug 6, 2025).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.3.5

Feature type

New functionality

Proposed functionality

Add new object_type and object_id fields to the default JSON payload of outbound webhooks:

{
    "event": "updated",
    "timestamp": "2025-08-05T14:24:22.300153+00:00",
    "object_type": "dcim.site",
    "object_id": 123,
    "model": "site",
    "username": "admin",
    ...
}

Note: This is not a breaking change, as the currently model field will be retained to ensure backward compatibility.

Use case

Currently, only the bare model name (e.g. "site") is included. This is ambiguous and represents an opportunity for naming collisions. Additionally, providing the object ID at the JSON data root simplifies the process of extracting the data, as it obviates the need to also parse the data object.

Database changes

N/A

External dependencies

N/A

Originally created by @jeremystretch on GitHub (Aug 6, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.3.5 ### Feature type New functionality ### Proposed functionality Add new `object_type` and `object_id` fields to the default JSON payload of outbound webhooks: ```json { "event": "updated", "timestamp": "2025-08-05T14:24:22.300153+00:00", "object_type": "dcim.site", "object_id": 123, "model": "site", "username": "admin", ... } ``` Note: This is not a breaking change, as the currently `model` field will be retained to ensure backward compatibility. ### Use case Currently, only the bare model name (e.g. `"site"`) is included. This is ambiguous and represents an opportunity for naming collisions. Additionally, providing the object ID at the JSON data root simplifies the process of extracting the data, as it obviates the need to also parse the `data` object. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:45:23 +01:00
adam closed this issue 2025-12-29 21:45:23 +01:00
adam commented 2025-12-29 21:45:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 6, 2025):

Blocked by FR #20003

@jeremystretch commented on GitHub (Aug 6, 2025): Blocked by FR #20003
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#11449
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?