Project

General

Profile

Actions

Bug #15640

closed

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

Added by Janos Mattyasovszky over 2 years ago. Updated almost 2 years ago.

Status:
Rejected
Priority:
N/A
Category:
Techniques
Target version:
Severity:
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:
Priority:
59

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...


Related issues 1 (0 open1 closed)

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

Also available in: Atom PDF