...
- Should allow CRUD operations for agent configs
-
Configs need to have a JCR representation (either the default one or a new one) in order to support the following workflow: configure all agents on a author instance and replicate configuration to all publish instances.
Command API
- Should allow Replicate/Import Package/Export Package
-
Commands might be issued to multiple agents at once (but this not a strong requirement I think)
Monitoring API
- Should allow inspection to internal queues of replication agents
- Should allow inspection of commands history
...
- Create config - POST /system/replication/config
- Read config - GET /system/replication/config/publish{config identifier}
- Update config - PUT /system/replication/config/publish{config identifier}
- Delete config - DELETE /system/replication/config/publish{config identifier} or POST with :operation=delete
Command API
For command and monitoring APIs we can have two kind of APIs. We do not need to implement both variants, and I do not think there is a strict requirement for choosing one variant or another.
...
Replication - HTTP API (proposal) 