Unify what authorization MLEM and DVC require

[aguschin]

Right now, when working with private repos, MLEM require HTTPS auth, while DVC require SSH https://mlem.ai/doc/user-guide/dvc/#working-with-private-repositories

It's awkward, so we'd like to allow to use a single authentication method. IIUC, DVC supports SSH only https://dvc.org/doc/api-reference/open#example-accessing-private-repos (@skshetry, @efiop, can you please confirm?)

If so, then it makes sense to make MLEM support SSH (we can keep supporting HTTPs if that's possible).

related to #497

[skshetry]

DVC supports both HTTPS/SSH authentication. The docs was just showing an example with ssh. You can pass passwords in url itself, or better enable git credentials-helper, from which dvc can extract username/password for the remote url.

Regarding GITHUB_USERNAME and GITHUB_TOKEN, it's mlem's implementation than being a standard, and even does not have anything to do with fsspec.

mlem/mlem/contrib/github.py

Lines 78 to 79 in 1a1d203

	kwargs["username"] = LOCAL_CONFIG.GITHUB_USERNAME
	kwargs["token"] = LOCAL_CONFIG.GITHUB_TOKEN

[aguschin]

Hi @skshetry! Is this incorrect info that should be fixed then?

https://dvc.org/doc/command-reference/exp/push

[aguschin]

@skshetry could you please TAL and answer? :)

[skshetry]

yes, it is incorrect.