From 65356b3691021221cb08121eaec1431cae8f915a Mon Sep 17 00:00:00 2001 From: Edoardo Tenani Date: Tue, 17 Jun 2025 15:15:35 +0200 Subject: [PATCH] update resource version 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 --- x-pack/plugin/apm-data/src/main/resources/resources.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/x-pack/plugin/apm-data/src/main/resources/resources.yaml b/x-pack/plugin/apm-data/src/main/resources/resources.yaml index beca2e5890bc0..748b965318491 100644 --- a/x-pack/plugin/apm-data/src/main/resources/resources.yaml +++ b/x-pack/plugin/apm-data/src/main/resources/resources.yaml @@ -1,7 +1,7 @@ # "version" holds the version of the templates and ingest pipelines installed # by xpack-plugin apm-data. This must be increased whenever an existing template or # pipeline is changed, in order for it to be updated on Elasticsearch upgrade. -version: 13 +version: 20 component-templates: # Data lifecycle.