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

Extend the default object representation to include the "full" representation of related objects in webhook body #9841

New Issue
Open
opened 2025-12-29 21:23:27 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:23:27 +01:00
Owner
Copy Link

Originally created by @FloMeyer on GitHub (Jun 13, 2024).

NetBox version

v4.0.5

Feature type

Data model extension

Proposed functionality

As discussed but may be forgotten in https://github.com/netbox-community/netbox/issues/9594 I would like ask you to implement a full representation of related objects in the webhook body or at least device_role.

Use case

If you update an interface i would like to fire a webhook. But only if the interface belongs to a device with a specific device_role - this should be filtered via webhook condition.

Database changes

No response

External dependencies

No response

Originally created by @FloMeyer on GitHub (Jun 13, 2024). ### NetBox version v4.0.5 ### Feature type Data model extension ### Proposed functionality As discussed but may be forgotten in https://github.com/netbox-community/netbox/issues/9594 I would like ask you to implement a full representation of related objects in the webhook body or at least device_role. ### Use case If you update an interface i would like to fire a webhook. But only if the interface belongs to a device with a specific device_role - this should be filtered via webhook condition. ### Database changes _No response_ ### External dependencies _No response_
adam commented 2025-12-29 21:23:28 +01:00
Author
Owner
Copy Link

@crytectobi commented on GitHub (Aug 8, 2024):

Hi,

I have the very same use case. I'm from the network department and try to automate interface configuration of network devices.
I would like to check the device role to trigger only for network devices (e.g. device role network-access-switch, router, etc.).
But Netbox is used by all IT departments, and my automation would trigger from all devices.
Only solutions would be to tag every single interface, but that is more a workaround and makes zero sense outside of this trigger condition.
So this feature would be very much appreciated for automation. :)

@crytectobi commented on GitHub (Aug 8, 2024): Hi, I have the very same use case. I'm from the network department and try to automate interface configuration of network devices. I would like to check the device role to trigger only for network devices (e.g. device role network-access-switch, router, etc.). But Netbox is used by all IT departments, and my automation would trigger from all devices. Only solutions would be to tag every single interface, but that is more a workaround and makes zero sense outside of this trigger condition. So this feature would be very much appreciated for automation. :)
adam commented 2025-12-29 21:23:28 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 25, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 25, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
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: medium needs milestone netbox status: backlog 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#9841
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?