s3cmd implicitly adds a '*' to the end of path names

[richardalow]

s3cmd has surprising behaviour when listing or deleting:

s3cmd ls s3://bucket/dir/b
2013-10-03 16:35         0   s3://bucket/dir/b
2013-10-03 16:35         0   s3://bucket/dir/bb

which is inconsistent with ls, that would only list b. Deleting has slightly different but still unexpected behaviour. A single delete is OK:

s3cmd del s3://bucket/dir/b
File s3://bucket/dir/b deleted

but if I create directories 'b' and 'bb' then

s3cmd del -r s3://bucket/dir/b
File s3://bucket/dir/b/file deleted
File s3://bucket/dir/bb/file deleted

I've lost the files in 'bb' too! This is very surprising.

[mdomsch]

which version please?

On Thu, Oct 3, 2013 at 11:40 AM, richardalow [email protected]:

s3cmd has surprising behaviour when listing or deleting:

s3cmd ls s3://bucket/dir/b
2013-10-03 16:35 0 s3://bucket/dir/b
2013-10-03 16:35 0 s3://bucket/dir/bb

which is inconsistent with ls, that would only list b. Deleting has
slightly different but still unexpected behaviour. A single delete is OK:

s3cmd del s3://bucket/dir/b
File s3://bucket/dir/b deleted

but if I create directories 'b' and 'bb' then

s3cmd del -r s3://bucket/dir/b
File s3://bucket/dir/b/file deleted
File s3://bucket/dir/bb/file deleted

I've lost the files in 'bb' too! This is very surprising.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/231
.

[richardalow]

I reproduced on 1.0.0, 1.0.1 and master.

[fviard]

The ls is still showing all the files with the same prefix, but the bad behavior with the delete should already be fixed.