-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gitPrivateKey not used to sign commits #228
Comments
I have addressed this in https://github.com/whitesource/renovate-on-prem/releases/tag/2.6.0 I'm not certain it will be fixed, assuming there's a bug, but at the very least you should find some additional log messages with the |
The error seem to persist. At no point
|
Importing is done once, so a log like that isn't indicative of the failure. Please check your debug logs for all instances of the string gitPrivateKey |
Thanks a lot. It works now, my cluster did not upgrade the container. Lot of |
Setting up
renovate-on-prem
to sign commit by deploying the helm chart with the followingvalues.yaml
file:On gitlab side I enforce the commit signing. All push fails due to the missing signature.
I've made sure that the new line are not interpreted by the yaml using the single quote, when attaching to the pod,
gitPrivateKey
value is a single line still with\n
characters.I don't see what more can be done to solve this issue.
The text was updated successfully, but these errors were encountered: