OpenCTI: EnvFromSecret variable not taking precedence over normal env in chart

[estemendoza]

Current Behaviour

I am using the OpenCTI chart to install a connector and I am having some issues when setting env vars from secrets.

I am customising the deployment of the chart with the following values.yaml:

connectors:
  - name: connector-import-file-stix
    enabled: true
    image:
      repository: opencti/connector-import-file-stix
    env:
      CONNECTOR_ID: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
      CONNECTOR_TYPE: INTERNAL_IMPORT_FILE
      CONNECTOR_NAME: ImportFileStix
      CONNECTOR_VALIDATE_BEFORE_IMPORT: "true"
      CONNECTOR_SCOPE: application/json,text/xml
      CONNECTOR_AUTO: "true"
      CONNECTOR_CONFIDENCE_LEVEL: 15
      CONNECTOR_LOG_LEVEL: info
    envFromSecrets:
      OPENCTI_TOKEN:
        name: admin-credentials
        key: api-token

But when I generate the configuration using the chart, I get the following results

containers:
        - name: connector-import-file-stix-connector
          securityContext:
            null
          image: "opencti/connector-import-file-stix:6.0.5"
          imagePullPolicy: IfNotPresent
          env:
          # Variables in plain text
          - name: OPENCTI_URL
            value: "http://cti-opencti-server:80"
          - name: OPENCTI_TOKEN
            value: "ChangeMe"
          - name: CONNECTOR_AUTO
            value: "true"
          - name: CONNECTOR_CONFIDENCE_LEVEL
            value: "15"
          - name: CONNECTOR_ID
            value: "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
          - name: CONNECTOR_LOG_LEVEL
            value: "info"
          - name: CONNECTOR_NAME
            value: "ImportFileStix"
          - name: CONNECTOR_SCOPE
            value: "application/json,text/xml"
          - name: CONNECTOR_TYPE
            value: "INTERNAL_IMPORT_FILE"
          - name: CONNECTOR_VALIDATE_BEFORE_IMPORT
            value: "true"

          # Variables from secrets
          - name: OPENCTI_TOKEN
            valueFrom:
              secretKeyRef:
                name: admin-credentials
                key: api-token
          resources:
            null

Notice how OPENCTI_TOKEN is duplicated in the env variables and once it is deployed, it ignores the variable configured from the secret. It is configuring the default value and also the custom value.

Note: This also happens for the server and worker deployments.

Expected Behaviour

Environmental variables shouldn't be duplicated and if they are duplicated, the ones from the secrets should take precedence.