Allow syncing custom repos without password#7426
Conversation
|
The error in the issue is passing '' as the password - can't you just "not set it", or pass None? |
It looks like aiohttp does not buy it.. 😞 |
31cde14 to
3674b8a
Compare
When a custom repository requires upstream_username only (no password), we should be able to proceed with the username only for the base auth. Assisted By: Claude Code Closes pulp#7425
3674b8a to
ae446d6
Compare
|
I set up a test-scenario removing as many variables as possible (e.g., just-pulp and its API ), reproduced the problem, and with this PR showed it was addressed. For future reference:
Note that, along the way, I discovered that you can set a Remote's password to None, but not to empty string: fails, but succeeds. With this fix, they are treated identically - which matches the Finally, with respect to "password but no username may also be valid" - not that I can see from how BasicAuth actually works. |
Backport to 3.63: 💚 backport PR created✅ Backport PR branch: Backported as #7496 🤖 @patchback |
Backport to 3.73: 💚 backport PR created✅ Backport PR branch: Backported as #7500 🤖 @patchback |
Backport to 3.105: 💚 backport PR created✅ Backport PR branch: Backported as #7497 🤖 @patchback |
Backport to 3.85: 💚 backport PR created✅ Backport PR branch: Backported as #7498 🤖 @patchback |
When a custom repository requires upstream_username only (no password), we should be able to proceed with the username only.
Closes #7425
📜 Checklist
See: Pull Request Walkthrough