From 69d4c8dce6e771fca7538de53eeac6e4996315b6 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 30 Aug 2018 15:52:44 -0400 Subject: [PATCH] devblog --- CHANGELOG | 3 +++ .../day_515__S3_exporttree_with_versioning.mdwn | 10 ++++++++++ 2 files changed, 13 insertions(+) create mode 100644 doc/devblog/day_515__S3_exporttree_with_versioning.mdwn diff --git a/CHANGELOG b/CHANGELOG index 514eaaafab..0fa699eeae 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -25,6 +25,9 @@ git-annex (6.20180808) UNRELEASED; urgency=medium locales too. * Stop using external hash programs, since cryptonite is faster. * Fix build on FreeBSD. + * S3: Support buckets with versioning enabled. When a remote + is configured with exporttree=yes versioning=yes, git-annex can + download past versions of exported files from it. -- Joey Hess Wed, 08 Aug 2018 11:24:08 -0400 diff --git a/doc/devblog/day_515__S3_exporttree_with_versioning.mdwn b/doc/devblog/day_515__S3_exporttree_with_versioning.mdwn new file mode 100644 index 0000000000..27ff00d5aa --- /dev/null +++ b/doc/devblog/day_515__S3_exporttree_with_versioning.mdwn @@ -0,0 +1,10 @@ +Most of the way done with implementing support for export to S3 buckets +with versioning enabled. This will make the files from the most recent +`git annex export` be visible to users browsing the bucket, while letting +git-annex download any of the content from previous exports too. + +Still need to test it. And, deletion of old content from such a bucket is +not supported, and my initial thoughts are that it might not be possible +in a multi-writer situation. I need to think about it more. + +This work is supported by the NSF-funded DataLad project.