[9.2] Strip system-managed date fields from ingest pipelines before PUT (#252579)#253256
Merged
kibanamachine merged 1 commit intoelastic:9.2from Feb 16, 2026
Merged
Conversation
…astic#252579) ## Summary Fixes elastic#251491 Elasticsearch 9.2 introduced system-managed timestamp fields (`created_date`, `created_date_millis`, `modified_date`, `modified_date_millis`) in ingest pipeline GET responses ([elastic/elasticsearch#130847](elastic/elasticsearch#130847)). These fields are read-only, including them in a PUT request causes ES to reject it with: ``` parse_exception: Provided a pipeline property which is managed by the system: created_date_millis ``` The enterprise search plugin's ML inference pipeline management fetches existing parent pipelines and spreads all their fields back into PUT requests when attaching or detaching sub-pipelines. Since 9.2, this inadvertently includes the new system-managed fields, breaking both operations. This PR strips those managed fields via destructuring before the PUT call in both affected code paths: - `addSubPipelineToIndexSpecificMlPipeline` in `create_ml_inference_pipeline.ts` (attaching) - `detachMlInferencePipeline` in `detach_ml_inference_pipeline.ts` (detaching) Similar fix was applied in Fleet: elastic#241096 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [x] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [x] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [x] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [x] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [x] **Low risk** — The change only removes fields from the PUT request payload that ES already rejects. No functional behavior changes for ES versions prior to 9.2 (fields were not present in GET responses before then). Unit tests cover both affected code paths. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> (cherry picked from commit 2da0bcb)
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
9 tasks
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
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.
Backport
This will backport the following commits from
mainto9.2:Questions ?
Please refer to the Backport tool documentation