sorry, it's true, that it would not make sense to strip the beginning / from the filename when downloading, as it could be part of the objectname.
But it seems that the output of the upload command does no longer return the objectname but the filename which has been uploaded.
I observed that an automatic script broke when upgrading swiftclient from 2.1.0 to 2.3.1 . The reason lies in the output of the swift command when uploading a file.
# swift --version
swift 2.1.0
# swift upload atest /tmp/tmp.Bk3QMVbivC
tmp/tmp.Bk3QMVbivC
# swift --version
swift 2.3.1
# swift upload atest /tmp/tmp.HPCvgbCAQj
/tmp/tmp.HPCvgbCAQj
The automatic script retrieved the output, and tried to download the file, which did not work with swiftclient 2.3.1, because the client outputs the filename and not the object name on the server.
Hello clayg,
sorry, it's true, that it would not make sense to strip the beginning / from the filename when downloading, as it could be part of the objectname.
But it seems that the output of the upload command does no longer return the objectname but the filename which has been uploaded.
I observed that an automatic script broke when upgrading swiftclient from 2.1.0 to 2.3.1 . The reason lies in the output of the swift command when uploading a file.
# swift --version
swift 2.1.0
# swift upload atest /tmp/tmp.Bk3QMVbivC
tmp/tmp.Bk3QMVbivC
# swift --version
swift 2.3.1
# swift upload atest /tmp/tmp.HPCvgbCAQj
/tmp/tmp.HPCvgbCAQj
The automatic script retrieved the output, and tried to download the file, which did not work with swiftclient 2.3.1, because the client outputs the filename and not the object name on the server.