Skip to content
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

fix: don't use DEFAULT_REGION for listBuckets method #1248

Merged
merged 8 commits into from
Mar 19, 2024

Conversation

aldy505
Copy link
Contributor

@aldy505 aldy505 commented Nov 26, 2023

Closes #1148

Previously I remembered that I change this line of code to fix that issue. It turns out, I haven't.

Please try to test it with both S3 and MinIO backends.

@aldy505
Copy link
Contributor Author

aldy505 commented Dec 14, 2023

@prakashsvmx @kaankabalak Can we get this reviewed, please?

@kaankabalak kaankabalak self-requested a review December 14, 2023 01:50
@prakashsvmx
Copy link
Member

i need to validate this with AWS.

@aldy505
Copy link
Contributor Author

aldy505 commented Feb 7, 2024

@prakashsvmx Have you validate this with AWS S3?

@prakashsvmx prakashsvmx merged commit e1d730c into minio:master Mar 19, 2024
14 checks passed
@aldy505 aldy505 deleted the fix/list-buckets-region branch March 19, 2024 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

listBuckets ignores Client constructor region
3 participants