How do I use GIT_SSL_NO_VERIFY after #43113 #43166
-
How are you running Renovate?Self-hosted Renovate CLI Which platform you running Renovate on?Other (please specify) Which version of Renovate are you using?43.169.4 Please tell us more about your question or problemIn my company we are using a selfhosted renovate cli via docker to update our dependencies in our repositories. We are using a selfhosted Bitbucket server that is not exposed to the internet and uses self-signed TLS certificates. This was working just fine when we set GIT_SSL_NO_VERIFY to 1 via the docker compose file, however this stopped working in the last 2 days, I assume due to #43113. Is there a way to keep the same functionality after this PR was merged? Logs (if relevant)Logs |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
After re-reading the PR I found the solution is already in there. If somebody else has the same issue: You now need to pass it via RENOVATE_CUSTOM_ENV_VARIABLES, e.g. See: https://docs.renovatebot.com/self-hosted-configuration/#customenvvariables |
Beta Was this translation helpful? Give feedback.
After re-reading the PR I found the solution is already in there. If somebody else has the same issue: You now need to pass it via RENOVATE_CUSTOM_ENV_VARIABLES, e.g.
RENOVATE_CUSTOM_ENV_VARIABLES: "{GIT_SSL_NO_VERIFY:'1'}"See: https://docs.renovatebot.com/self-hosted-configuration/#customenvvariables