[SLING-7736] OSGi Installer: Update OSGi installer's resource state in case of configuration/bundle updates outside of the OSGi Installer when JCR Installer Writeback is disabled

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: Installer Core 3.8.10, Installer Configuration Factory 1.2.0
• Component/s: Installer
• Assignee: Unassigned
• Reporter: Konrad Windszus
• Created: 15/Jun/18 08:06
• Updated: 06/Mar/19 14:32

Description

Currently the state of an OSGi installer's resource is only updated whenever it is newly added to the queue and subsequently processed. Manual configuration/bundle changes outside of the OSGi installer don't change the OSGi installer's resource state.

Actually, with the help of the BundleListener (https://osgi.org/javadoc/r5/core/org/osgi/framework/BundleListener.html) and the ConfigurationListener (https://osgi.org/javadoc/r5/cmpn/org/osgi/service/cm/ConfigurationListener.html) the OSGi installer could mark the according OSGi installer resources as IGNORED in case they have been overwritten.

The tricky part is to filter out those event's which have been caused by the OSGi installer itself. The resource's digest cannot be used for that, as that is completely calculated by the Provider (i.e. is different between JCR and file provider).

That would improve the effectiveness of the health check from SLING-5888 and also allows the OSGi installer to better enforce its state during reinstallation in the future.

Issue Links

• is related to: SLING-5887 OSGi Installer: configuration factory instances and regular configuration instances differ in terms of overwrite behaviour
• is related to: SLING-5745 Provide a button to clear all registered entities and reinstall those
• relates to: SLING-5888 Health Check for detecting not-installed configurations/bundles from the OSGi installer