User story #4329
open
Proposal: categorized directives overview
Description
In rudder 2.8.x rules were not categorised. I used "labels" to categorise rules myself, in my case based on group names:
-
- CentOS desktops: edit common files
- CentOS desktops: install common packages
- RHEL servers: edit common files
- RHEL servers: install common packages
- Ubuntu servers: edit common files
- Ubuntu servers: install common packages
In rudder 2.9.0 rules are categorised, so they look like this and are more organised:
- CentOS desktops
- edit common files
- install common packages
- RHEL servers
- edit common files
-install common packages
- Ubuntu servers
- edit common files
- install common packages
The same I would like to see with directives. Now if I use a technique 20+ times, like Enforce File Content, the directive list gets long. For now also in directives I use "labels":
- Enforce File Content
- CentOS desktops: edit common files
- RHEL servers: edit common files
- Ubuntu servers: edit common files
- Install RHEL/CentOS packages
- CentOS desktops: install common packages
- RHEL servers: install common packages
- Install Ubuntu Packages
- Ubuntu servers: install common packages
I might make enemies with this proposal, but I want to give it a try:
In the rules overview you don't see a tree of directives, so why do I see a tree of techniques in the directive screen? I think it would be nice to choose the technique to use while creating or editing a directive. In the same way you choose (a) directive(s) and (a) group(s) from a list when you create a rule. For me it's not very useful to see the technique names as categories of directives. It would be really much more useful to see categories in directives, like this:
- CentOS desktops
- edit common files
- install common packages
- RHEL servers
- edit common files
-install common packages
- Ubuntu servers
- edit common files
- install common packages
And then if I click on the directive, I can see from which technique it comes. At the moment I have 20+ directives of Enforce File Content and there are more to come. The "labels" do help a little bit, but it's difficult to manage. My proposal is to change the directives overview to be much like the rules overview. The directives overview could be empty in the beginning, like the rules overview. And then, if you create a directive, you can choose the technique and technique version from a list.
Updated by François ARMAND over 10 years ago
- Assignee set to Jonathan CLARKE
Your proposal is very intersting in two aspects, that seems to fit nicely togeither:
- you categorize things by tags, not really by categories or tree
- you don't really care to categorize Directives by Technique, you want to categorize them by their use (or behaviour, or such).
So, the next step seems to be what you propose:
- Techniques does not appear in the Directive screen, but in place you have some kind of navigation panel + list of directives.
- the navigation panel could be some kind of tree like in the rule screen
- Creating a new Directive launch a widget (wizard ?) where you first select the Technique for the directive, then configure the Directive like today.
That's what you thought?
The next, next step could even be a merge of that "new directive" widget directly in the update rule screen, so that you can do everything from that place.
Jon, what do you thing about that ?
Updated by Dennis Cabooter over 10 years ago
That's a nice and clear description. Thank you! :)
Updated by François ARMAND about 10 years ago
It won't be on 2.10, but it's still something toward which we want to go.
Updated by Benoît PECCATTE almost 9 years ago
- Category set to Web - Config management
- Assignee deleted (
Jonathan CLARKE) - Target version set to Ideas (not version specific)