Project

General

Profile

Actions
Copy link

Bug #12812

open

Wrong reports on "File content" when using undefined variables

Added by Félix DALLIDET over 6 years ago. Updated 5 months ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Generic methods
Target version:
7.3.17
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Priority:
0
Name check:
Fix check:
Regression:

Description

I tried to use file content with a call to a undefined variable on rudder 4.3.3

In file content:

file: /tmp/fda
value: ${my_prefix.my_name}
enforce: true

I end up with a GM reporting "compliant", not a repaired one, creating the file /tmp/fda with the following content:
${my_prefix.my_name}

I was expecting an error report, or at least a repaired and a warning.

Actions
Copy link

Also available in: Atom PDF