severity of alarm entities in templates are case sensitive

[Elisha Rosensweig]

When creating a vitrage template, with an alarm as an entity in the "definitions" section (not in the "scenarios" section), if the alarm severity is listed - it only works if it's in upper case (e.g., "CRITICAL", not "critical"). Should be case-insensitive.

[Abhinav Gupta (abhinavgupta)]

Is anyone working on this bug ?
I would like to work on it.

[Elisha Rosensweig (elisha-rosensweig)]

you can take it - but note that it's not as simple as it looks. I'll give a short overview:

In the templates you can use any key-value pair in the entity properties to condition on. The condition is tested against the values in the entity graph.

Now, some fields (e.g., resource name) should be case-sensitive, while others (severity) should not. Thus, the name of this bug (and marking it as low-hanging) is confusing. It will require some design to support knowing which fields can be case-insensitive.

[Ifat Afek (ifat-afek)]

Elisha - in that case, I'll remove the low-hanging-fruit tag. I agree that it is confusing.