Optional s3 sync flag to address https://github.com/aws/aws-cli/issues/599 #824
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.
Implements an optional
--exact-timestamps
flag for theaws s3 sync
operation. This flag provides a workaround for one of the issues described in #599: failure to synchronize same-sized files when a newer version exists in S3. With this flag set, files will be synchronized unless the local and S3 timestamps match exactly.This is essentially an implementation of the first Proposed Solution described in #599, but implemented as an optional feature as opposed to changing default behavior: