Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Installer Console 1.0.2
-
None
-
None
Description
Currently the web console at /system/console/osgi-installer exposes the history/state of the OSGi installer. In case the state is not reflecting reality for some reason, there should be a possibility to remove that history and restart the according bundles with a button inside that console.
The actions which should be triggered under the hood should be
- remove the data file RegisteredResourceList.ser
- restart the bundle org.apache.sling.installer.core
That should lead to every provider being asked about all entities which are then processed again so you end up with state again where the most prioritized entites are deployed.
Attachments
Issue Links
- is blocked by
-
SLING-6313 Sling installer can duplicate factory configurations if an invalid RegisteredResourceList.ser is found
- Closed
- is related to
-
SLING-4894 Allow failed package install to retry later on
- Closed
- relates to
-
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
- Open