gc: clarify behavior of cloud/remote options

[dberenbaum]

Extracted from treeverse/dvc.org#2917 (comment):

@dberenbaum
What happens if you use --remote without --cloud?

@jorgeorpinel
Looks like the remote is ignored and it operates locally instead. A bit confusing but this text is correct ATM.

p.s. It should probably fail or give a clearer warning at least...
the warning is always the same even with -c:

WARNING: This will remove all cache except items used in the workspace of the current repo.

No mention of cloud/remotes.

Warnings should be clarified with respect to using --cloud and --remote options. Also, should --remote imply --cloud so that both aren't required?

[karajan1001]

Yes, it is quite confusing, only after tried myself can I ascertain its behavior.

[dberenbaum]

treeverse/dvc.org#2917 clarified that gc --cloud cleans up the remote in addition to the local cache. Is this intended behavior? Seems like it would be more useful to have gc --cloud be independent and not clean up the local cache.

[dberenbaum]

@daavoo Since you recently updated these options, do you recall if these issues still exist?

[daavoo]

@daavoo Since you recently updated these options, do you recall if these issues still exist?

The --remote flag only doesn't give any hints or warning if --cloud or --not-in-remote is missing. Failing should be a simple change to do.

---

Were you also referring to this one?:

Seems like it would be more useful to have gc --cloud be independent and not clean up the local cache.

This sounds more like a feature request / change in default behavior which would be a breaking change