We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Originally posted by seanses March 30, 2024 In an experiment effort to build an S3-compatible service I found it unnecessary to restrict bucket names according to https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html. Does it make sense to add a quick path to disable check_bucket_name?
check_bucket_name
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Discussed in #142
Originally posted by seanses March 30, 2024
In an experiment effort to build an S3-compatible service I found it unnecessary to restrict bucket names according to https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html. Does it make sense to add a quick path to disable
check_bucket_name
?The text was updated successfully, but these errors were encountered: