You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (Jira)" <ji...@apache.org> on 2021/06/24 09:22:00 UTC

[jira] [Resolved] (SLING-10538) Support merging of configurations

     [ https://issues.apache.org/jira/browse/SLING-10538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carsten Ziegeler resolved SLING-10538.
--------------------------------------
    Resolution: Fixed

Implemented support in configuration factory:

https://github.com/apache/sling-org-apache-sling-installer-factory-configuration/commit/89448aa1b524a35e58467a92edad20039731a0d6

The factory can be configured with a framework property sling.installer.config.mergeSchemes. If this is set, for example to "launchpad" then all configurations from launchpad act as default configurations and if the new configuration uses the same values they are filtered out before writing it back

> Support merging of configurations
> ---------------------------------
>
>                 Key: SLING-10538
>                 URL: https://issues.apache.org/jira/browse/SLING-10538
>             Project: Sling
>          Issue Type: Improvement
>          Components: Installer
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Installer Core 3.11.6, Installer Configuration Factory 1.3.6
>
>
> Today, the installer support for configurations applies a configuration as a unit. While this is useful for many use cases, there are use cases where for example an application provides an ootb OSGi configuration and the customization of that configuration should only contain the changed properties but not repeat all properties from the application.



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