So far so good, the workaround you've mentionned is working great ! We are able to have both swift api and s3api working on our proxy.
The only issue remaining that I can see at the moment is the following:
when I do an "ls" command with s3api in the project, i'm seeing all containers/buckets created in 2009. But when I do an "ls" inside a bucket/container, i'm seeing correct dates.
Hello Tim,
So far so good, the workaround you've mentionned is working great ! We are able to have both swift api and s3api working on our proxy.
The only issue remaining that I can see at the moment is the following:
when I do an "ls" command with s3api in the project, i'm seeing all containers/buckets created in 2009. But when I do an "ls" inside a bucket/container, i'm seeing correct dates.
Here is an example: 23456 test_s3 2/README. md
15-01-2021 14:18:46 :] : s3cmd ls
2009-02-03 16:45 s3://autretest
2009-02-03 16:45 s3://bucketopendev
2009-02-03 16:45 s3://container
2009-02-03 16:45 s3://container12
2009-02-03 16:45 s3://container1
2009-02-03 16:45 s3://container13
2009-02-03 16:45 s3://container_dev
2009-02-03 16:45 s3://container_s3
2009-02-03 16:45 s3://container_
2009-02-03 16:45 s3://containerlol
2009-02-03 16:45 s3://sergetest
2009-02-03 16:45 s3://test-bucket
2009-02-03 16:45 s3://test123
2009-02-03 16:45 s3://testbucket
2009-02-03 16:45 s3://testbucket2
15-01-2021 14:18:49 :] s3cmd ls s3://testbucket2
2020-12-23 10:42 4802 s3://testbucket
Any idea on why we are seeing this behaviour ?
Thanks a lot !