Bordering on a bug request, but I'll give you the benefit of the doubt and label this as a feature request, because it could simply be that my intuition is out of line with how dvc works.
When used locally (without the --cloud flag) dvc status can operate on a path spec, but this fails confusingly when the --cloud flag is added.
Scenario: "folder" is tracked by dvc but has been deleted from the cache and/or the remote.
dvc status --cloud folder
.. will report "Cache and remote are in sync".
If folder/ is tracked via folder.dvc then the correct status can be obtained via ...
dvc status --cloud folder.dvc
I feel that it would be more intuitive if dvc status --cloud folder worked out of the box.
Discord discussion: https://discordapp.com/channels/485586884165107732/1095524989870022667
Bordering on a bug request, but I'll give you the benefit of the doubt and label this as a feature request, because it could simply be that my intuition is out of line with how dvc works.
When used locally (without the
--cloudflag)dvc statuscan operate on a path spec, but this fails confusingly when the--cloudflag is added.Scenario: "folder" is tracked by dvc but has been deleted from the cache and/or the remote.
.. will report "Cache and remote are in sync".
If
folder/is tracked viafolder.dvcthen the correct status can be obtained via ...I feel that it would be more intuitive if
dvc status --cloud folderworked out of the box.Discord discussion: https://discordapp.com/channels/485586884165107732/1095524989870022667