[Bug] - versitygw admin does not respect --bucketlinks #1081
Labels
bug
Something isn't working
Comments
jbert
added a commit
to jbert/versitygw
that referenced
this issue
Feb 27, 2025
…spect --bucketlinks" versity#1081
|
Hi. I managed to reproduce this locally and have a potential PR which seems to fix: #1094 (and adds tests). regards, jb |
benmcclelland
pushed a commit
that referenced
this issue
Feb 28, 2025
- extract method to find top-level dirs, optionally including links to dirs - rework ListBuckets and ListBucketsAndOwners to use FileInfo rather than DirEntry Fixes #1081
benmcclelland
pushed a commit
that referenced
this issue
Feb 28, 2025
- extract method to find top-level dirs, optionally including links to dirs - rework ListBuckets and ListBucketsAndOwners to use FileInfo rather than DirEntry Fixes #1081
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When running versitygw with
posix --bucketlinks /some/dirversitygw admin list-bucketsdoes not list the buckets that are represented by symlinks. The buckets that are not listed with the above admin command are listed though withaws s3api list-bucketsTo Reproduce
Just start versitygw with posix and create some normal directories and some symlinks under the bucket root directory (the directory provided as argument to posix). Then call commands mentioned in the "Describe the bug" section and see the difference.
Expected behavior
Same buckets are listed via the admin API and the standard S3 API.
Server Version
1.0.10
Additional context
None.
The text was updated successfully, but these errors were encountered: