Uplink ls and uplink ls --recrusive results are different

I’m unable to create an empty prefix via uplink, seems it’s possible only via third party tools.
You can’t add a missed prefix, but you can upload data again with a right prefix.
Perhaps in the tool where you created a backup you specified a prefix started with /.

There is two ways how to solve this problem:

  1. Setup an Tardigrade S3 Gateway
    1.1. Install aws cli
    1.2. Setup aws cli to use the Tardigrade S3 Gateway
    1.3. Operate with aws s3 --endpoint http://localhost:7777 with an empty prefix, i.e.
aws s3 --endpoint http://localhost:7777 ls s3://stoneblmbpro-15//
  1. Remove the bucket and create a new one and upload with a right prefix
uplink rb --force sj://stoneblmbpro-15/
uplink mb sj://stoneblmbpro-15

I created an issue