Hello Scott,
"develop" is 3.0.
Technically what is happening is that the Kura configuration service does forward all configuration updates to the OSGi ConfigAdmin. Which actually overwrites everything which is in the OSGi ConfigAdmin. It also only works with the Equinox ConfigAdmin, there
is some issue when using the Felix ConfigAdmin which causes duplicate entries. I am not sure what causes this up until now but I am not sure if it is worth tracking this down.
There are some know oddities with the Kura ConfigurationService and my hope is that we can replace the Kura ConfigurationService with the default OSGi ConfigAdmin in the 3.0 release cycle or in the following release.
[Scott] Does this mean that org.eclipse.kura.configuration.ConfigurableComponent will still be used to indicate a component that is to be presented in the Kura Admin UI? Or will there be something else (e.g. just using the metatype info?)
Another Admin UI question: Will Kura support ComponentFactories as ConfigurableComponents within the Kura Admin UI? e.g. and allow multiple instances of a service to be created via that ComponentFactory?
[Jens]
My idea is to only use the OSGi ConfigAdmin and provide a set of addons to that, implementing the features Kura need (encryption, rollbacks, import/export). But sticking to standard OSGi functionality and tooling for all the rest.