Using an existing secret to specify the config.json file?

[kastl-ars]

Hi all,

sorry if I have missed this, but I found no hint in the chart's values.yaml that I can use an existing secret (created outside of the chart) to specify the config.json configuration file?

From looking a the chart (currently on the road, hence no way to test it) it might be possible to use renovate.existingConfigFile pointing to a file that was mounted from a secret using extraVolumes and etraVolumeMounts?

Something like this:

renovate:
  existingConfigFile: /some/path/config.json
extraVolumes:
  - name: my-own-config
     secret:
       name: renovate-config-secret
extraVolumeMounts:
  - name: my-own-config
    mountPath: /some/path/config.json
    subPath: config.json

Am I on the right track?

Kind Regards
Johannes

[viceice]

yes, that should work.

[kastl-ars]

Thanks Michael!

[johanneskastl]

Small change, it needs to be:

extraVolumes:
  - name: my-own-config
     secretName: # <<< this must be secretName, not just secret
       name: renovate-config-secret

Should I prepare a small PR to add a commented example to the values.yaml?

[viceice]

sure