Actions
Bug #15640
closed
Built in File Content technique does not warn about using cfengine variable syntax in file content
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | Technique editor and level 1 Techniques
Effort required:
Priority:
59
Name check:
To do
Fix check:
To do
Regression:
Description
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...
Updated by 
Updated by 
Updated by 
Updated by 
Updated by
Actions