Changing env to extraEnvVars, moving to nsconsumer section because that's the deployment template that uses them.

Author: RWShelton

helm/templates/deployment-consumer.yaml

@@ -46,7 +46,7 @@ spec:
                 secretKeyRef:
                   name: {{ $secretName }}
                   key:  {{ .Values.rmq.rmqConnection.rmqPasswordKey }}
-            {{- range $k, $v := .Values.env }}
+            {{- range $k, $v := .Values.nsconsumer.extraEnvVars }}
             - name: {{ $k }}
               value: {{ $v | quote }}
             {{- end }}

helm/values.yaml

@@ -283,8 +283,7 @@ nodeSelector: {}
 tolerations: []
 affinity: {}
 resources: {}
-# Logging / env map
-env: {}
+
 # We usually recommend not to specify default resources and to leave this as a conscious
 # choice for the user. This also increases chances charts run on environments with limited
 # resources, such as Minikube. If you do want to specify resources, uncomment the following
@@ -401,6 +400,10 @@ nsconsumer:
     periodSeconds: 10
     timeoutSeconds: 5
 
+  # @param extraEnvVars Optional additional env vars to be added to the container.
+  # Format: { EXAMPLE_ENV_VAR: "example_value", ANOTHER_ENV_VAR: "another_value" }
+  extraEnvVars: {}
+
 ## @section RabbitMQ Connection Configuration
 ## (This section does NOT affect the RabbitMQ Operator installation itself.)
 ## These settings are used to configure the connection from the nsconsumer app to an existing