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
dvc auth check #8235
Comments
Related: #6927. Maybe it could be an option to pass arbitrary information to |
I did a quick look into it:
Even if we have a credentials check, the operations may fail due to permissions to list/read/write. So is it better to have a credentials check or a |
My understanding here is that fsspec does not have a good way to check for authentication issues. |
If the check is cheap to perform, I think would be also nice to include the check as part of Similar to how the |
@skshetry We are not limited by fsspec there, we can add any auth checks that we please on top and then consider propagading into upstream. But overall auth errors are handled differently depending on filesystem, in some it is better than in others. The OSError you've mentioned is just a bug, we've discussed this before. What's important to remember here is that auth check is not going to be a silver bullet, as with many operations we won't know if we have access untill we try to do them. For example, s3 ls might work with some prefixes but not with others and so on, there are a lot of variables there. The best we can reasonably do is probably try listing a specified path, but even that is pretty limited. |
I'll consider this as a
feature request
I agree, I don't think the command helps, we should try to improve on error messages and exceptions. I'll suggest closing this in favour of #6353. |
The way I interpreted the request is that the command is not intended to be a silver bullet but rather a quick way of detecting errors regarding credentials and/or remote setup. Would be nice to clarify the use case for the command |
An error could happen due to lot of things. Ideally, dvc should be able to inform users that the auth failed, in the commands where relevant, there should not be a need for a separate command. |
Something like
(just from the top of my head, it should be something simple and informative). It doesn't have to be perfect, even calling MIght get to this in the near future for studio. |
From @dmpetrov
The text was updated successfully, but these errors were encountered: