Bug in new Connector Validation

[tebriel]

#365 introduced a bug that prevents us from creating a new connector as our splunk.hec.uri is a list of URIs instead of a single URI.

This line takes the connectorConfig.splunkURI and concatenates it with the endpoint, however the README.md notes that the splunk.hec.uri can be a comma separated list of URIs.

Our existing connectors are continuing to function after the restart, however we cannot create new connectors.

We have found no workaround yet and are downgrading to v2.0.9. Update Downgrading to v2.0.9 allowed us to create a connector with a list of URIs, further validating that this is likely the culrpit.

/cc @harshit-splunk @deep-splunk

[tebriel]

Example connector config:

{
  "name": "example-connector",
  "config": {
    "connections.max.idle.ms": "180000",
    "connector.class": "com.splunk.kafka.connect.SplunkSinkConnector",
    "enable.timestamp.extraction": "true",
    "errors.tolerance": "all",
    "errors.log.enable": "true",
    "metadata.max.age.ms": "180000",
    "request.timeout.ms": "60000",
    "session.timeout.ms": "30000",
    "splunk.header.support": "false",
    "splunk.hec.ack.enabled": "false",
    "splunk.hec.backoff.threshhold.seconds": "1",
    "splunk.hec.max.batch.size": "2000",
    "splunk.hec.max.http.connection.per.channel": "200",
    "splunk.hec.raw": "false",
    "splunk.hec.raw.line.breaker": "######",
    "splunk.hec.ssl.validate.certs": "false",
    "splunk.hec.token": "SOME_TOKEN",
    "splunk.hec.total.channels": "8",
    "splunk.hec.uri": "https://a.url.com,https://b.url.com,https://c.url.com",
    "splunk.indexes": "prod-ingest",
    "splunk.sourcetypes": "asourcetype",
    "tasks.max": 60,
    "timestamp.format": "epoch",
    "timestamp.regex": "\"@timestamp\":\\s*(?<time>.*?),",
    "topics": "thetopic"
  }
}