Add catalog functionality to prevent re-downloads #99
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.
Creates a JSON catalog file with etag and md5 at time of download. This catalog is used on subsequent runs to determine whether the file needs redownloaded. Having this in place, how the etag is derived is irrelevant (as S3 can use several methods for generating it) and can be simply used as a remote change indicator. Local changes are determined by the stored md5.
Using this catalog becomes the default but it can be turned off via node attribute.
Also fixes issues with default owner/group always being null and the
fileresource always being updated if owner/group/mode were different than what the new file happened to be downloaded with.