PDM authenticate to private nexus repository #28943
Unanswered
jackson-chris
asked this question in
Request Help
Replies: 2 comments 6 replies
-
Where are you configuring those "secrets"? E.g. in a config.js file? You can't quote "process.env.FOO". That's just a string. You need to remove the "" |
Beta Was this translation helpful? Give feedback.
3 replies
-
Unfortunately that didn't work either. It still complaining the credentials are missing. I tried setting env variables like so in my
I tried both |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Github using full image 37.351.2-full
Please tell us more about your question or problem
I am using pdm to manage dependencies. Those dependencies are being pulled from a private nexus repo. Renovatebot is failing to update the
pdm.lock
file as it cannot authenticate with the repository. Error shown below. I have the following relevant configuration:I am also setting these env variables at the renovatebot process level, the first two are for automatic host rule creation, the latter two are to be referenced as secrets and injected into subprocess for lock updates:
NOTE these have equivalent values
PDM_PYPI_USERNAME=PYPI_NEXUS_MYCOMPANY_COM_USERNAME
andPDM_PYPI_PASSWORD=PYPI_NEXUS_MYCOMPANY_COM_PASSWORD
.My
pyproject.toml
has the following section:Usually when building locally we include a
pdm.toml
file with the following content:we obviously don't check this file into source control nor would we want to.
What am I doing wrong? What's the correct way to inject PDM credentials for renovate to consume?
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions