New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: S3 "folder" key has no ending slash #10714
Comments
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. |
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 I believe that if you create a key named Thanks! |
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. |
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! |
Is there an existing issue for this?
Current Behavior
The results of listing S3 bucket objects don't contain a forward slash for "folder" objects. For instance, if a bucket contains "folders" abc, and def, then the result is
Expected Behavior
The ending slash for
def
.How are you starting LocalStack?
Custom (please describe below)
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Start localstack with docker or localstack cli.
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: