Using webhook conditions.

[LilTrublMakr]

I am trying to get the hang of webhook conditions to leverage when a hook should be ran. So far, I have gotten the mode types to work, but would like to only be ran on certain tags since I am running switches from Ubiquiti and Cisco. Since the formats are a little different, I need to run different webhooks.

I tried running the following code to run the webhook but it does not trigger:

{
  "and": [
    {
      "attr": "mode.value",
      "value": "access"
    }, 
    {
      "attr": "tags.slug", 
      "value": "unifi"
    }
  ]
}

My guess is because the tag is actually an array is the reason that the hook will not fire.

How do I go about making the condition to see if the hook contains a certain tag?

[jeremystretch]

To check for a single tag, you need to specify an operation to inform how the condition is evaluated. To check for an item within a list, for instance:

{
  "attr": "tags.slug", 
  "value": "unifi",
  "op": "contains"
}

[LilTrublMakr]

Yep, that fixed it for me as well. Not really sure the proper procedures to create a test case and bug report. Is that something you would be willing to take care of?

[kkthxbye-code]

@LilTrublMakr - There's already a feature request open for it: #9876

Maybe @candlerb is interested in suggesting his fix there.

[LilTrublMakr]

It seems the issue is about to be closed for inactivity. I honestly think this is something that should be implemented. I have been implementing the proposed fix every time that Netbox gets updated.

[AndMrzv]

Can you make it work by manually checking "tags[0].slug" OR "tags[1].slug" etc. in conditions or netbox does not support that? Having this problem with cable connections after 3.3.

[LilTrublMakr]

I believe that the problem is that the webhook conditions doesn't see embedded arrays. At the very least, it does not allow for tags and I have not tested any others. Since tags are the only thing that is an extra actual array, that makes sense. @jeremystretch seems to think it should work, but has been tested by multiple people have tested it and came to the conclusion that it does not. A proposed solution has been presented both here and in issue #9876, and multiple other solutions that I feel should be implemented but would produce breaking changes, so I can understand why they would they wouldn't.

EDIT: clarified webhook conditions

[tyler-8]

Thankful that I found this thread as I was having a heck of time getting my tag-based conditions to work and thought I was doing it wrong. I'll keep my eye on #9876