[
https://issues.apache.org/jira/browse/SLING-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870540#comment-13870540
]
Carsten Ziegeler commented on SLING-3315:
-----------------------------------------
We can't use the configurations stored in the repository as the source - the
only truth is represented by the configuration admin.
So we either come up with a REST api for the configuration admin or we stick
with the approach of having a wrapper api for just replication configurations.
I assume that there will be an OSGi spec for the REST api at some point this
year - and I think doing this right is a rather larger task, so maybe the
specific replication wrapper api is the better option
> Refactor replication HTTP API
> -----------------------------
>
> Key: SLING-3315
> URL: https://issues.apache.org/jira/browse/SLING-3315
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Marius Petria
> Labels: replication
> Attachments: SLING-3315.patch
>
>
> Refactor HTTP API in order to access independently the configuration of an
> agent and the service API for an agent. This was needed because there are
> times when a configuration can exist without an agent being available (e.g.
> when the agent is not disabled).
> Proposed API:
> Managing configuration
> POST /system/replication/config/agent (creates and agent cofig)
> GET /system/replication/config/agent (retrieves all agents config)
> POST /system/replication/config/agent/{agentName} (updates and agent)
> GET /system/replication/config/agent/{agentName} (retrieves the agent
> config)
> DELETE /system/replication/config/agent/{agentName} (deletes an agent config)
> Managing agent
> POST /system/replication/config/agent/{agentName} (schedules a package
> for replication or removes one from the queue)
> GET /system/replication/config/agent/{agentName}/queue (lists the
> packages in the queue)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
