[apm-data] fix(9.0): update resource version #129552
Merged
Conversation
This file contains hidden or 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
We introduced some changes in 8.17 that did not update the resource version. As such for cluster upgrading from an older version Elasticsearch would not detect the need to apply the new templates, effectively not introducing the new changes As we updated 8.18 to match and there are some changes to templates between 8.18 and 9.0 we want to ensure the resource version triggers the template upgrade on stack version upgrade. Related to elastic/ingest-dev#5701
endorama
added
>bug
:Data Management/Data streams
|
Pinging @elastic/es-data-management (Team:Data Management) |
endorama
added
v9.0.3
cloud-deploy
simitt
approved these changes
Jun 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We introduced some changes in 8.17 that did not update the
resource version. As such for cluster upgrading from an
older version Elasticsearch would not detect the need to
apply the new templates, effectively not introducing the
new changes
As we updated 8.18 to match and there are some changes to
templates between 8.18 and 9.0 we want to ensure the resource
version triggers the template upgrade on stack version upgrade.
Related to https://github.com/elastic/ingest-dev/issues/5701