Revision Management¶
GET : revisions¶
https://dydra.com/system/accounts/<account name>/repositories/<repository-name>/revisions
Headers¶
Content-Type: text/plain
Response¶
Returns a list of the repository revisions.
DELETE : all revisions¶
In order to delete all revisions, that is, to clear a repository:
https://dydra.com/system/accounts/<account>/repositories/<repository>/revisions
Response¶
Returns a graph describing the task solution field.
DELETE : selected history¶
To not delete all revisions, but instead preserve the revisions starting at a boundary revision and trim the history to that boundary, one can specify this boundary revision with a HTTP parameter revision-id and specify a mode for the delete operation. This affects all revisions before the boundary.
The boundary is to be specified as a Revision Designator Specification, usually a revision UUID, its ordinal, a timestamp, HEAD, or TAIL. If left out, the most recent revision is used, that is, the equivalent to HEAD.
One can either set the mode to delete-history:
https://dydra.com/system/accounts/<account>/repositories/<repository>/revisions?mode=delete-history&revision-id=<revision-designator>
This remove all revisions prior to the boundary with all their data, and results in a state that is equivalent to a new, empty repository into which all remaining revisions have been inserted.
Alternatively, one can specify the mode as project-history:
https://dydra.com/system/accounts/<account>/repositories/<repository>/revisions?mode=project-history&revision-id=<revision-designator>
This also removes all revisions prior to the boundary but instead of just deleting them, it projects their state to the boundary, and thus causes the boundary revision to reflect all data through to that point.
In other words, the mode delete-history will cause the specified boundary to be equivalent to a new, empty repository. While the mode project-history will cause the boundary to have all the content that the repository’s revision had prior to this operation but without its history. All data appears to have been inserted at that revision.
If the mode is not sepecified, it defaults to all, which will clear the repository by deleting all revisions, see section DELETE all revisions.
Headers¶
Content-Type: text/plain
Response¶
Returns a list of the repository revisions that have been deleted, that is, all revisions prior to the specified revision-id.
In case no revisions have been deleted, it returns a HTTP status response 204 No Content with no content. For example, if revision-id referenced the first revision, which is valid but has no history to delete.