[jira] [Resolved] (SLING-5872) Management of agent configurations must identify configurations by name

["Tommaso Teofili (JIRA)" <ji...@apache.org>]

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

Tommaso Teofili resolved SLING-5872.
------------------------------------
       Resolution: Fixed
    Fix Version/s: Content Distribution 0.2.0

thanks [~marett], I've merged your PR in r1753527.

> Management of agent configurations must identify configurations by name 
> ------------------------------------------------------------------------
>
>                 Key: SLING-5872
>                 URL: https://issues.apache.org/jira/browse/SLING-5872
>             Project: Sling
>          Issue Type: Bug
>          Components: Distribution
>    Affects Versions: Content Distribution Core 0.1.18
>            Reporter: Timothee Maret
>            Assignee: Timothee Maret
>             Fix For: Content Distribution 0.2.0
>
>
> Currently, the configurations are identified by the tuple {{(name,kind)}}.
> As a consequence, it is possible to create two configurations with the same name but different kind, using the Sling POST servlet on path
> {code}
> /libs/sling/distribution/settings/agents/<agentName>
> {code}
> This breaks the concept of having a single resource type (and thus a single agent) for a given type.
> This is somewhat related to SLING-5742, however it does not cover creation of agents via the OSGI consoles (only via the Sling POST servlet).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)