By now, the capsule is considered to be the same a proxy, therefore
I've build the capsules entry point, that uses the smart proxy
on backend, but uses the capsule wording for convenience.
I've added the following API
GET /api/capsules - list the capsules
GET /api/capsules/:id - hos the capsule details
GET /api/capsules/:id/content/lifecycle_environments - environments attached to the capsule for syncing content
POST /api/capsules/:id/content/lifecycle_environments - attach lifecycle environment to the capsule (hamm
DELETE /api/capsules/:id/content/lifecycle_environments/:environment_id - remove lifecycle environment from the capsule
POST /api/capsules/:id/content/sync - synchronize the capsule (optionally, one can limit the synchronization to one environemnt with environment_id)
The corresponding hammer commands are:
hammer capsule list
hammer capsule info --id 1
hammer capsule content lifecycle-environments --id 1
hammer capsule content add-lifecycle-environment --id 1 --environment-id 1
hammer capsule content remove-lifecycle-environment --id 1 --environment-id 1
hammer capsule content synchronize --id 1
hammer capsule content synchronize --id 1 --environment-id 1
Updated by 
Updated by