Automatically stringify st2.datastore_crypto_key and st2chatop.env values if needed.

Author: cognifloyd

CHANGELOG.md

@@ -22,6 +22,7 @@
 * Fix a bug when datastore cryto keys are not able to read by the rules engine. ``datastore_crypto_key`` volume is now mounted on the ``st2rulesengine`` pods (#223) (by @moti1992)
 * Minimize required sensor config by using default values from st2sensorcontainer for each sensor in st2.packs.sensors (#221) (by @cognifloyd)
 * Do not template rabbitmq secrets file unless rabbitmq subchart is enabled. (#242) (by @cognifloyd)
+* Automatically stringify st2.datastore_crypto_key and st2chatop.env values if needed. (#241) (by @cognifloyd)
 
 ## v0.60.0
 * Switch st2 version to `v3.5dev` as a new latest development version (#187)

templates/secrets_datastore_crypto_key.yaml

@@ -20,6 +20,10 @@ metadata:
 type: Opaque
 data:
   # Datastore key used to encrypt/decrypt record for the KV store
+  {{- if kindIs "string" .Values.st2.datastore_crypto_key }}
   datastore_crypto_key: {{ .Values.st2.datastore_crypto_key | b64enc }}
+  {{- else }}
+  datastore_crypto_key: {{ .Values.st2.datastore_crypto_key | toJson | b64enc }}
+  {{- end }}
 
 {{- end }}

templates/secrets_st2chatops.yaml

@@ -16,6 +16,6 @@ metadata:
 type: Opaque
 data:
 {{- range $env, $value := .Values.st2chatops.env }}
-  {{ $env }}: {{ $value | b64enc | quote }}
+  {{ $env }}: {{ $value | toString | b64enc | quote }}
 {{- end }}
 {{- end }}