get/import: don't require default remote for get/import in certain cases

[pared]

As pointed in discussion under #2711
DVC, upon get and import operations requires that default remote is defined in target repo.
We should remove this requirement.

UPDATE:

check this comment that generalizes it to non-cached files when cache is present already.

#2780 (comment)

[efiop]

Will need to be solved as a part of #2515

[shcheklein]

I think this requirement can be removed even for cached files if they exist in cache already? The case can be a shared cache (all repos use the same cache effectively and sometimes don't even use remote at all).

Double check the behavior with directories (when they only partially cached).

[sharidas]

I am looking into this issue.

[sharidas]

Below are the steps I tried:

• Created a local folder mylocalchange and example-get-started.
• Inside mylocalchange:
  • execute git init; dvc init
  • added folder data2 ( didn't executed dvc add dataset1 ) so its not in the cache.
• Now from the example-get-started folder where (git init; dvc init executed )
  • execute dvc import ../mylocalchange dataset1
  • error logged in the console:

failed to import 'data2' from '../mylocalchange'. - The path 'data2' does not exist in the target repository '../mylocalchange' neighther as an output nor a git-handled file.

• Say if I created the folder dataset1 in mylocalchange and then executed dvc add dataset1. This way the cache is generated in the source.
• Inside folder example-get-started execute:
  • dvc import ../mylocalchange dataset1 , the data gets imported without errors.

Anything that I am missing here to reproduce the issue?