Hi Robert, I can certainly disable writeback (or remove the jcr-installer-provider completely), but that does make the usefulness of the webconsole somewhat limited. Any changes to configuration via the webconsole are gone after the server has restarted which isn't what I was expecting.
Are you suggesting that a new "Feature Model Installer Provider" implementation would be required to write back the configuration changes to a feature model json file that can be loaded as additional arguments to the launcher script? For example: launcher -f feature-oak_tar.json -f webconsole-writeback-configs.json -CC "*=MERGE_LATEST" If that is the right approach, then maybe it would be good to detect that the feature model is being used and disable the writeback support form jcr-install-provider and file-install-provider automatically so it isn't so confusing? Regards, Eric On Wed, Dec 7, 2022 at 5:04 AM Robert Munteanu <[email protected]> wrote: > Hi Eric, > > On Sun, 2022-11-27 at 12:38 -0800, Eric Norman wrote: > > Have I missed something or any other thoughts? > > I am not an expert in this area, but I think this is a scenario where > the feature model and the OSGi installer conflict. Have you tried > disabling the writeback for the installer, as documented at [1]? > > Thanks, > Robert > > [1]: > > https://sling.apache.org/documentation/bundles/jcr-installer-provider.html#write-back-support-1 >
