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

Add a built-in webhook listener to aid in troubleshooting #3547

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

Originally created by @jeremystretch on GitHub (Apr 7, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • Python version: 3.6.9
  • NetBox version: 2.7.11

Proposed Functionality

Add a new management command that will initialize a simple HTTP daemon and print to terminal all received HTTP requests. For example:

$ python manage.py webhook_receiver 0.0.0.0:9000
Listening on 0.0.0.0:9000...
[1] Received request from 192.0.2.48
  Type: POST
  Headers: <...>
  Body: <...>

Use Case

It can be difficult to troubleshoot webhooks, especially when writing custom header/body templates. Introducing a local service to dump received requests allows a user to perform local troubleshooting by pointing a webhook to the local host on the specified port.

Database Changes

None

External Dependencies

None

Originally created by @jeremystretch on GitHub (Apr 7, 2020). Originally assigned to: @jeremystretch on GitHub. ### Environment * Python version: 3.6.9 * NetBox version: 2.7.11 ### Proposed Functionality Add a new management command that will initialize a simple HTTP daemon and print to terminal all received HTTP requests. For example: ``` $ python manage.py webhook_receiver 0.0.0.0:9000 Listening on 0.0.0.0:9000... [1] Received request from 192.0.2.48 Type: POST Headers: <...> Body: <...> ``` ### Use Case It can be difficult to troubleshoot webhooks, especially when writing custom header/body templates. Introducing a local service to dump received requests allows a user to perform local troubleshooting by pointing a webhook to the local host on the specified port. ### Database Changes None ### External Dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 18:29:48 +01:00
adam closed this issue 2025-12-29 18:29:48 +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 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#3547
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?