If I mix tools like s3cmd and s3-sync, I can end up PUTting a file without including the "x-amz-meta-syncfilehash" header. Then subsequent calls to s3-sync won't recognize the file as changed and just glides silently past it.
I'm sorry for being a bad citizen and not providing a simple test case. I'm actually using this through grunt-s3-sync, so it's a little awkward. I do have a proposed fix, though, that works for me. It's over at my fork so I guess I'll make a pull request.
If I mix tools like s3cmd and s3-sync, I can end up PUTting a file without including the "x-amz-meta-syncfilehash" header. Then subsequent calls to s3-sync won't recognize the file as changed and just glides silently past it.
I'm sorry for being a bad citizen and not providing a simple test case. I'm actually using this through grunt-s3-sync, so it's a little awkward. I do have a proposed fix, though, that works for me. It's over at my fork so I guess I'll make a pull request.