Story #9592

[FUSE] rmdir on CollectionDirectory sets expires_at

Added by Brett Smith about 3 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
07/13/2016
Due date:
% Done:

0%

Estimated time:
Story points:
-

Description

As of this writing, if you rmdir a CollectionDirectory in FUSE, it uses the collections/delete API. Instead, it should calculate a timestamp that is defaultTrashLifetime (or, if that's not set in the discovery document, blobSignatureTtl) seconds in the future, and update the collection's expires_at attribute to that value. The CollectionDirectory should still be removed from its parent, as now, because expiring collections do not appear in most directory listings (see #9584).


Related issues

Related to Arvados - Story #9278: [Crunch2] Document/fix handling of collections with non-nil expires_at fieldIn Progress06/01/2016

Copied from Arvados - Feature #3900: [Workbench] Trash button on collection uses "delete" API instead of setting expires_at/trash_atResolved02/10/2017

History

#1 Updated by Brett Smith about 3 years ago

  • Tracker changed from Feature to Story

#2 Updated by Tom Morris almost 3 years ago

  • Assigned To changed from Brett Smith to Tom Morris

#3 Updated by Tom Morris over 2 years ago

  • Target version set to Arvados Future Sprints

Also available in: Atom PDF