Actions
Bug #17829
closedDatasource properties are merged, not replaced
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
Description
If we have a json property from a datasource, then sub-items are merged, not replaced with new value.
For example:
Run 1:
{"env":"prod", "merge": { "test1":"val1" } }
Run 2:
{"env":"prod", "merge": { "test2":"val2" } }
Result on node to:
{"env":"prod", "merge": { "test1":"val1", "test2":"val2" } }
It is suprising. It should replace value, or even better: replace value by default, and let user have an option to chose to merge (but clearly don't do that by default).
Updated by François ARMAND over 4 years ago
- Status changed from New to In progress
Updated by François ARMAND over 4 years ago
- Status changed from In progress to Resolved
Resolved in rudder with #17830
Updated by François ARMAND over 4 years ago
- Related to Bug #17830: Updating property merge them in place of replacing them added
Actions