pull: not providing response on success

[bhavaniravi]

I was following the get started tutorial with local storage, followed the steps until dev pull - https://dvc.org/doc/get-started/retrieve-data.

When I do a dev pull and the data is fetched I don't get any response saying Sucess I have do a ls to verify whether the data folder has been created

[jorgeorpinel]

Thanks @bhavaniravi. I'm going to move your report over to the DVC core repo for handling.

We'll keep in mind the outcome of this ticket in the dvc.org documentation as well.

[shcheklein]

Thanks, @bhavaniravi ! The same with dvc checkout actually in certain cases. We've removed too much from the output at some point and need to get some stuff back a little bit cc @casperdcl

[efiop]

I'll close this one in favor of #1035

[shcheklein]

I think #1035 was about dvc run commands, when you execute repro. For example, you can imagine you can just capture command outputs when you run repro and show only OK marks when something is done.

This one is about pull and checkout being completely silent. Even though they are doing something. Or they they say something like "Everything is up to date" at the end (while actually they changed the state). So, I would say the solution here should be writing a summary of changes for example (like git checkout), or at least saying a sentence like "Data has been updated".

[efiop]

@shcheklein No, it was about other commands as well, I remember the discussion we've had. I see no point in keeping this issue opened when we have #1035

[shcheklein]

@efiop kk. I recall it in a different way :) And probably it means that ticket is not specific enough, lacks some details (@bhavaniravi should have been able to find that ticket at least and upvote it, for example). I would keep this one if you want to keep only one.

Also, I think the approach from #1035 won't be solving the issue. It will be just printing "ok" every time which is not enough again to say what has just happened.

Also, printing "ok" for every DVC command is kinda cumbersome. I understand the value when we print it for repro stages (and hide output), I don't understand the value to show this every time.