[Streams] Remove managed index template properties from PUT request#231394
Merged
miltonhultgren merged 1 commit intoelastic:mainfrom Aug 12, 2025
Merged
Conversation
miltonhultgren
added
the
release_note:skip
miltonhultgren
added
backport:skip
klacabane
approved these changes
Aug 12, 2025
Contributor
This was referenced Aug 12, 2025
Contributor
|
Is it possible to link the Elasticsearch issue here ? i found an ES issue but its not resolved - elastic/elasticsearch#88225 |
Member
|
Looks like it went into elastic/elasticsearch#132083. |
|
ES issue: elastic/elasticsearch#108754 |
Contributor
|
shouldn't it be backported to 9.1.x? We can see the same test failure in the branch |
delanni
pushed a commit
that referenced
this pull request
Aug 15, 2025
## Summary Skipping test to unblock backport pipelines while #231394 is not backported itself
miltonhultgren
added
backport:version
Contributor
|
Starting backport for target branches: 9.1 https://github.com/elastic/kibana/actions/runs/17034704633 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Aug 18, 2025
…lastic#231394) Recent changes to Elasticsearch now makes the GET index_template response include two properties (created_date, modification_date). When updating Ingest Pipelines for Classic Streams, we read this index template using GET and spread the response into our request where we modify the pipeline. This means we pass these new properties as part of the PUT index_template request which Elasticsearch rejects. This PR just removes those two properties from the PUT request. (cherry picked from commit 49b06b2)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Aug 18, 2025
…uest (#231394) (#232054) # Backport This will backport the following commits from `main` to `9.1`: - [[Streams] Remove managed index template properties from PUT request (#231394)](#231394) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Milton Hultgren","email":"milton.hultgren@elastic.co"},"sourceCommit":{"committedDate":"2025-08-12T11:11:17Z","message":"[Streams] Remove managed index template properties from PUT request (#231394)\n\nRecent changes to Elasticsearch now makes the GET index_template\nresponse include two properties (created_date, modification_date). When\nupdating Ingest Pipelines for Classic Streams, we read this index\ntemplate using GET and spread the response into our request where we\nmodify the pipeline. This means we pass these new properties as part of\nthe PUT index_template request which Elasticsearch rejects.\nThis PR just removes those two properties from the PUT request.","sha":"49b06b23812b287cfe1789994692895f524aa4bb","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:version","Feature:Streams","v9.1.0","v9.2.0"],"title":"[Streams] Remove managed index template properties from PUT request","number":231394,"url":"https://github.com/elastic/kibana/pull/231394","mergeCommit":{"message":"[Streams] Remove managed index template properties from PUT request (#231394)\n\nRecent changes to Elasticsearch now makes the GET index_template\nresponse include two properties (created_date, modification_date). When\nupdating Ingest Pipelines for Classic Streams, we read this index\ntemplate using GET and spread the response into our request where we\nmodify the pipeline. This means we pass these new properties as part of\nthe PUT index_template request which Elasticsearch rejects.\nThis PR just removes those two properties from the PUT request.","sha":"49b06b23812b287cfe1789994692895f524aa4bb"}},"sourceBranch":"main","suggestedTargetBranches":["9.1"],"targetPullRequestStates":[{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231394","number":231394,"mergeCommit":{"message":"[Streams] Remove managed index template properties from PUT request (#231394)\n\nRecent changes to Elasticsearch now makes the GET index_template\nresponse include two properties (created_date, modification_date). When\nupdating Ingest Pipelines for Classic Streams, we read this index\ntemplate using GET and spread the response into our request where we\nmodify the pipeline. This means we pass these new properties as part of\nthe PUT index_template request which Elasticsearch rejects.\nThis PR just removes those two properties from the PUT request.","sha":"49b06b23812b287cfe1789994692895f524aa4bb"}}]}] BACKPORT--> Co-authored-by: Milton Hultgren <milton.hultgren@elastic.co>
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Aug 18, 2025
…lastic#231394) Recent changes to Elasticsearch now makes the GET index_template response include two properties (created_date, modification_date). When updating Ingest Pipelines for Classic Streams, we read this index template using GET and spread the response into our request where we modify the pipeline. This means we pass these new properties as part of the PUT index_template request which Elasticsearch rejects. This PR just removes those two properties from the PUT request.
qn895
pushed a commit
to qn895/kibana
that referenced
this pull request
Aug 26, 2025
…lastic#231394) Recent changes to Elasticsearch now makes the GET index_template response include two properties (created_date, modification_date). When updating Ingest Pipelines for Classic Streams, we read this index template using GET and spread the response into our request where we modify the pipeline. This means we pass these new properties as part of the PUT index_template request which Elasticsearch rejects. This PR just removes those two properties from the PUT request.
This was referenced Oct 30, 2025
flash1293
added a commit
that referenced
this pull request
Oct 30, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 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.
Recent changes to Elasticsearch now makes the GET index_template response include two properties (created_date, modification_date). When updating Ingest Pipelines for Classic Streams, we read this index template using GET and spread the response into our request where we modify the pipeline. This means we pass these new properties as part of the PUT index_template request which Elasticsearch rejects.
This PR just removes those two properties from the PUT request.