Event rule condition logic

[Azmodeszer]

This is driving me insane. Basically, I want an even rule triggered by creating or updating objects having a certain specific tag AND not having a certain more generic tag.

{
    "and": [
        {
            "attr": "tags.slug",
            "op": "contains",
            "value": "webmin"
        },
        {
            "attr": "tags.slug",
            "negate": true,
            "value": "webmin"
        }
    ]
}

This should match objects tagged as "Webmin-XYZ" and not tagged as "Webmin" as well, but the trigger does not work. Yes, the slug is correct.

Apparently I am fundamentally misunderstanding something here, because I've played around with it a bit and

{
    "and": [
        {
            "attr": "tags.slug",
            "op": "contains",
            "value": "webmin"
        }
    ]
}

does work, but it only matches objects with the "Webmin" tag and is indifferent to objects with "Webmin-XYZ". When I remove "op": "contains", no matches at all. So the contains operator acts like an exact match and the exact match operator... does not work at all? Please advise.

[Azmodeszer]

hmmm, so this could be the root of the problem? #9797 As I understand it, the operators don't work because the data format they're operating on is a list rather than a single string?

Is there a workaround for me to achieve this functionality? Surely tag-based event rules aren't a particularly exotic use case.

[Azmodeszer]

Anyone?