dvc.org: DVC list not working with remote google cloud storage

There are two things here:

  1. I expected to be able to just do dvc list and it would pick up the default remove.
  2. dvc list gs://... is not working (cloning is failing)

I can list the content by using dvc status --remote so I would like to be able to do the same with listing.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 16 (11 by maintainers)

Commits related to this issue

Most upvoted comments

@tupui, dvc list is a virtual ls of your repo, it does not work with other remotes at all. It provides list of your dvc tracked and git tracked files in a virtual list.

Eg:

$ dvc list <path/to/your/repo>

To my mind this ticket was about dvc list. There is not intention to change its behavior. And to be honest I doubt we can list remote in any meaningful way. So it feels that this primarily about making docs extra clear about this (if needed).

For the tooltip, I think this should be uniformize at least. So DVC repo or DVC Project in both cases. Also, for me this is not a DVC repo as it is a repo with my code and with data. When you write DVC repo or project, I expect to only have DVC related things under this definition. Hence doing a dvc list would list DVC things.

you have an API for git related things which you call DVC repo and some other API for the data registry

On this I’m not sure we can compare the internal Python Repo API (not documented but available for use) with the dvc list/import/get commands. Not sure I got that right though.

Here I am not talking about the Python API sorry. I was referring to the CLI.

IMO, there would be two ways to address this. Either keep the ability to either get info about GIT things and only DVC things. Or remove this distinction for the user.

@tupui That paragraph is a part of use-case, which doesn’t have to be throughout. What about https://dvc.org/doc/command-reference/list ? If you have any suggestions, please let us know.