I wasn't initially planning on moving to 8.6.0 however I noticed we register the index templates under a derived name using {type}-{dataset}.
When releasing new version this would mean our bootstrapping would notice an old index template with the same name and therefor return early.
This PR changes that and includes the version number in the index template name: {type}-{dataset}-{ecs.version} and adjusts the index template priority based on a stable integer representation of the version number.
This means that each new ecs version library deployment can successfully bump the index templates for the target datastreams and indices.
I wasn't initially planning on moving to
8.6.0however I noticed we register the index templates under a derived name using{type}-{dataset}.When releasing new version this would mean our bootstrapping would notice an old index template with the same name and therefor return early.
This PR changes that and includes the version number in the index template name:
{type}-{dataset}-{ecs.version}and adjusts the index template priority based on a stable integer representation of the version number.This means that each new ecs version library deployment can successfully bump the index templates for the target datastreams and indices.