Bug #15640

Built in File Content technique does not warn about using cfengine variable syntax in file content

Added by Janos Mattyasovszky 5 months ago. Updated about 2 months ago.

Target version:
Pull Request:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:


When using $(text) or ${text} as in the File content part of technique "File content version 8.0", there is no warning about escaping or not using them, otherwise you might hit issue #15167.

Please consider adding an appropriate warning label to each of the affected input fields if this is still applicable.

Suggesting it as Major because it will break the technique with no visible error and no real input that it does not work other than it does not work, and adding a visual information should be quite trivial...

Related issues

Related to Rudder - Bug #15167: Invalid detection of empty strings for edition in TechniquesReleasedActions



Updated by Janos Mattyasovszky 5 months ago

  • Related to Bug #15167: Invalid detection of empty strings for edition in Techniques added

Updated by François ARMAND 4 months ago

  • Target version set to 5.0.14

Updated by Vincent MEMBRÉ 4 months ago

  • Target version changed from 5.0.14 to 5.0.15

Updated by François ARMAND 3 months ago

  • Assignee set to Nicolas CHARLES
  • Priority changed from 70 to 69

Adding in the field documentation the warning is easy, and we should defenitly do that. Having a real-time warning based on the input text is not possible right now (we don't know on rudder what are the defined variables on nodes). We could rule out some inputs, thought (like "no . in the variable name").

So for now, step 1: add warning in field documentation.


Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 5.0.15 to 5.0.16
  • Priority changed from 69 to 67

Also available in: Atom PDF