[SLING-5872] Management of agent configurations must identify configurations by name

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Content Distribution Core 0.1.18
• Fix Version/s: Content Distribution Core 0.2.0
• Component/s: Content Distribution
• Flags: Patch
• Assignee: Timothee Maret
• Reporter: Timothee Maret
• Created: 19/Jul/16 21:14
• Updated: 16/Feb/17 13:30
• Resolved: 20/Jul/16 14:47

Description

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

/libs/sling/distribution/settings/agents/<agentName>

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

Issue Links

• is duplicated by: SLING-5742 Do not allow registration of agents/exporters/importers with duplicate names
• is related to: SLING-5900 Improve create agents API handling of duplicate IDs
• relates to: SLING-5742 Do not allow registration of agents/exporters/importers with duplicate names
• links to: GitHub Pull Request #154