You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/01/20 11:12:00 UTC

[jira] [Created] (SLING-9014) Configuration Installer: Optionally clean up/remove existing configurations from factory

Konrad Windszus created SLING-9014:
--------------------------------------

             Summary: Configuration Installer: Optionally clean up/remove existing configurations from factory
                 Key: SLING-9014
                 URL: https://issues.apache.org/jira/browse/SLING-9014
             Project: Sling
          Issue Type: Improvement
          Components: Installer
    Affects Versions: Installer Configuration Factory 1.2.4
            Reporter: Konrad Windszus


It should be possible to automatically remove non-OSGi Installer managed configurations from a given configuration factory. 
Often it is hard/impossible to predict with which name/alias they have been created on existing instances, but you want to maintain all configurations belonging to that particular factory PID via OSGi installer.

Open Questions: 
# When to do the cleanup? It must happen after all resources have been processed. 
# How to indicate via JCR/File Installer, that you want to perform a cleanup? Maybe a specific node/file name like <factoryPid>.config.cleanup (with empty content)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)