Ali Ok - Looks good. Glad to see that it can be done.

A few questions / thoughts

• How do we factor the creation of the ElasticSearch IndexTemplate into our deployments? Seems like it's something that would need to be done as part of the APB that runs for deploying Sync... Thoughts?

• It's probably not a good idea to pollute the top level namespace with all of out parameters - for example, we have a hostname field and there is a pre-existing hostname field, so there is a clash...

Looking at the dynamic mapping you have and at the ElasticSearch docs https://www.elastic.co/guide/en/elasticsearch/reference/current/dynamic-templates.html#path-match-unmatch, I think it should be possible to namespace our params using the copy_to param- e.g.

"message_properties": {

  "path_match":   "message.*",

  "mapping": {

    "type": "string",

    "index": "not_analyzed",

    "copy_to" : "message.{name}"

  }

}