space in path and or filename causes fall back to aws cp

[jalbstmeijer]

using version 2.10.7

created two buckets;
s3p-source
s3p-target

created two folders in s3p-source
testfolder1
testfolder 2

you now see "aws cp" being used to copy the folder with a space in the name.

s3p sync --dryrun --verbose --overwrite --bucket s3p-source --to-bucket s3p-target
parsed-command-line: command: sync, options: dryrun: true, verbose: true, overwrite: true, bucket: s3p-source, toBucket: s3p-target
s3p: d: 1s, items: 0, items/s: 0, listRequests: 2, listWorkers: 4, copied 0/0 0_B/0_B 0_B/s inFlight: 0_B copyWorkers: 0 + 0 PRETENDING same: 0(0_B) toDelete: 0(0_B)
aws s3 cp 's3://s3p-source/testfolder 2/' 's3://s3p-target/testfolder 2/'
copyObject: CopySource: s3p-source/testfolder1/, Bucket: s3p-target, Key: testfolder1/
s3p: d: 1s 238ms, items: 2, items/s: 1, listRequests: 2, copied 2/2 0_B/0_B 0_B/s inFlight: 0_B copyWorkers: 1 + 0 PRETENDING same: 0(0_B) toDelete: 0(0_B), DONE
final-stats:
dryrun: true
copiedBytes: 0
copiedBytesPerSecond: 0
copiedFiles: 2
toDeleteFiles: 0
toDeleteBytes: 0
toReplaceFiles: 0
toReplaceBytes: 0
toReplaceWithBytes: 0
replacedFiles: 0
replacedBytes: 0
unchangedFiles: 0
unchangedBytes: 0
duration: 1.24
items: 2
itemsPerSecond: 1.62
requests: 2
human: copiedBytes: 0_B, copiedBytesPerSecond: 0_B, toDeleteBytes: 0_B, toReplaceBytes: 0_B, toReplaceWithBytes: 0_B, replacedBytes: 0_B, unchangedBytes: 0_B

[shanebdavis]

This is intentional. There was a bug in the AWS SDK v2.x that caused file-names with spaces to not work. I'll need to investigate if this bug persists.

[zewar96]

if you use double quotes instead of single (apostrophe), it works with spaces. I verified this with a simple aws s3 cp call in command-prompt. Is there an easy way to change this? Right now i am getting an error when trying to do a dry-run sync command