How to restrict Renovate so that it only looks at private repositories #34282
Unanswered
VladimirMikov
asked this question in
Request Help
Replies: 2 comments 2 replies
-
What settings have you tried? Copy/paste your "preferred" attempt here. You most likely can use https://docs.renovatebot.com/configuration-options/#defaultregistryurls and configure it to your private registry, but you haven't provided enough details for me to be sure |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hi, please format any copy/pasted code or logs so they're readable. You can find a Markdown code formatting guide here as well as some GitHub-specific information formatting code blocks here. Thanks, the Renovate team |
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
-
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.
Azure using latest docker image version
Please tell us more about your question or problem
Currently we're running Renovate through an Azure DevOps pipeline that runs it as a docker image. Due to security requirements we need to store any and all docker images in our private repository after our security team has performed a scan.
As it stands adding our private repo as one that Renovate scans is not an issue, the problem I encounter is that no matter what setting I've tried using it also checks public repositories as well and subsequently opens PRs when newer versions are available publicly.
I've gone through the documentation a few times but I can't find any way to restrict or disable certain repositories from ever being scanned. Any suggestions would be greatly appreciated!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions