Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Browse the repository at this point in the history
# Backport This will backport the following commits from `main` to `8.x`: - [Allow data Streams enrich policies (#200903)](#200903) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sonia Sanz Vivas","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-27T18:50:35Z","message":"Allow data Streams enrich policies (#200903)\n\nCloses [#187438](https://github.com/elastic/kibana/issues/187438)\r\n\r\n## Summary\r\n\r\nThis PR introduces the data streams as source indices in the enrich\r\npolicies. For that, it uses the groups functionality, so the indices are\r\nseparated from the data streams.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/1716d57b-b8c7-417a-b75c-33378f3269ca\r\n\r\n### Strings\r\nI've changed some of the existing strings but left other as they were.\r\nI'll be happy to also change those if folks feel that should be the\r\ncase.\r\n\r\nI've added a hint text and changed the label for the box in the creation\r\nstep (marked in yellow)\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 12 35 32\"\r\nsrc=\"https://github.com/user-attachments/assets/794a7063-3f75-4f3d-996c-12ca8b9ed9b6\">\r\n\r\nI haven't change the label for the indices group (green) and I've\r\nfollowed the same structure for the new group category (yellow)\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img alt=\"Screenshot 2024-11-20 at 12 37 51\"\r\nsrc=\"https://github.com/user-attachments/assets/89a554a6-57e4-4208-bde4-d4868dec11bc\">\r\n </td>\r\n <td>\r\n<img alt=\"Screenshot 2024-11-20 at 12 38 16\"\r\nsrc=\"https://github.com/user-attachments/assets/d82c7ae3-79c9-432e-aa3c-8ca02502e18f\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\nI haven't change the 'Source indices' text in the Summary (green)\r\nbecause in the request tab the correspondan field in the request is\r\nindices (blue)\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img alt=\"Screenshot 2024-11-20 at 12 38 53\"\r\nsrc=\"https://github.com/user-attachments/assets/80623ded-11e3-4661-9fa8-ad84182a72a3\">\r\n </td>\r\n <td>\r\n<img alt=\"Screenshot 2024-11-20 at 12 39 19\"\r\nsrc=\"https://github.com/user-attachments/assets/f2ad6449-1a3a-448a-8598-c8c9eb41a717\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\nI also haven't change the 'Source indices' text in the table or in the\r\ndetail flyout (green) since both indices and data streams are treated\r\nlike indices.\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img width=\"898\" alt=\"Screenshot 2024-11-20 at 12 39 52\"\r\nsrc=\"https://github.com/user-attachments/assets/8165fe3f-0286-4ad1-a40d-44e19e4eef29\">\r\n </td>\r\n <td>\r\n<img width=\"892\" alt=\"Screenshot 2024-11-20 at 12 40 25\"\r\nsrc=\"https://github.com/user-attachments/assets/bb046aa4-2a6c-40e0-bb32-ecb4a13adea9\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8629b1da8e392880632b197b4d5b031353a39f28","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Index Management","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor"],"title":"Allow data Streams enrich policies","number":200903,"url":"https://github.com/elastic/kibana/pull/200903","mergeCommit":{"message":"Allow data Streams enrich policies (#200903)\n\nCloses [#187438](https://github.com/elastic/kibana/issues/187438)\r\n\r\n## Summary\r\n\r\nThis PR introduces the data streams as source indices in the enrich\r\npolicies. For that, it uses the groups functionality, so the indices are\r\nseparated from the data streams.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/1716d57b-b8c7-417a-b75c-33378f3269ca\r\n\r\n### Strings\r\nI've changed some of the existing strings but left other as they were.\r\nI'll be happy to also change those if folks feel that should be the\r\ncase.\r\n\r\nI've added a hint text and changed the label for the box in the creation\r\nstep (marked in yellow)\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 12 35 32\"\r\nsrc=\"https://github.com/user-attachments/assets/794a7063-3f75-4f3d-996c-12ca8b9ed9b6\">\r\n\r\nI haven't change the label for the indices group (green) and I've\r\nfollowed the same structure for the new group category (yellow)\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img alt=\"Screenshot 2024-11-20 at 12 37 51\"\r\nsrc=\"https://github.com/user-attachments/assets/89a554a6-57e4-4208-bde4-d4868dec11bc\">\r\n </td>\r\n <td>\r\n<img alt=\"Screenshot 2024-11-20 at 12 38 16\"\r\nsrc=\"https://github.com/user-attachments/assets/d82c7ae3-79c9-432e-aa3c-8ca02502e18f\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\nI haven't change the 'Source indices' text in the Summary (green)\r\nbecause in the request tab the correspondan field in the request is\r\nindices (blue)\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img alt=\"Screenshot 2024-11-20 at 12 38 53\"\r\nsrc=\"https://github.com/user-attachments/assets/80623ded-11e3-4661-9fa8-ad84182a72a3\">\r\n </td>\r\n <td>\r\n<img alt=\"Screenshot 2024-11-20 at 12 39 19\"\r\nsrc=\"https://github.com/user-attachments/assets/f2ad6449-1a3a-448a-8598-c8c9eb41a717\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\nI also haven't change the 'Source indices' text in the table or in the\r\ndetail flyout (green) since both indices and data streams are treated\r\nlike indices.\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img width=\"898\" alt=\"Screenshot 2024-11-20 at 12 39 52\"\r\nsrc=\"https://github.com/user-attachments/assets/8165fe3f-0286-4ad1-a40d-44e19e4eef29\">\r\n </td>\r\n <td>\r\n<img width=\"892\" alt=\"Screenshot 2024-11-20 at 12 40 25\"\r\nsrc=\"https://github.com/user-attachments/assets/bb046aa4-2a6c-40e0-bb32-ecb4a13adea9\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8629b1da8e392880632b197b4d5b031353a39f28"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200903","number":200903,"mergeCommit":{"message":"Allow data Streams enrich policies (#200903)\n\nCloses [#187438](https://github.com/elastic/kibana/issues/187438)\r\n\r\n## Summary\r\n\r\nThis PR introduces the data streams as source indices in the enrich\r\npolicies. For that, it uses the groups functionality, so the indices are\r\nseparated from the data streams.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/1716d57b-b8c7-417a-b75c-33378f3269ca\r\n\r\n### Strings\r\nI've changed some of the existing strings but left other as they were.\r\nI'll be happy to also change those if folks feel that should be the\r\ncase.\r\n\r\nI've added a hint text and changed the label for the box in the creation\r\nstep (marked in yellow)\r\n<img width=\"400\" alt=\"Screenshot 2024-11-20 at 12 35 32\"\r\nsrc=\"https://github.com/user-attachments/assets/794a7063-3f75-4f3d-996c-12ca8b9ed9b6\">\r\n\r\nI haven't change the label for the indices group (green) and I've\r\nfollowed the same structure for the new group category (yellow)\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img alt=\"Screenshot 2024-11-20 at 12 37 51\"\r\nsrc=\"https://github.com/user-attachments/assets/89a554a6-57e4-4208-bde4-d4868dec11bc\">\r\n </td>\r\n <td>\r\n<img alt=\"Screenshot 2024-11-20 at 12 38 16\"\r\nsrc=\"https://github.com/user-attachments/assets/d82c7ae3-79c9-432e-aa3c-8ca02502e18f\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\nI haven't change the 'Source indices' text in the Summary (green)\r\nbecause in the request tab the correspondan field in the request is\r\nindices (blue)\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img alt=\"Screenshot 2024-11-20 at 12 38 53\"\r\nsrc=\"https://github.com/user-attachments/assets/80623ded-11e3-4661-9fa8-ad84182a72a3\">\r\n </td>\r\n <td>\r\n<img alt=\"Screenshot 2024-11-20 at 12 39 19\"\r\nsrc=\"https://github.com/user-attachments/assets/f2ad6449-1a3a-448a-8598-c8c9eb41a717\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\nI also haven't change the 'Source indices' text in the table or in the\r\ndetail flyout (green) since both indices and data streams are treated\r\nlike indices.\r\n<table>\r\n <tr>\r\n <td style=\"padding-right: 10px;\">\r\n<img width=\"898\" alt=\"Screenshot 2024-11-20 at 12 39 52\"\r\nsrc=\"https://github.com/user-attachments/assets/8165fe3f-0286-4ad1-a40d-44e19e4eef29\">\r\n </td>\r\n <td>\r\n<img width=\"892\" alt=\"Screenshot 2024-11-20 at 12 40 25\"\r\nsrc=\"https://github.com/user-attachments/assets/bb046aa4-2a6c-40e0-bb32-ecb4a13adea9\">\r\n </td>\r\n </tr>\r\n</table>\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8629b1da8e392880632b197b4d5b031353a39f28"}}]}] BACKPORT--> Co-authored-by: Sonia Sanz Vivas <[email protected]>
- Loading branch information