Actions
Bug #17830
closed
Updating property merge them in place of replacing them
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
It's the root cause of: https://issues.rudder.io/issues/17829
If we have a json property in a node, then sub-items are merged, not replaced with new value.
For example:
Prop time 1:
{"env":"prod", "merge": { "test1":"val1" } }
Update with:
{"env":"prod", "merge": { "test2":"val2" } }
Result on node to:
{"env":"prod", "merge": { "test1":"val1", "test2":"val2" } }
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 Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/3101
Updated by François ARMAND over 4 years ago
- Related to Bug #17829: Datasource properties are merged, not replaced added
Updated by François ARMAND over 4 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|8a339433c13b3854ddfd0734dfd95cb8160053c7.
Updated by François ARMAND over 4 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 4 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.1.1 which was released today.
Actions