sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konrad Windszus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-7735) OSGi installer configuration is marked as "IGNORED" in case the ConfigurationAdmin contains the correct configuration state already
Date Fri, 15 Jun 2018 07:46:00 GMT

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

Konrad Windszus updated SLING-7735:
-----------------------------------
    Description: 
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.

  was:
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}}.



> 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
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message