dvc auth check

@dberenbaum why don’t we introduce a command in dvc for the check availability of buckets/directories? like dvc auth check s3://mybucket / dvc credentials azure://mycontainer

From @dmpetrov

[daavoo]

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 https://github.com/iterative/dvc/issues/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

[efiop]

@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.