Dvc.org: cmd ref: mention that cache options could be used additionally to remote modify params

[shcheklein]

At least type can be specified and is taken into account for dvc remote modify command SSH remotes. More details here: https://github.com/iterative/dvc/issues/2704

UPDATE: See more details in https://github.com/iterative/dvc.org/issues/764#issuecomment-548979449 below.

[jorgeorpinel]

iterative/dvc#2704 is a little confusing. Would be great if this issue was self-contained with a summery of what and why to improve the remote modify cmd ref.

[shcheklein]

@jorgeorpinel we have a list of options that are applicable for different remotes provided via expandable sections here (btw, section should be renamed Available Options).

In case of remote data management, when you set that remote as an external cache, specifically for SSH you can specify some options that are not mentioned in that list:

dvc remote add sshcache ssh://[email protected]:/cache
dvc config cache.ssh sshcache
dvc remote modify sshcache type symlinks,reflinks,copy

type in this case is similar to the regular cache config type we have. Not sure about reflinks though, @mroutis and @efiop could clarify that?

I can imagine that protected should make sense in this case as well. Not sure about slow_link_warning.

[ghost]

@shcheklein , reflinks are supported :)

[ghost]

@shcheklein , protect make sense but is not enable, I was talking about it on https://github.com/iterative/dvc/issues/2542 could you take a look?

[jorgeorpinel]

Hi. Per this support case we should probably document all the cache link types that are supported per remote location, and explain how caching works for external outputs.

Also added a checkbox about this in epic #520