lockFileMaintenance with private inputs on a flake #34504
Unanswered
Rider128
asked this question in
Request Help
Replies: 1 comment
-
|
I solved this, giving Renovate access to the Git server by setting: RENOVATE_HOST_RULES: |
[
{
"matchHost": "gitea.${BASE_DOMAIN:?}",
"token": "${RENOVATE_TOKEN}"
}
]and giving the git-config: # file .gitconfig
content: |
[credential]
helper = "store"
git-credentials: # file .git-credentials
content: "https://renovate:${RENOVATE_TOKEN:?}@gitea.${BASE_DOMAIN:?}" |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
Gitlab
Please tell us more about your question or problem
Hello,
I have a flake with multiple private inputs, but my Renovate bot cannot perform flake.lock maintenance because it fails to fetch the private input via Git. The issue seems to be that the SSH key is not properly referenced.
The Renovate bot runs on a NixOS VM.
How can I configure Renovate to use an SSH key or make it use the SSH key available in the VM?
For GitLab CI, I worked around a similar issue by using a token with the following configuration:
git config --global url."https://gitlab-ci-token:${CI_JOB_TOKEN}@gitlab.address".insteadOf "ssh://git@gitlab-address"Is there a way to apply a similar workaround for Renovate, or another method to resolve this issue?
Thanks in advance!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions