-
Notifications
You must be signed in to change notification settings - Fork 325
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
how do you pass in credentials for MinioAdmin after the major refactor? #1331
Comments
Here is an example: from minio.credentials import StaticProvider
madmin = MinioAdmin(
"127.0.0.1:9000",
credentials=StaticProvider(
access_key='minioadmin',
secret_key='minioadmin'
),
secure=False
) |
awesome, thank you! I'll give that a try and then also try to add some examples in a PR shortly :) |
Refer #1334 |
I landed here, too. It would be really nice if you had some documentation around MinioAdmin class in general... |
Sorry, the project I'm on right now started demoing an alternative self hosted object store, and then I didn't have time to try out the new suggested workflow. If others have more time and have tested the example in #1331 (comment) please feel free to submit example PRs ahead of me. |
After #1291, how do you pass in credentials for the MinioAdmin class now?
credentials
type is not defined here, but is required as there is no default:minio-py/minio/minioadmin.py
Line 90 in 8e681bb
But when I look at the code here, it shows it should be of type
Provider
:minio-py/minio/minioadmin.py
Lines 96 to 97 in 8e681bb
However, when I look at
Provider
, it doesn't explain what type credentials are either:minio-py/minio/credentials/providers.py
Lines 78 to 84 in 8e681bb
In the future, before merging and releasing a major refactoring change like this, please require doc and example updates. A deprecation warning would have also been helpful.
For the type hints, I added #1334 to try and help out. If I can get confirmation on how to pass in credentials, I'm happy to create further PRs to update some examples to help out.
The text was updated successfully, but these errors were encountered: