I notice that the FileManager creates a placeholder object in S3 to represent each folder, and the key ends in slash, ex: Files/MyFolder/. (This is fine, though it would be nice if this fact were documented a little better, since S3 typically doesn't require folder objects to exist.) However, AmazonS3FileProvider behaves buggy when these folder placeholders don't exist; it has problems parsing folder structure as you browse up/down in the tree.
I am working on an app that uses s3 sync to copy s3 files to local filesystem, and then s3 sync again to put them back into s3. In the sync process the folder placeholder objects get dropped, because they can't be represented well in the local filesystem. So when I re-sync files back to S3, the path hierarchy gets re-constituted, but the placeholder objects don't exist. FileManager doesn't play well with the re-synced files in S3.
Would it be possible to name the placeholder objects differently, for example, "Files/MyFolder/.s3keep" so that they're more explicitly managed when copying files into/out of S3? I would appreciate a little guidance. Thank you!
