Rudder

When a property is inherited by a group, to override it at a node level, you have to:

• create a property with the same name to override it, but then, you "loose" the information of what the local override value was as only the merged result is displayed.
• if a local override already exists, you have to use the "edit" button on the property, but it displays whole "merged result" to edit instead of the local override already defined, which mean that a non attentive user will create a faulty local override without knowing it, and will prevent the node to receive any value update from the group

An example below:
In my group Ubuntu, I define the following "test" property:

{"a": "a", "b": "b", "c":"c"}

On a node within this group, I define a new property "test" as:

{"b": "bob"}

The resulting effective property is:

{
  "a": "a",
  "b": "bob",
  "c": "c" 
}

So far, everything it fine, except that I "lost" the information of what is the value of my local override (it is displayed on the tooltip, which is not super user friendly)

Now, I want to modify the local override to change the value of a, I have to click on the "edit" button of the property, which displays the current effective value to edit:

{
  "a": "a",
  "b": "bob",
  "c": "c" 
}

Which I modify to:

{
  "a": "alice",
  "b": "bob",
  "c": "c" 
}

This is the big issue here, my local override now also contains an override to the "c" key, which I did not want.
To demonstrate it, if I go back to the group node page and modify the initial "test" property to:

{"a": "a", "b": "b", "c":"charly"}

The charly value will never reach the node...