Revisions
Google drive stores revisions of files. When you upload a change to an existing
file to google drive using rclone it will create a new revision of that file.
Revisions follow the standard google policy which at time of writing was
They are deleted after 30 days or 100 revisions (whatever comes first).
They do not count towards a user storage quota.
Is there a way to control this during upload? Something like:
--max-revisions=200
or
--max-revision-age=60
or even better:
--google-drive-keep-forever
If such a thing is possible or available, is there a way to enable it for previously uploaded files? Clicking the “keep forever” check box for each file is impossible.
Thanks again for all your hard work and the wonderful program you have made for us.
Looks like keeping revision forever might be possible…
In the v3 api - you can set keepVersionForever in the file upload.
In the v2 API you can pin a revision. It says about this
Whether to pin the head revision of the uploaded file. A file can have a maximum of 200 pinned revisions. (Default: false)
and the SDK docs (no mention of 200 limit)
// Pinned: Whether this revision is pinned to prevent automatic purging.
// This will only be populated and can only be modified on files with
// content stored in Drive which are not Google Docs. Revisions can also
// be pinned when they are created through the
// drive.files.insert/update/copy by using the pinned query parameter.
I think this is probably the equivalent of keepRevisionForever but I’m not 100% certain.
rclone uses the v2 API. It would be relatively easy to add a --drive-keep-forever flag which set the pinned attribute. Moving to the v3 API is a lot more work though!