HTTP 401 while fetching releases from GitHub using a custom datasource #40859
Unanswered
multani
asked this question in
Request Help
Replies: 0 comments
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?
A Mend.io-hosted app
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
42.92.1
Please tell us more about your question or problem
I wrote a custom datasource to parse releases numbers from a GitHub repository with a very particular format (cf. a past discussion on how to parse EKS versions from the
aws/eks-distrorepository)The solution I implemented last Summer (documented here) worked more or less correctly, with the caveat mentioned at the bottom of my message where Renovate sometimes receives HTTP 403 responses from the GitHub API (which I assume where due to rate limiting from unauthenticated access, documented here)
A few months ago, this custom datasource stopped working completely: now, everytime Renovate tries to fetch the releases from GitHub, the calls fails with a HTTP 401.
For instance, using the test repository in https://github.com/multani/test-renovate-eks/, Renovate logs the following:
I noticed there's now a new
hostRules: applying Bearer authentication for api.github.comthat I think was not there when I wrote the custom datasource last August.In the logs, I can see that several
hostRulesare configured forapi.github.com:In that list, only
app.terraform.ioandeurope-west3-docker.pkg.devhave been explicitly configured for my GitHub organization, so I assume theapi.github.comtokens are set automatically by the Mend.io-hosted application.hostRulesfor my custom datasource triggers?api.github.com?Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions