ElasticSearch configuration for keystore certs and keys not mapped correctly

[exalate-issue-sync]

When using a self-signed certificate in the helm chart with the following configuration:

 set {
    name  = "es.ssl.keystore.type"
    value = var.graviteeio_es_ssl_keystore_type
  }
  set {
    name  = "es.ssl.keystore.certs"
    value = "{${var.graviteeio_es_ssl_keystore_cert_path}}"
  }

The generated configuration is the following:

analytics:
          type: elasticsearch
          elasticsearch:
            endpoints:
              - https://elasticdb-elasticsearch:9200
            index_mode: daily
            security:
              username: elastic
              password: xxxxxx
            ssl:
              keystore:
                type: pem
                certs: [/etc/ssl/certs/es.pem]
                keys: 
            index: graviteeio

And the error on startup is the following:

ERROR i.g.e.client.http.HttpClient - Unable to get a connection to Elasticsearch: Unable to read file at path: /opt/graviteeio-gateway
ERROR i.g.e.client.http.HttpClient - Unable to get a connection to Elasticsearch: Unable to read file at path: /opt/graviteeio-management-api

The issue preventing users from using their self-signed elastic instance is that SSL configuration doesn’t support list of certs/keys

If you use a valid list of certs/keys, Gravitee doesn’t start and only works with a String

This should work but doesn’t:

    ssl:        
      keystore:         type: pem
        certs: 
          - /path/to/crt.pem
        keys: 
          - /path/to/key.pem

This works but should not:

    ssl:        
      keystore:
        type: pem
        certs: /path/to/crt.pem
        keys: /path/to/key.pem