-
Notifications
You must be signed in to change notification settings - Fork 169
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
Should Show Error When Node Starts With Bad S3 Auth Info #597
Comments
I'm looking into this ticket now @ericxtang ... does this kind of logging suffice? This is an older ticket, so logging might have changed. As for how to validate credentials on boot-up, it seems like we'd have to call a service that throws invalid access key id exceptions, such as the file upload function in
|
I think trying to upload & delete a small file on boot-up in this case will create a better user experience. |
Potentially, provide credentials can only have rights to write and no rights to delete. |
Good point. I think in that case, writing a simple test file would be helpful - even if it leave some artifact there. |
Cool, by |
Yes. I think if upload fails, we should exit. And then we can try to delete the file (it's fine if that fails). |
Describe the bug
The node should show an error if it's started with the wrong S3 auth info.
To Reproduce
Expected behavior
If wrong S3 auth is provided, we should either:
The text was updated successfully, but these errors were encountered: