Skip to content
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

Incorrect Helm externalPostgresql.db_name parameter in values.yaml #1245

Closed
itay-grudev opened this issue Jan 29, 2023 · 0 comments · Fixed by #2036
Closed

Incorrect Helm externalPostgresql.db_name parameter in values.yaml #1245

itay-grudev opened this issue Jan 29, 2023 · 0 comments · Fixed by #2036

Comments

@itay-grudev
Copy link

itay-grudev commented Jan 29, 2023

The Helm chart values.yaml refers to a parameter: externalPostgresql.db_name

externalPostgresql:
host:
port:
db_name:

Whereas the macro using the parameter is referring to just db (as in no _name).

{{- define "snippet.postgresql.db" -}}
{{- if and (not .Values.postgresql.enabled) .Values.externalPostgresql.db -}}
{{- required "externalPostgresql.db is required if not postgresql.enabled" .Values.externalPostgresql.db | quote}}
{{- else -}}
"oncall"
{{- end -}}
{{- end -}}

I suppose these need to be synced, likely in favour of the less descriptive db as it would not affect existing setups.

Unfortunately the typo was not made in the MariaDB which will cause an inconsistency:

{{- define "snippet.mysql.db" -}}
{{- if and (not .Values.mariadb.enabled) .Values.externalMysql.db_name -}}
{{- required "externalMysql.db is required if not mariadb.enabled" .Values.externalMysql.db_name | quote}}
{{- else -}}
"oncall"
{{- end -}}
{{- end -}}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants