Unable to deploy helm chart due to connection_uri being set to true

[estein9825]

Expected vs actual behavior

The values.yaml has connection_uri set to a boolean value which breaks the helm chart update as a result. Apparently it is because it uses a secret value from the secrets yaml file, but secrets.yaml file still expects to pull in a value that can be converted to base64. A boolean cannot.

The problematic area is here:

  kratos:
    development: false
    config:
      version: v0.10.1
      courier:
        smtp:
          # As per Kratos configuration it should string, but Kratos
          # helm chart is using it only as a flag to set
          # COURIER_SMTP_CONNECTION_URI variable. Actual value is
          # taken from kratos Secret.
          connection_uri: true

Which results in this error message in flux:

group":"helm.toolkit.fluxcd.io","reconciler kind":"HelmRelease","name":"paralus","namespace":"paralus","error":"Helm upgrade failed: template: ztka/charts/kratos/templates/statefulset-mail.yaml:44:12: executing \"ztka/charts/kratos/templates/statefulset-mail.yaml\" at <include \"kratos.annotations.checksum\" .>: error calling include: template: ztka/charts/kratos/templates/_helpers.tpl:184:28: executing \"kratos.annotations.checksum\" at <include (print $.Template.BasePath \"/secrets.yaml\") .>: error calling include: template: ztka/charts/kratos/templates/secrets.yaml:21:76: executing \"ztka/charts/kratos/templates/secrets.yaml\" at <b64enc>: wrong type for value; expected string; got bool"}

It needs to be a string or else the b64 call will fail.

Steps to reproduce the bug

1. Attempt to run the 0.2.1 helm chart

Are you using the latest version of the project?

I was unable to install the latest due to this error

You can check your version by running helm ls|grep '^<deployment-name>' or using pctl, pctl version, and provide the output.

• 0.2.0 chart

What is your environment setup? Please tell us your cloud provider, operating system, and include the output of kubectl version --output=yaml and helm version. Any other information that you have, eg. logs and custom values, is highly appreciated!

• k8s on EKS

(optional) If you have ideas on why the bug happens or how it can be solved, please provide it here

Workaround is to actually set the value. Since I was using a secret name as well, I also had to override the smtpConnectionURI secret.

• [X ] I've described the bug, included steps to reproduce it, and included my environment setup with all customizations.
• I'm using the latest version of the project. -- no because of this issue