[Storage Cleaner] Move unarchiving logic to cleaning jobs #390
Conversation
This file contains 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
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.
I originally designed the storage cleaner with the idea that
StorageAdapters would abstract out lots of the FS-related operations. I included handling archives in that abstraction, which turns out to have been a bad idea. This PR moves the responsibility of handling unarchiving from theStorageAdapterto the storage cleaning job that needs to use unarchiving. It should hopefully make the storage cleaner easier to work with (especially since none of thefull_pathstuff from #379 will be needed anymore).