Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simple condition (without and/or) does not work in event rule #14829

Open
markkuleinio opened this issue Jan 17, 2024 · 1 comment · May be fixed by #14870
Open

Simple condition (without and/or) does not work in event rule #14829

markkuleinio opened this issue Jan 17, 2024 · 1 comment · May be fixed by #14870
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@markkuleinio
Copy link
Contributor

Deployment Type

Self-hosted

NetBox Version

v3.7.0

Python Version

3.11

Steps to Reproduce

  1. Create webhook: Name = Test, URL = http://127.0.0.1:9000 (doesn't matter in this case, it won't be triggered but is required to configure event rule)
  2. Go to Event rules - Add:
  • Name = Test
  • Content types = Circuit
  • select Updates
  • set Conditions:
{
    "attr": "status.value",
    "value": "active"
}
  • Action type = Webhook
  • Webhook = Test
  • Create

Expected Behavior

Event rule is created

Observed Behavior

Error is shown about the condition:

Ruleset must have exactly one logical operator (found 2)

The examples in https://docs.netbox.dev/en/stable/reference/conditions/ look the same: simple JSON object with attributes attr and value.

@markkuleinio markkuleinio added the type: bug A confirmed report of unexpected behavior in the application label Jan 17, 2024
@DanSheps DanSheps added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Jan 19, 2024
@Julio-Oliveira-Encora
Copy link
Contributor

Please, someone could assign it to me?

@DanSheps DanSheps added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
3 participants