bug: S3 "folder" key has no ending slash about localstack HOT 4 OPEN

Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.

from localstack.

Hello @spring1915 and thanks for your report!

It's not clear what the issue is here. "Folder" objects are technically defined by yourself or the SDK, you would have to create them yourself.

Could you please share the commands done to create those particular folder keys? We should have pretty good parity with keys finishing with / or not.

I believe that if you create a key named /abc/def/, then the call to ListObjectsV2 should return /abc/def/.
The report does not share how those keys are created.

Thanks!

from localstack.

Thanks @bentsku . I used the "Create Folder" button of Localstack Desktop to create a new folder.

It seems that I found a way to get it over. When hitting "Create Folder", a name ending with a slash must be included as the folder name. Making a folder without this character results in the missing of a slash when listing bucket objects, even although the folder is indicated as being successfully created.

from localstack.

Hello @spring1915 and thanks for the quick feedback!

So to be sure, when in AWS S3 you'd create a "folder" key, it would come with a trailing slash. But with the same action with the LocalStack Desktop app, it does not. This looks like an issue in our application then and not S3. I will share this issue with the related team, and update you here. Thank you!

from localstack.