-
Notifications
You must be signed in to change notification settings - Fork 44
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
Files Uploading to Default Bucket Despite Specified Bucket-ID #216
Comments
Hello, Thanks |
I simply created a bucket called ‘trailers’ in Hasura (the buckets table) and created the same one in MinIO. Then I ran example_curl.sh, where I changed the BUCKET (bucket-id). The files were sent, but only to the default bucket. |
Thanks for the explanation. I think this a misunderstanding, hasura-storage's buckets don't map into minio buckets. No matter of which bucket you upload to in the request the file will be uploaded to the bucket you configured on the service when starting it. hasura-storage's buckets are a specific construct of the service to group configuration and permissions so the only thing that setting Closing as I don't think there is anything to do here but if you have any questions don't hesitate to comment. Thanks again. |
Alright, I understand, thank you. If it’s not possible to change the bucket, is there a way for me to upload a file to a specific folder (which might not yet be created), or will all files be uploaded to the root folder in minio? |
That depends on the underlying storage. For instance, s3 doesn't have folders per se but their UI will "pretend" there are folders if you set as filename |
Ok, thank you, I’ll give it a try. |
Hi, I’m using nhost/hasura-storage:0.6.1. I added a new bucket to the buckets table, and when uploading, I specify the new bucket-id. The entries in the files table successfully receive the new value, but all the files I see in MinIO are uploaded to the default bucket. Is this the expected behavior, or did I miss specifying some necessary parameters?
The text was updated successfully, but these errors were encountered: