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
Updated by François ARMAND over 4 years ago
- Target version set to 6.1.0~rc4
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 32
The case seems rare and not very severe (keeping json formating is not needed often). And if it's the case, one can still define the corresponding on group properties.
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0~rc4 to 6.1.0
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.0 to 6.1.1
Updated by François ARMAND over 4 years ago
- Effort required set to Medium
- Priority changed from 32 to 16
I already spent more than one day on that.
Updated by Raphael GAUTHIER over 4 years ago
- Status changed from New to In progress
- Assignee set to Raphael GAUTHIER
Updated by Raphael GAUTHIER over 4 years ago
- Status changed from In progress to New
- Assignee changed from Raphael GAUTHIER to François ARMAND
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.1 to 6.1.2
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.2 to 6.1.3
- Priority changed from 16 to 15
Updated by François ARMAND over 4 years ago
- Target version changed from 6.1.3 to 6.1.4
Updated by Vincent MEMBRÉ over 4 years ago
- Target version changed from 6.1.4 to 6.1.5
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.5 to 6.1.6
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.6 to 6.1.7
Updated by Vincent MEMBRÉ about 4 years ago
- Target version changed from 6.1.7 to 6.1.8
- Priority changed from 15 to 14
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.8 to 6.1.9
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.9 to 6.1.10
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.10 to 6.1.11
Updated by Vincent MEMBRÉ almost 4 years ago
- Target version changed from 6.1.11 to 6.1.12
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.12 to 6.1.13
- Priority changed from 14 to 13
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.13 to 6.1.14
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.14 to 6.1.15
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.15 to 6.1.16
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by Benoît PECCATTE almost 3 years ago
- Category set to Web - Config management
Updated by François ARMAND almost 3 years ago
- Status changed from New to Rejected
We won't realisticly spend more time on that ticket. If anyone is impacted, please let us know so that we can know that the time spent worth it.
Actions