Description

Add an audit log trail for document changes and a way to create versions for documents.

Related Issue

6

5

Motivation and Context

When updating documents it currently is not recorded who did the change nor that a change happened at all. This PR adds this functionality by creating empty files in R2 where it stores the information about the author(s) in the metadata. Additionally, it allows a user to request that the current state becomes a version which means that in addition to the above metadata the file is not empty but captures the content in the document at the time of the request. The versions as well as the audit log history is exposed via a new endpoint.

How Has This Been Tested?

Tested locally against live storage

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Release notes

Implement /versionlist route for listing versions of a document.
Implement /versionsource route for POSTing and GETing a version of a document.
Audit logs are automatically created upon POST with the people associated with an edit.
Audit logs and versions are de-coupled from the main content tree so they are preserved even upon deletion.

adobe / da-admin

Versioning & Audit Logs #27