Bump target ECS version to 8.6.0 #291
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.