Fix clean up staging directory after DuraCloud AIP upload#809
Open
camlyall wants to merge 1 commit intoartefactual:qa/0.xfrom
Open
Fix clean up staging directory after DuraCloud AIP upload#809camlyall wants to merge 1 commit intoartefactual:qa/0.xfrom
camlyall wants to merge 1 commit intoartefactual:qa/0.xfrom
Conversation
… staging directories
camlyall
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes an issue where temporary directories were not being deleted after DuraCloud uploads, causing disk space to be consumed by accumulated staging files.
The DuraCloud storage model was missing the
post_move_from_storage_servicehook that other storage backends implement. This hook is called after successful uploads to clean up staging directories.Changes
post_move_from_storage_service()method to theDuracloudclassThe issue can be found here: archivematica/Issues#1768