Include a serialized representation of the HTTP request in each webhook #124

Closed
opened 2026-04-05 16:21:57 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @jeremystretch on 3/18/2026

NetBox version

v4.5.5

Feature type

Change to existing functionality

Proposed functionality

When generating an outbound webhook, include a sanitized serialized capture of the triggering HTTP request (if any) under the request key.

Use case

This provides additional context about the originating request that may be useful to the receiver. It also obviates the need to attach the username and request ID separately (see #21284).

Database changes

N/A

External dependencies

N/A

*Originally created by @jeremystretch on 3/18/2026* ### NetBox version v4.5.5 ### Feature type Change to existing functionality ### Proposed functionality When generating an outbound webhook, include a sanitized serialized capture of the triggering HTTP request (if any) under the `request` key. ### Use case This provides additional context about the originating request that may be useful to the receiver. It also obviates the need to attach the username and request ID separately (see [#21284](https://github.com/netbox-community/netbox/issues/21284)). ### Database changes N/A ### External dependencies N/A
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/netbox#124