Using Bearer
authorization for private gitlab terraform package registry
#27156
Unanswered
javajawa
asked this question in
Request Help
Replies: 1 comment 6 replies
-
@rarkins it seems we should switch from that deprecated gitlab header to the official auth header? that's probably breaking for someone who's using very outdated and unsupported Gitlab version |
Beta Was this translation helpful? Give feedback.
6 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
If you're self-hosting Renovate, tell us what version of Renovate you run.
ghcr.io/renovatebot/renovate:37.59.8@sha256:5cc2c1681c1d43ebc2fd3e91792c780b3ecf4ad6b3e80a3562fb958e8979e296
If you're self-hosting Renovate, select which platform you are using.
GitLab self-hosted
What is your question?
GitLab's private terraform package registry requires the use of
Authorization: Bearer [token]
rather thanPrivate-Token: [token]
in order to query the API. When self hosting renovate on the same private gitlab instance, I have not been able to configure this correctly.The private packages documentation seems to suggest there is a known solution to this, but I have been unable to get it working either directly as shown, or with alternate
hostType
to attempt to match the terraform packages.I feel like I'm missing something obvious, but I'm not sure what, and I can only find tangentially related issues.
The underlying issue is very likely the way the token is presented -- using the configured token, I can replicate the following
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions