Actions
Bug #10363
closedVariable * techniques description refers to CFEngine technical vocabulary
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
For the three Variable techniques, the description use term that are very CFEngine specific, and will be very strange for new comes in Rudder who don't have a CFEngine previous experience.
For example, for 'Variable (string)', we have the following description:
Configures a generic CFEngine variable in a common bundle, to be used in another Technique. This Technique does nothing by itself, you must reuse the variable(s) you will create here in another Technique with the form: ${generic_variable_definition.variablename}
We really don't need all the bundle & co thing. Something along the following text will be clearer:
Define new variables that can be used in other Techniques or Directive parameters with the syntax: ${generic_variable_definition.variablename}. That expression will be expanded to the value defined for "variablename" below.
I propose to do the change only in 4.1 to go with other naming evolution done in #10214
Actions