Let Deployment use secretRef even when embedded PostgreSQL is enabled

[Donnie]

retool-helm/charts/retool/templates/deployment_backend.yaml

Line 184 in c7d8d30

{{- if .Values.postgresql.enabled }}

It would be great if we could use the config.postgresql.passwordSecretName secretref even when we use the embedded postgres.

The way it is now, any small change to the helm file triggers regeneration of the random password, and everything breaks.

Or one has to hardcode the secret into the helm values file.

[jjlgao]

Hi Donnie,

Apologies for the late response here. I'm not sure I fully understand, are you looking for the config.postgresql.passwordSecretName param to override the name part of the config if it's provided? Is this because the template command forces regeneration whenever it has to be rerun, even if the actual name of the secret doesn't ultimately change? Apologies, I haven't seen this happen, so I'm not familiar with the behavior you're mentioning.

          {{- if  .Values.postgresql.enabled }}
                name: {{ template "retool.postgresql.fullname" . }}

Can take care of the change once I make sure I understand what the ask is.

Thanks,
Jason