Fix wrong reference to existingKey (#415) All checks were successful continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
### Description of the change Fix a wrong reference to `signing.existingKey`, `signing.existingSecret` was what was meant and what is used in the chart. ### Benefits Less confusion when trying to use the Helm chart. ### Possible drawbacks Evangelists of `existingKey` storming the barricades even though `existingKey` is long dead. ### Applicable issues None, nobody noticed enough to care, apparently. Co-authored-by: Tobias Wolter <towo@towo.eu> Reviewed-on: gitea/helm-chart#415 Reviewed-by: pat-s <pat-s@noreply.gitea.io> Reviewed-by: justusbunsi <justusbunsi@noreply.gitea.io> Co-authored-by: towo <towo@noreply.gitea.io> Co-committed-by: towo <towo@noreply.gitea.io>
This commit was merged in pull request #415.
This commit is contained in:
@@ -1,6 +1,6 @@ | ||||
{{- if .Values.signing.enabled -}} | ||||
{{- if and (empty .Values.signing.privateKey) (empty .Values.signing.existingSecret) -}} | ||||
{{- fail "Either specify `signing.privateKey` or `signing.existingKey`" -}} | ||||
{{- fail "Either specify `signing.privateKey` or `signing.existingSecret`" -}} | ||||
{{- end }} | ||||
{{- if and (not (empty .Values.signing.privateKey)) (empty .Values.signing.existingSecret) -}} | ||||
apiVersion: v1 | ||||
| ||||
Reference in New Issue
Block a user