You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Timothee Maret (JIRA)" <ji...@apache.org> on 2016/07/19 21:15:21 UTC
[jira] [Created] (SLING-5872) Management of agent configurations
must identify configurations by name
Timothee Maret created SLING-5872:
-------------------------------------
Summary: 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
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)