Project

General

Profile

Actions
Copy link

Bug #23664

open

rudderc may produce malformed powershell scripts

Bug #23664: rudderc may produce malformed powershell scripts

Added by Félix DALLIDET about 2 years ago. Updated about 1 month ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
rudderc
Target version:
8.3.9
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I hate Rudder for that
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Priority:
74
Name check:
To do
Fix check:
To do
Regression:
No

Description

To reproduce, try to define a technique with the following content as input of any of the methods:

test $(grep -Pr --include=*.{sources,conf} '^\h*server\h+\H+' /etc/chrony/ | wc -l) -ge 3

The resulting powershell technique will have at least one line looking like:

$componentKey = "test $(grep -Pr --include=*.{sources,conf} '^\h*server\h+\H+' /etc/chrony/ | wc -l) -ge 3"

which is un-parsable for powershell as the comma is interpreted as a comma operator to define a list due to the `$()` used in the field.

Actions
Copy link

Also available in: PDF Atom