We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
As reported originally here: renovatebot/renovate#13054
Copypaste from my comment here: renovatebot/renovate#13054 (comment):
I believe this could be related to: config: Renovate will now fail if RENOVATE_CONFIG_FILE is specified without a file extension (https://github.com/renovatebot/renovate/releases/tag/30.0.0) This should have been fixed here: #170 But unfortunately the line introduced in that PR will not be evaluated because the whole env section is guarded by another if: helm-charts/charts/renovate/templates/cronjob.yaml Line 88 in 5e50b02 {{- if or .Values.redis.enabled .Values.renovate.existingConfigFile .Values.env .Values.dind.enabled }} As a workaround, this can be specified in the values.yml env: RENOVATE_CONFIG_FILE: /usr/src/app/config.json
I believe this could be related to:
config: Renovate will now fail if RENOVATE_CONFIG_FILE is specified without a file extension
(https://github.com/renovatebot/renovate/releases/tag/30.0.0)
This should have been fixed here: #170
But unfortunately the line introduced in that PR will not be evaluated because the whole env section is guarded by another if:
env
helm-charts/charts/renovate/templates/cronjob.yaml
Line 88 in 5e50b02
As a workaround, this can be specified in the values.yml
values.yml
env: RENOVATE_CONFIG_FILE: /usr/src/app/config.json
The text was updated successfully, but these errors were encountered:
Actually, if I'm reading this correctly, specifying anything on env will cause #170 to behave as intended, so doing:
env: foo: bar
Should also be a valid workaround.
Sorry, something went wrong.
fix RENOVATE_CONFIG_FILE not being rendered
RENOVATE_CONFIG_FILE
48c8bfa
Fixes renovatebot#173 Fixes renovatebot/renovate#13054
Successfully merging a pull request may close this issue.
As reported originally here: renovatebot/renovate#13054
Copypaste from my comment here: renovatebot/renovate#13054 (comment):
The text was updated successfully, but these errors were encountered: