expose and use size-only in data sync s3 sync paths #4
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.
Details
Why is this necessary?
For merscope analysis, the data sync fails for repeated downloads from aws s3 buckets in Storage-AIBS account. It fails to verify data already written to efs locations because the s3 buckets use server side encryption and we cannot generate ETags effectively.
The solution is to allow for data sync to use
size_only
when doing comparisons. This is considered a near-term fix.Testing