fixed bug 226696: clean up ingest pipelines #230106
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
6 tasks
maxcold
added
release_note:skip
Contributor
|
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
Contributor
|
/ci |
Contributor
|
@elasticmachine run docs-build |
Contributor
|
/ci |
maxcold
approved these changes
Aug 1, 2025
Contributor
|
/ci |
Contributor
|
@elasticmachine run docs-build |
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]
History
|
szaffarano
pushed a commit
to szaffarano/kibana
that referenced
this pull request
Aug 5, 2025
## Summary Note: This PR replaces PR elastic#227684 to fix a CLA issue (commit was made under the wrong e-mail) Fixes: - elastic#226696 This PR fixes a bug where internal ingest pipelines used by the cloud_security_posture plugin were not marked as managed. By adding the `_meta.managed: true` field to these pipelines, they will now be correctly recognized as managed pipelines by Elasticsearch and Kibana. This prevents accidental user modifications and aligns with other Elastic-managed pipelines. --- ### Checklist - [x] Follows EUI writing guidelines and includes i18n support where applicable - [ ] Documentation updated as needed - [ ] Unit or functional tests updated or added - [ ] Checked for breaking HTTP API changes - [ ] Flaky Test Runner used on tests changed - [ ] Release Notes section included and appropriate label applied --- ### Identify risks This change only adds metadata to existing ingest pipeline definitions and does not affect pipeline logic or data processing. Risk of regressions or data loss is minimal. The change improves system stability by marking pipelines as managed. --- --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
delanni
pushed a commit
to delanni/kibana
that referenced
this pull request
Aug 5, 2025
## Summary Note: This PR replaces PR elastic#227684 to fix a CLA issue (commit was made under the wrong e-mail) Fixes: - elastic#226696 This PR fixes a bug where internal ingest pipelines used by the cloud_security_posture plugin were not marked as managed. By adding the `_meta.managed: true` field to these pipelines, they will now be correctly recognized as managed pipelines by Elasticsearch and Kibana. This prevents accidental user modifications and aligns with other Elastic-managed pipelines. --- ### Checklist - [x] Follows EUI writing guidelines and includes i18n support where applicable - [ ] Documentation updated as needed - [ ] Unit or functional tests updated or added - [ ] Checked for breaking HTTP API changes - [ ] Flaky Test Runner used on tests changed - [ ] Release Notes section included and appropriate label applied --- ### Identify risks This change only adds metadata to existing ingest pipeline definitions and does not affect pipeline logic or data processing. Risk of regressions or data loss is minimal. The change improves system stability by marking pipelines as managed. --- --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
NicholasPeretti
pushed a commit
to NicholasPeretti/kibana
that referenced
this pull request
Aug 18, 2025
## Summary Note: This PR replaces PR elastic#227684 to fix a CLA issue (commit was made under the wrong e-mail) Fixes: - elastic#226696 This PR fixes a bug where internal ingest pipelines used by the cloud_security_posture plugin were not marked as managed. By adding the `_meta.managed: true` field to these pipelines, they will now be correctly recognized as managed pipelines by Elasticsearch and Kibana. This prevents accidental user modifications and aligns with other Elastic-managed pipelines. --- ### Checklist - [x] Follows EUI writing guidelines and includes i18n support where applicable - [ ] Documentation updated as needed - [ ] Unit or functional tests updated or added - [ ] Checked for breaking HTTP API changes - [ ] Flaky Test Runner used on tests changed - [ ] Release Notes section included and appropriate label applied --- ### Identify risks This change only adds metadata to existing ingest pipeline definitions and does not affect pipeline logic or data processing. Risk of regressions or data loss is minimal. The change improves system stability by marking pipelines as managed. --- --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Summary
Note: This PR replaces PR #227684 to fix a CLA issue (commit was made under the wrong e-mail)
Fixes:
This PR fixes a bug where internal ingest pipelines used by the cloud_security_posture plugin were not marked as managed.
By adding the
_meta.managed: truefield to these pipelines, they will now be correctly recognized as managed pipelines by Elasticsearch and Kibana.This prevents accidental user modifications and aligns with other Elastic-managed pipelines.
Checklist
Identify risks
This change only adds metadata to existing ingest pipeline definitions and does not affect pipeline logic or data processing.
Risk of regressions or data loss is minimal. The change improves system stability by marking pipelines as managed.