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 2023/05/09 19:06:00 UTC

[jira] [Commented] (SLING-11864) Configuration merge/default values not considered in OSGi Installer Configuration Printer Web Console

    [ https://issues.apache.org/jira/browse/SLING-11864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721047#comment-17721047 ] 

Carsten Ziegeler commented on SLING-11864:
------------------------------------------

I think default values (metatype) are correctly handled, so the question is only whether the console plugin that displays the JSON should reflect the configuration as stored in config admin or respect the merge schemes directive. That's a design decision for the console plugin.

If you look at /apps/system/config/org.apache.jackrabbit.vault.packaging.impl.PackagingImpl.cfg.json you will see that the merge scheme is correctly handled and that configuration only contains the single additional property

> Configuration merge/default values not considered in OSGi Installer Configuration Printer Web Console
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-11864
>                 URL: https://issues.apache.org/jira/browse/SLING-11864
>             Project: Sling
>          Issue Type: New Feature
>          Components: Installer
>    Affects Versions: Installer Console 1.1.0
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>             Fix For: Installer Console 1.1.2, Installer Configuration Factory 1.4.4
>
>
> Despite https://sling.apache.org/documentation/bundles/configuration-installer-factory.html#merging-of-configurations stating that
> bq. Similar, for write back and the OSGi Installer Configuration Printer Web Console only the properties with different configuration values than the default configuration are written back/exposed.
> I still see all values which differ from the metatype default value being exposed at {{/system/console/osgi-installer-config-printer}}. I tried with a distribution which has two configurations
> {code}
> * org.apache.jackrabbit.vault.packaging.impl.PackagingImpl: 2a425da9bfe3907800abf828d7dba911/200, jcrinstall:/apps/system/config/org.apache.jackrabbit.vault.packaging.impl.PackagingImpl.cfg.json, INSTALLED, 
>   - 311121c892dc31cecae4b5844a5855e9/50, launchpad:resources/config/org.apache.jackrabbit.vault.packaging.impl.PackagingImpl.config, INSTALL, Another resource with the same entity id but a higher version or priority or digest found (in that order, the latter only in case the version is a SNAPSHOT)!
> {code}
> and framework property {{sling.installer.config.mergeSchemes = launchpad}}.
> Still values from both sources are exposed at {{/system/console/osgi-installer-config-printer?pid=org.apache.jackrabbit.vault.packaging.impl.PackagingImpl&format=JSON}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)