[
https://issues.apache.org/jira/browse/SLING-7735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-7735.
------------------------------------
Resolution: Fixed
Fixed in
https://github.com/apache/sling-org-apache-sling-installer-factory-configuration/commit/0df065077af77f07955f9420158b008d73ce5ed3.
> OSGi installer configuration is marked as "IGNORED" in case the
> ConfigurationAdmin contains the correct configuration state already
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-7735
> URL: https://issues.apache.org/jira/browse/SLING-7735
> Project: Sling
> Issue Type: Bug
> Components: Installer
> Affects Versions: Installer Configuration Factory 1.1.2
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: Installer Configuration Factory 1.2.0
>
> Attachments: SLING-7735-v01.patch
>
>
> If I have a repository which first contains
> {code}
> .../config/myPID [sling:OsgiConfig]
> {code}
> and this is being changed to
> {code}
> .../config/myPID.config [nt:file]
> {code}
> The latter configuration is marked as {{IGNORED}} in the OSGi installer. This
> is the case, because the old configuration already had the correct data and
> hence the configuration has not been updated via the ConfigurationAdmin. The
> state is rather confusing though, because in fact, exactly that configuration
> is installed in the system. Therefore I would propose to mark the
> configuration installer resource rather with {{INSTALLED}}.
> This would be especially helpful in the context of the health check being
> contributed via SLING-5888 as that will fail for every configuration in any
> other state but {{INSTALLED}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
