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

Webhook conditions primary_ip is defined not working #7056

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

Originally created by @stefanmarti on GitHub (Sep 30, 2022).

NetBox version

v3.2.5

Python version

3.8

Steps to Reproduce

Create webhook on event update and model device with the following condition:

{
   "and":[
      {
         "attr":"status.value",
         "value":"active"
      },
      {
         "attr":"primary_ip",
         "value":"",
         "negate":true
      }
   ]
}

Expected Behavior

Webhook shoud not get fired if device doesn't have a primary_ip set

Observed Behavior

Webhook get fired also for devices without a primary_ip set

Originally created by @stefanmarti on GitHub (Sep 30, 2022). ### NetBox version v3.2.5 ### Python version 3.8 ### Steps to Reproduce Create webhook on event `update` and model `device` with the following condition: ``` { "and":[ { "attr":"status.value", "value":"active" }, { "attr":"primary_ip", "value":"", "negate":true } ] } ``` ### Expected Behavior Webhook shoud not get fired if device doesn't have a primary_ip set ### Observed Behavior Webhook get fired also for devices without a primary_ip set
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:48:25 +01:00
adam closed this issue 2025-12-29 19:48:25 +01:00
adam commented 2025-12-29 19:48:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 30, 2022):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Sep 30, 2022): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 19:48:26 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 10, 2022):

Closing as there's been no further reply.

@jeremystretch commented on GitHub (Oct 10, 2022): Closing as there's been no further reply.
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: revisions needed type: bug
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#7056
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?