Does anyone have a successful setup using

uv

with a private python repository? I'm having some issues with getting auth to work right. It's working locally, but not in CI, and I can't seem to figure out why. Curious if anyone else has had any hiccups they managed to work through

How do you configure auth?

~/.netrc

, credentials embedded in a configured custom index URL or env vars with pass-throughs for those env vars configured in Pants? Or - do you locally use

uv auth

locally? This one does not appear to be handled by Pants.

Currently trying to use credentials embedded in the URL. I had it configured this way for a while now (prior to trying to switch to uv). My naiive attempt was "maybe it will just work the same way", but then it worked locally and not in CI

So - be really verbose! Is the auth in the URL embedded directly or via env var?

auth is embedded via env var like

https://${USER}:${PASSWORD}@example.org

I don't generate the lock file at all in CI. Its on use (and on any use) that it fails. It is always due to a 401 return from artifactory when trying to access the internal package. I turned on verbose logging and that was enough to see that it got the 401 from

<https://example.org>

I notice the URL no longer contains the auth. I don't know if that is due to it being lost in translation, or if uv just stripped it from the log.

And how do you get pants to plumb USER and PASSWORD - are there additional setting you use to punch holes for these env vars?

Looks like I just need the next 2.34 release then. Thanks for the info

Related issue: https://github.com/pantsbuild/pants/issues/23459 And I will fix the find-links issue I think by folding them into indexes with

format = "flat"