You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Marius Petria (JIRA)" <ji...@apache.org> on 2014/01/13 09:39:51 UTC
[jira] [Updated] (SLING-3315) Refactor replication HTTP API
[ https://issues.apache.org/jira/browse/SLING-3315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marius Petria updated SLING-3315:
---------------------------------
Description:
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)
was:
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
{code}
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)
{code}
Managing agent
{code}
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)
{code}
> 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
>
> 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)