-
Notifications
You must be signed in to change notification settings - Fork 61
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
On helm-chart 7.0.0 with value mendRnvLogHistoryDir unset logs are going to /tmp/renovate/logs #489
Comments
Yes, |
If you didn't want logging locally (as we stream all the STDOUT to a logging platform), what should it be set to? I know we tried |
You can set EDIT: The above will override the value that is being sent to the Renovate CLI, effectively disabling it (refer to the |
That is what we tried, here are the slightly redacted errors from that:
|
You tried setting This will prevent Renovate from writing local logs to the PVC (and the error you mention), but it won't prevent the creation of the |
Btw, setting |
Hi @pippitt we'll address this issue and allow not storing logs at all |
we update the configurations docs to indicate where the files will be saved by default and how to clean them up |
I recommend a feature request to provide a hard-coded value for The new value could be something like: OFF, NONE, DISABLED I recommend: NONE |
After updating from chart version 6.10.0 to 7.0.0 we noticed the renovate attached PVC was filling with logs.
Previous image with no logs:
ghcr.io/mend/renovate-ce:6.11.0
Current image with logs:
ghcr.io/mend/renovate-ce:7.0.0
The previous deployment logged nothing to /tmp/renovate/logs as expected with
mendRnvLogHistoryDir
unset.As a work around we set these values:
There is the output of
env|grep LOG
on the 7.0.0 version container:and the same on the 6.11.0 container:
From the logs on the new version I do see config.log being set, example with redactions:
vs logs from the 6.11.0 for a
"msg": "Running Renovate job"
:Let me know if I can provide further information.
The text was updated successfully, but these errors were encountered: