Hi,

The feature configuration (KARAF-3100) seems to have conflicting rules when 
appending new feature configuration values to an existing configuration. If the 
feature file contains a new config key, then all values are taken from the 
feature config keys. But the code before it puts only new values to component 
configuration.

So the FeatureConfigInstaller flow is:

1.       installFeatureConfigs uses existing values and only appends new ones 
(lines 114-118)

2.       updateStorage overwrites all values from the ones in feature 
configuration (lines 266-275)

I think this is a bug: it seems that the intention is to keep the existing 
configuration as is and only append new values. Which makes more sense to me.

We can provide a small PoC if necessary.


br,
Jami



P PLEASE CONSIDER OUR ENVIRONMENT BEFORE PRINTING THIS EMAIL.

This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments. Thank you.

Reply via email to