status: support outputs as targets [qa]

[jorgeorpinel]

Bug Report

UPDATE: Jump to #4191 (comment)

---

Looks like dvc status is recursive by default now (maybe always was) from some testing I just did:

λ dvc status
foo.dvc:
        changed outs:
                modified:           foo
data\raw.dvc:
        changed outs:
                modified:           data\raw

λ dvc status -R data/
data\raw.dvc:
        changed outs:
                modified:           data\raw

1. So it's really just useful to limit the status to specific directories (not really about recursion).
2. Why not just support dirs AND FILES as targets of the command, like all other commands that take targets (I think)?

Relater to treeverse/dvc.org#1384 (comment)

3. In fact this is already supported by status, but only in remote mode (-r or -c options), which is kind of confusing (and complicates the docs).

Please provide information about your setup

DVC version: 1.1.2
Python version: 3.7.5
Platform: Windows-10-10.0.18362-SP0
Binary: True
Package: exe
Supported remotes: azure, gdrive, gs, hdfs, http, https, s3, ssh, oss
Cache: reflink - not supported, hardlink - supported, symlink - not supported
Filesystem type (cache directory): ('NTFS', 'C:\\')
Repo: dvc, git
Filesystem type (workspace): ('NTFS', 'C:\\')

[efiop]

@jorgeorpinel Non -c status just doesn't support granularity right now.

[efiop]

Closing in favor of #2180

[efiop]

To clarify:

Why not just support dirs AND FILES as targets of the command, like all other commands that take targets (I think)?

It does support files as targets, but not files(or subdirs) in tracked directories (this is what -c/push/pull/etc support).

[jorgeorpinel]

It does support files as targets

@efiop so is this a bug? 👇

λ ls foo*
foo  foo.dvc
λ dvc status foo
ERROR: failed to obtain data status - 'dvc.yaml' does not exist.

[efiop]

@jorgeorpinel Yes, looks like a bug. Reopening. Thanks!