User story #6298
closedSearching on key=value properties is not easy
Description
On all the desktops I've got in Rudder I have two key=value properties. One is for the user the desktop belongs to, one is for the room of that user.
This makes life easy and I can get rid of the desktop list in our wiki. E.g.
User: Dennis Cabooter
Room: 16.14
For example if a user calls me with a problem, I need to find which desktop belongs to him. Now I have a few possibilities to do this:
Name=Value > Regexp > .*=.*Cabooter
Or:
Name=Value > Name= > Name=Cabooter
It would be nice if that could be a little more easy. E.g.
Name=Value > Name= > Cabooter
And:
Name=Value > Value= > Name
For example if I want to list all the nodes that have the Name/Room keys set. Maybe I forgot one, and in this case I don't have to check all nodes one by one.
Additionally to the "Regex" criterium, it would be nice if was possible to search on "Part of string" without knowing how to do regexes.
This would apply to all search criteria in Rudder.
Updated by Dennis Cabooter almost 10 years ago
Maybe it's a little confusing that I used the Name key in the above examples. I also made a mistake in the above examples.
Let's do it with the Room key to make sure things are clear.
User: Dennis Cabooter
Room: 16.14
Now I can do:
Name=Value > Regexp > .*=.*16.14
Or:
Name=Value > Name= > Room=16.14
It would be nice if that could be a little more easy. E.g.
Name=Value > Name= > Room
And:
Name=Value > Value= > 16.14
For example if I want to list all the nodes that have the Name/Room keys set. Maybe I forgot one, and in this case I don't have to check all nodes one by one.
Additionally to the "Regex" criterium, it would be nice if was possible to search on "Part of string" without knowing how to do regexes.
This would apply to all search criteria in Rudder.
Updated by Dennis Cabooter almost 10 years ago
One thing to add, but maybe it should be a separate ticket. The properties have key=value pairs. But in the API and in searching you call it name=value. This is quitte confusing.
Updated by François ARMAND almost 10 years ago
Thanks, and of course you are right.
Could you open a different ticket for the last comment, clearly a bug in consistancy.
Updated by François ARMAND almost 10 years ago
Thikning of it, the first problem seems to be that there is no online documentation about what is allowed in each field. If there was example of regex (or authorized units, for that matter), it would ease the pain - not a solution to that problem, but an other missing thing that make it even worse.
See http://www.rudder-project.org/redmine/issues/3616 http://www.rudder-project.org/redmine/issues/113
Updated by Benoît PECCATTE over 9 years ago
- Category set to Web - UI & UX
- Target version set to Ideas (not version specific)
Updated by François ARMAND over 4 years ago
- Status changed from New to Resolved
It is now (rudder 5.0)! You have access to json path, which is a big improvement.