User story #6244
closed
Automatic directive naming
Description
Hi,
a very nice helper would be to be able to set a "naming scheme" or "naming template" with each technique.
When one instantiates it, it could pre-fill the name to a text like
"PKG_INSTALL <project> <purpose> <package>"
The user would still need to adjust it, but lose one interruption to the workflow.
("err. what was i gonna call it? how did we think we should name them? why am i even at work?")
Updated by François ARMAND almost 10 years ago
- Category set to Web - Config management
- Status changed from New to 8
- Target version set to 3.1.0~beta1
Oh yes so much yes I want that !
Updated by François ARMAND almost 10 years ago
A good idea would be to (pre)name differently Directives from unique technique:
- unique Techniques lead to directive with the same name as them
- non-uniuqe Techniques lead to a more specific directive name
Updated by
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.0~rc1 to 3.1.0
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.0 to 3.1.1
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 3.1.1 to 3.1.2
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.1.2 to 3.1.3
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.1.3 to 3.1.4
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.1.4 to 3.1.5
Updated by François ARMAND about 9 years ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND about 9 years ago
OK, so the first quick win for that one is to use the technique name for every technique.
A more elaborated scheme would imply to actually set the text somewhere (most likelly in the metadata.xml, because it is here for just that kind of thing, but that mean modifying these file for the feature to be of any use, so a whole lot more code...)
Updated by François ARMAND about 9 years ago
- Target version changed from 3.1.5 to 3.2.0~beta1
Updated by François ARMAND about 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/942
Updated by François ARMAND almost 9 years ago
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ almost 9 years ago
- Pull Request changed from https://github.com/Normation/rudder/pull/942 to https://github.com/Normation/rudder/pull/976
Updated by François ARMAND almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|eeefbea148ea1beface6fabd45586d8eb10c8744.
Updated by Vincent MEMBRÉ almost 9 years ago
Applied in changeset rudder|e6244b2f31ceffd076897196dc8c3a21dbf2be40.
Updated by Vincent MEMBRÉ almost 9 years ago
- Subject changed from Feature idea: automatic directive naming to Automatic directive naming
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.2.0~beta1 which was released today.