dulwich - clone from remote repo authentication

Question

I couldn't find any resource on this topic. I need to clone from a private repository by providing the username and the password. However when they are provided as keyword arguments to 'dulwich.get-client-from-path()' an error occurs saying 'unknown argument "username"'.

This seems to be a simple thing to do, however I can't find the proper method.

@user12321 does it use the git binary or does it manipulate the index to carry out the tasks? The main reason I chose Dulwich was its use of the index. — chamilad, Jan 25 '15 at 17:34
Nothing so far. I've opened an issue on Dulwich's github repo. — chamilad, Jul 31 '15 at 18:51

score 2 · Accepted Answer · edited Nov 05 '19 at 15:14

2

Try this snippet:

porcelain.clone("https://user:password@your_git_repo.git")

edited Nov 05 '19 at 15:14

Robert Columbia

6,313
15
32
40

answered Nov 05 '19 at 15:01

harvin

76
5

At the time this wasn't possible, but this has been fixed now in Dulwich. Accepting answer. – chamilad Dec 16 '21 at 04:00

score 1 · Answer 2 · answered Sep 01 '22 at 13:05

This works as well:

porcelain.clone("https://example.com/repo.git", username="user", password="password")

I quickly checked to see if the credentials are stored locally:

When using the username and password syntax from this answer, neither username nor password seem to be stored anywhere.
When using the method from harvin's answer, the username is stored locally (you can check this on the command line with git remote -v). The password does not seem to be stored.
- This is different from the behavior of executing git clone https://user:password@example.com/repo.git on the command line, which stores both username and password.

How I found out

The Dulwich porcelain documentation does not mention the possibility to clone with authentication at all.
The source code for porcelain.clone does take **kwargs.
- They are passed to client.get_transport_and_path.
- This passes them to client.get_transport_and_path_from_url.
- This passes them to HttpGitClient.from_parsedurl. If username and password are present in the URL, they are extracted and stored into the kwargs dictionary (this probably is what makes harvin's answer work).
- The kwargs dictionary is then passed on again somewhere. I did not check that location out, because the fact that the code knows about a username and a password key in kwargs was enough evidence for me to just try the snippet I posted above, and it worked.

dulwich - clone from remote repo authentication

2 Answers2

How I found out

Linked