Description
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.
Attachments
Issue Links
- is related to
-
KARAF-3100 Add Option To Create Config Files For Feature Configs Instead Of Importing Directly Into Config Admin
-
- Resolved
-