Using 1.3.21 of aws cli on Windows 7
Appears that having a folder name which starts with another folder name at the same level causes aws cli to believe that the files in that directory do not exist, and therefore re-uploads them. This conclusion based on running the following (with and without comparator):
aws s3 sync "C:\abc" "s3://my_bucket_name/abc"
c:\abc contains some files and 2 folders "xyz" and "xyz2". The first time it runs successfully and I have verified that everything has been copied to the s3 bucket. On every subsequent run all the files in c:\abc\xyz are re-uploaded erroneously.
I was puzzling as to what was going on (including investigation of #599). There is a thread about this in the aws forum https://forums.aws.amazon.com/thread.jspa?threadID=146851&tstart=0
Using 1.3.21 of aws cli on Windows 7
Appears that having a folder name which starts with another folder name at the same level causes aws cli to believe that the files in that directory do not exist, and therefore re-uploads them. This conclusion based on running the following (with and without comparator):
aws s3 sync "C:\abc" "s3://my_bucket_name/abc"
c:\abc contains some files and 2 folders "xyz" and "xyz2". The first time it runs successfully and I have verified that everything has been copied to the s3 bucket. On every subsequent run all the files in c:\abc\xyz are re-uploaded erroneously.
I was puzzling as to what was going on (including investigation of #599). There is a thread about this in the aws forum https://forums.aws.amazon.com/thread.jspa?threadID=146851&tstart=0