Fix persist config values for custom components (#31862)
Closes #31858 Signed-off-by: Stephan Schrader <stephan.schrader@wallis.de> Signed-off-by: Stephan Schrader <zstephanz@gmail.com> Co-authored-by: Stephan Schrader <stephan.schrader@wallis.de>
This commit is contained in:
parent
acbbfde4ab
commit
4d64092119
2 changed files with 7 additions and 4 deletions
|
@ -1058,7 +1058,7 @@ public class RepresentationToModel {
|
|||
Set<String> keys = new HashSet<>(rep.getConfig().keySet());
|
||||
for (String k : keys) {
|
||||
if (!internal && !providerConfiguration.containsKey(k)) {
|
||||
break;
|
||||
continue;
|
||||
}
|
||||
|
||||
List<String> values = rep.getConfig().get(k);
|
||||
|
|
|
@ -229,6 +229,9 @@ public class ComponentsTest extends AbstractAdminTest {
|
|||
// Check value updated
|
||||
returned.getConfig().putSingle("val1", "one-updated");
|
||||
|
||||
// send a key / value which not contained in the original component config
|
||||
returned.getConfig().putSingle("not-a-config-key", "ten");
|
||||
|
||||
// Check null deletes property
|
||||
returned.getConfig().putSingle("val2", null);
|
||||
|
||||
|
|
Loading…
Reference in a new issue