Actions
Bug #17691
closedFormating is lost for global param string looking like json
Status:
Rejected
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
13
Name check:
To do
Fix check:
To do
Regression:
Description
If we have a global parameter of type `string` which is a json, then when used in file content with ${node.properties[]}
, then the formating is lost. That does not happen if the string is not json, or if the property is defined on node.
Global param:
On node:
Gives after enforce file content
==>
json_string_6_0 -- {"i'm not":"json"} -- jsonStringOnNode -- { "that's" : "not json but string" } -- stringWithReturn --- I'm a multiline string! with spaces ---
Files
Actions