Project

General

Profile

Actions

User story #6244

closed

Automatic directive naming

Added by Florian Heigl over 6 years ago. Updated about 4 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Config management
Target version:
Suggestion strength:
User visibility:
Effort required:

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?")


Subtasks 3 (0 open3 closed)

Bug #10397: Missing "default-directive-names.conf" example fileReleasedAlexis MOUSSETActions
Bug #10398: Missing documentation for "default-directive-names.conf" ReleasedAlexis MOUSSETActions
Bug #10419: Move directives-names doc out of advanced usageReleasedFrançois ARMANDActions
Actions #1

Updated by François ARMAND over 6 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 !

Actions #2

Updated by François ARMAND about 6 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

Actions #3

Updated by Benoît PECCATTE about 6 years ago

  • Status changed from 8 to New
Actions #4

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.0~beta1 to 3.1.0~rc1
Actions #5

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.0~rc1 to 3.1.0
Actions #6

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.0 to 3.1.1
Actions #7

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 3.1.1 to 3.1.2
Actions #8

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.2 to 3.1.3
Actions #9

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.3 to 3.1.4
Actions #10

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 3.1.4 to 3.1.5
Actions #11

Updated by François ARMAND over 5 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #12

Updated by François ARMAND over 5 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...)

Actions #13

Updated by François ARMAND over 5 years ago

  • Target version changed from 3.1.5 to 3.2.0~beta1
Actions #14

Updated by François ARMAND over 5 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
Actions #15

Updated by François ARMAND over 5 years ago

  • Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
Actions #16

Updated by Vincent MEMBRÉ over 5 years ago

  • Pull Request changed from https://github.com/Normation/rudder/pull/942 to https://github.com/Normation/rudder/pull/976
Actions #17

Updated by François ARMAND over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #19

Updated by Vincent MEMBRÉ over 5 years ago

  • Subject changed from Feature idea: automatic directive naming to Automatic directive naming
Actions #20

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.2.0~beta1 which was released today.

Actions

Also available in: Atom PDF