Description
NetBox version
v4.2.6
Feature type
New functionality
Proposed functionality
Allow users to make use of request data (such as username) when deciding to trigger an event rule.
Use case
Some integrations are shared between systems, so NetBox may update a system using a webhook, and then the same system may update another field in NetBox. So when the second system updates a field in NetBox I want to avoid running a webhook updating the other system again. Basically to avoid a never-ending loop of updates.
As an example I would like to do something like this in an event rule:
"attr": "username",
"negate": true,
"value": "api_othersystem"
If I am to look beyond my own specific need, I can see the need of using the group membership of the user triggering the event as well. Maybe there are multiple systems updating certain fields in NetBox, and you want to group them to make is easier to decide on event rules triggering.
Database changes
No database changes. From what I can see the need is to add some request data (for an example username) to the data dictionary used in this line:
netbox/netbox/extras/events.py
Line 90 in 6f78b3d
External dependencies
No response