6579 commits

Author	SHA1	Message	Date
Julia Bardi	bb1aede715	[8.x][Fleet] Backport auto upgrade feature to 8.x (#217461) ... ## Summary Backport auto upgrade feature to 8.x --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Jill Guyonnet <jill.guyonnet@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> Co-authored-by: Mason Herron <46727170+Supplementing@users.noreply.github.com>	2025-04-09 13:38:12 +02:00
Tim Sullivan	a331e45889	[8.x] [Security Solution] Use static declaration for navigation hierarchy (#215969) (#217248) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Use static declaration for navigation hierarchy (#215969)](https://github.com/elastic/kibana/pull/215969) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tim Sullivan","email":"tsullivan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-04-03T15:38:04Z","message":"[Security Solution] Use static declaration for navigation hierarchy (#215969)\n\n## Summary\n\nPart of Epic: https://github.com/elastic/kibana-team/issues/1439\nAddresses https://github.com/elastic/kibana/issues/212903, but does not\nremove the landing page access. The landing page access will be removed\nin https://github.com/elastic/kibana/pull/210893\n\n**Changes**\n1. Converts the declaration of the Security Solution side navigation for\nserverless and stateful projects into a static declaration, rather than\nalgorithmically parsing registered links to dynamically build the\ndeclaration.\n2. Updates the contents of the \"Assets\" panel to prepare for removal of\nthat landing page.\n3. Eliminates the top-level nesting of the nav items, which removes the\nextra space between the project title and the first nav items. See\n45454bdc4d\n\n**Known issue**: Clicking the \"Browse integrations\" button does not\nclose the secondary nav panel. Doing that will be a relatively simple\nchore, but will require some changes in the SharedUX chrome-navigation\npackage, as well as the `LinkButton` component in the Security Solution\nnavigation-links package.\n\n### Screenshots\nServerless\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ef907a32f2ca3885d60aebd4875f5c8104ee99b1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:SharedUX","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Use static declaration for navigation hierarchy","number":215969,"url":"https://github.com/elastic/kibana/pull/215969","mergeCommit":{"message":"[Security Solution] Use static declaration for navigation hierarchy (#215969)\n\n## Summary\n\nPart of Epic: https://github.com/elastic/kibana-team/issues/1439\nAddresses https://github.com/elastic/kibana/issues/212903, but does not\nremove the landing page access. The landing page access will be removed\nin https://github.com/elastic/kibana/pull/210893\n\n**Changes**\n1. Converts the declaration of the Security Solution side navigation for\nserverless and stateful projects into a static declaration, rather than\nalgorithmically parsing registered links to dynamically build the\ndeclaration.\n2. Updates the contents of the \"Assets\" panel to prepare for removal of\nthat landing page.\n3. Eliminates the top-level nesting of the nav items, which removes the\nextra space between the project title and the first nav items. See\n45454bdc4d\n\n**Known issue**: Clicking the \"Browse integrations\" button does not\nclose the secondary nav panel. Doing that will be a relatively simple\nchore, but will require some changes in the SharedUX chrome-navigation\npackage, as well as the `LinkButton` component in the Security Solution\nnavigation-links package.\n\n### Screenshots\nServerless\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ef907a32f2ca3885d60aebd4875f5c8104ee99b1"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215969","number":215969,"mergeCommit":{"message":"[Security Solution] Use static declaration for navigation hierarchy (#215969)\n\n## Summary\n\nPart of Epic: https://github.com/elastic/kibana-team/issues/1439\nAddresses https://github.com/elastic/kibana/issues/212903, but does not\nremove the landing page access. The landing page access will be removed\nin https://github.com/elastic/kibana/pull/210893\n\n**Changes**\n1. Converts the declaration of the Security Solution side navigation for\nserverless and stateful projects into a static declaration, rather than\nalgorithmically parsing registered links to dynamically build the\ndeclaration.\n2. Updates the contents of the \"Assets\" panel to prepare for removal of\nthat landing page.\n3. Eliminates the top-level nesting of the nav items, which removes the\nextra space between the project title and the first nav items. See\n45454bdc4d\n\n**Known issue**: Clicking the \"Browse integrations\" button does not\nclose the secondary nav panel. Doing that will be a relatively simple\nchore, but will require some changes in the SharedUX chrome-navigation\npackage, as well as the `LinkButton` component in the Security Solution\nnavigation-links package.\n\n### Screenshots\nServerless\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"ef907a32f2ca3885d60aebd4875f5c8104ee99b1"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-04-08 18:26:39 +02:00
Kibana Machine	53921b8f61	[8.x] [unified search] optimize async chunk loading (#214483) (#216115) ... # Backport This will backport the following commits from `main` to `8.x`: - [[unified search] optimize async chunk loading (#214483)](https://github.com/elastic/kibana/pull/214483) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-27T00:39:58Z","message":"[unified search] optimize async chunk loading (#214483)\n\nPR reduces unifiedSearch chunks into ui chunk, action chunk, and a\nautocomplete chunk.\n\n### Before\n<img width=\"350\" alt=\"Screenshot 2025-03-14 at 8 47 10 AM\"\nsrc=\"https://github.com/user-attachments/assets/f54fe21e-7548-48a1-8874-e36377826701\"\n/>\n\n### After\nThe second chunk request is because search bar loads KQL suggestions.\nThis will be addressed in a follow up PR and the search bar will lazy\nload suggestions only when interacted with.\n<img width=\"350\" alt=\"Screenshot 2025-03-14 at 12 56 28 PM\"\nsrc=\"https://github.com/user-attachments/assets/8f23ee56-a57a-489b-aeab-caa30f739d03\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3bc1465365872d093a9e8ff5666ab0b01738c792","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","backport:version","v9.1.0","v8.19.0"],"title":"[unified search] optimize async chunk loading","number":214483,"url":"https://github.com/elastic/kibana/pull/214483","mergeCommit":{"message":"[unified search] optimize async chunk loading (#214483)\n\nPR reduces unifiedSearch chunks into ui chunk, action chunk, and a\nautocomplete chunk.\n\n### Before\n<img width=\"350\" alt=\"Screenshot 2025-03-14 at 8 47 10 AM\"\nsrc=\"https://github.com/user-attachments/assets/f54fe21e-7548-48a1-8874-e36377826701\"\n/>\n\n### After\nThe second chunk request is because search bar loads KQL suggestions.\nThis will be addressed in a follow up PR and the search bar will lazy\nload suggestions only when interacted with.\n<img width=\"350\" alt=\"Screenshot 2025-03-14 at 12 56 28 PM\"\nsrc=\"https://github.com/user-attachments/assets/8f23ee56-a57a-489b-aeab-caa30f739d03\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3bc1465365872d093a9e8ff5666ab0b01738c792"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214483","number":214483,"mergeCommit":{"message":"[unified search] optimize async chunk loading (#214483)\n\nPR reduces unifiedSearch chunks into ui chunk, action chunk, and a\nautocomplete chunk.\n\n### Before\n<img width=\"350\" alt=\"Screenshot 2025-03-14 at 8 47 10 AM\"\nsrc=\"https://github.com/user-attachments/assets/f54fe21e-7548-48a1-8874-e36377826701\"\n/>\n\n### After\nThe second chunk request is because search bar loads KQL suggestions.\nThis will be addressed in a follow up PR and the search bar will lazy\nload suggestions only when interacted with.\n<img width=\"350\" alt=\"Screenshot 2025-03-14 at 12 56 28 PM\"\nsrc=\"https://github.com/user-attachments/assets/8f23ee56-a57a-489b-aeab-caa30f739d03\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"3bc1465365872d093a9e8ff5666ab0b01738c792"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Nathan Reese <reese.nathan@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>	2025-03-31 16:03:41 +01:00
Ievgen Sorokopud	baa0362f78	[8.x] [Security Solution] Move rule actions field and its validation into the common folder (#215494) (#215949) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Move rule actions field and its validation into the common folder (#215494)](https://github.com/elastic/kibana/pull/215494) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T19:50:08Z","message":"[Security Solution] Move rule actions field and its validation into the common folder (#215494)\n\n## Summary\n\nWith this PR we make `RuleActionsField` component and relevant\nvalidations reusable outside of and not bound to the rules management.\n\nAs part of the Attack Discovery Scheduling\n[feature](https://github.com/elastic/security-team/issues/10142) we\nwould like to be able to setup schedules (similar to detection rules,\njust named differently within the feature space) and be able to add\nactions (email, slack, webhook etc.).\n\nCurrently `RuleActionsField` lives inside the\n`x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation/components/`\nfolder. We could just reference it from within the Attack Discovery\nfolder, but for better code structure it will be good to put it into a\ncommon place.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8075\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"760b0cfca324eabaf544f23fdff819bab441576c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team: SecuritySolution","Team:Detection Rule Management","Team:Detection Engine","Team:Security Generative AI","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Move rule actions field and its validation into the common folder","number":215494,"url":"https://github.com/elastic/kibana/pull/215494","mergeCommit":{"message":"[Security Solution] Move rule actions field and its validation into the common folder (#215494)\n\n## Summary\n\nWith this PR we make `RuleActionsField` component and relevant\nvalidations reusable outside of and not bound to the rules management.\n\nAs part of the Attack Discovery Scheduling\n[feature](https://github.com/elastic/security-team/issues/10142) we\nwould like to be able to setup schedules (similar to detection rules,\njust named differently within the feature space) and be able to add\nactions (email, slack, webhook etc.).\n\nCurrently `RuleActionsField` lives inside the\n`x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation/components/`\nfolder. We could just reference it from within the Attack Discovery\nfolder, but for better code structure it will be good to put it into a\ncommon place.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8075\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"760b0cfca324eabaf544f23fdff819bab441576c"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215494","number":215494,"mergeCommit":{"message":"[Security Solution] Move rule actions field and its validation into the common folder (#215494)\n\n## Summary\n\nWith this PR we make `RuleActionsField` component and relevant\nvalidations reusable outside of and not bound to the rules management.\n\nAs part of the Attack Discovery Scheduling\n[feature](https://github.com/elastic/security-team/issues/10142) we\nwould like to be able to setup schedules (similar to detection rules,\njust named differently within the feature space) and be able to add\nactions (email, slack, webhook etc.).\n\nCurrently `RuleActionsField` lives inside the\n`x-pack/solutions/security/plugins/security_solution/public/detection_engine/rule_creation/components/`\nfolder. We could just reference it from within the Attack Discovery\nfolder, but for better code structure it will be good to put it into a\ncommon place.\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8075\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"760b0cfca324eabaf544f23fdff819bab441576c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-25 23:53:05 +02:00
Philippe Oberti	485175a7c5	[8.x] [Security Solution] Move files from detections folder to detection_engine folder (#215085) (#215923) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Move files from detections folder to detection_engine folder (#215085)](https://github.com/elastic/kibana/pull/215085) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T13:51:50Z","message":"[Security Solution] Move files from detections folder to detection_engine folder (#215085)\n\n## Summary\n\nThis PR is - at its core - only moving a handful of files around. A lot\nof of these files lived under the `detections` folder, but were almost\nexclusively used in files under the `detection_engine` folder. This is\nwhy the PR seems so huge. Almost everything modified here is only files\nimports...\n\nHere are the few files that were actually moved around:\n\n1. The files `detection_engine.tsx`, `detection_engine_no_index.tsx`,\n`detection_engine_user_unauthenticated.tsx` (and their respective test\nfiles) have been moved from\n`security_solution/public/detections/pages/detection_engine` to\n`security_solution/public/detections/pages/alerts`. I thought about\nrenaming them as well, but felt like there was already enough changes.\nRenaming will be done in a follow up PR.\n\n2. The content of the\n`security_solution/public/detections/pages/detection_engine/rules`\nfolder was moved to `security_solution/public/detection_engine/common`\nas almost the entire folder content is only used within the\n`security_solution/public/detection_engine` folder.\n\n#### Notes\n\n_If there is a better folder for the files moved to the\n`detection_engine/common` folder, feel free to suggest. I'll be happy to\nmake the change!_\n\nThe CODEOWNERS file has been updated and simplified accordingly.\n\nOnly imports should have been modified. No code, logic or UI changes!\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b2846452083943672cc7bee1a43cbcf06915903","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution] Move files from detections folder to detection_engine folder","number":215085,"url":"https://github.com/elastic/kibana/pull/215085","mergeCommit":{"message":"[Security Solution] Move files from detections folder to detection_engine folder (#215085)\n\n## Summary\n\nThis PR is - at its core - only moving a handful of files around. A lot\nof of these files lived under the `detections` folder, but were almost\nexclusively used in files under the `detection_engine` folder. This is\nwhy the PR seems so huge. Almost everything modified here is only files\nimports...\n\nHere are the few files that were actually moved around:\n\n1. The files `detection_engine.tsx`, `detection_engine_no_index.tsx`,\n`detection_engine_user_unauthenticated.tsx` (and their respective test\nfiles) have been moved from\n`security_solution/public/detections/pages/detection_engine` to\n`security_solution/public/detections/pages/alerts`. I thought about\nrenaming them as well, but felt like there was already enough changes.\nRenaming will be done in a follow up PR.\n\n2. The content of the\n`security_solution/public/detections/pages/detection_engine/rules`\nfolder was moved to `security_solution/public/detection_engine/common`\nas almost the entire folder content is only used within the\n`security_solution/public/detection_engine` folder.\n\n#### Notes\n\n_If there is a better folder for the files moved to the\n`detection_engine/common` folder, feel free to suggest. I'll be happy to\nmake the change!_\n\nThe CODEOWNERS file has been updated and simplified accordingly.\n\nOnly imports should have been modified. No code, logic or UI changes!\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b2846452083943672cc7bee1a43cbcf06915903"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215085","number":215085,"mergeCommit":{"message":"[Security Solution] Move files from detections folder to detection_engine folder (#215085)\n\n## Summary\n\nThis PR is - at its core - only moving a handful of files around. A lot\nof of these files lived under the `detections` folder, but were almost\nexclusively used in files under the `detection_engine` folder. This is\nwhy the PR seems so huge. Almost everything modified here is only files\nimports...\n\nHere are the few files that were actually moved around:\n\n1. The files `detection_engine.tsx`, `detection_engine_no_index.tsx`,\n`detection_engine_user_unauthenticated.tsx` (and their respective test\nfiles) have been moved from\n`security_solution/public/detections/pages/detection_engine` to\n`security_solution/public/detections/pages/alerts`. I thought about\nrenaming them as well, but felt like there was already enough changes.\nRenaming will be done in a follow up PR.\n\n2. The content of the\n`security_solution/public/detections/pages/detection_engine/rules`\nfolder was moved to `security_solution/public/detection_engine/common`\nas almost the entire folder content is only used within the\n`security_solution/public/detection_engine` folder.\n\n#### Notes\n\n_If there is a better folder for the files moved to the\n`detection_engine/common` folder, feel free to suggest. I'll be happy to\nmake the change!_\n\nThe CODEOWNERS file has been updated and simplified accordingly.\n\nOnly imports should have been modified. No code, logic or UI changes!\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4b2846452083943672cc7bee1a43cbcf06915903"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-25 21:49:41 +02:00
Kibana Machine	5a40684e0a	[8.x] Disable allowAbsoluteUrls for axios (#215138) (#215829) ... # Backport This will backport the following commits from `main` to `8.x`: - [Disable `allowAbsoluteUrls` for axios (#215138)](https://github.com/elastic/kibana/pull/215138) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-25T08:52:36Z","message":"Disable `allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter https://github.com/elastic/kibana/pull/214843, `axios` client\nusages need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers: if you think it's a mistake, and you created a client to\nrequest for absolute URLs, consider unsetting the `baseURL` to\ncommunicate intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","Team:QA","Team:Security","release_note:skip","backport:all-open","Team:obs-ux-logs","Team:obs-ux-infra_services","v9.1.0"],"title":"Disable `allowAbsoluteUrls` for axios","number":215138,"url":"https://github.com/elastic/kibana/pull/215138","mergeCommit":{"message":"Disable `allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter https://github.com/elastic/kibana/pull/214843, `axios` client\nusages need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers: if you think it's a mistake, and you created a client to\nrequest for absolute URLs, consider unsetting the `baseURL` to\ncommunicate intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215138","number":215138,"mergeCommit":{"message":"Disable `allowAbsoluteUrls` for axios (#215138)\n\n## Summary\nAfter https://github.com/elastic/kibana/pull/214843, `axios` client\nusages need to set a flag to prevent the vulnerable behavior.\n\nTo reviewers: if you think it's a mistake, and you created a client to\nrequest for absolute URLs, consider unsetting the `baseURL` to\ncommunicate intent.","sha":"e40b17aa22ec1a2fbc56ae8651e12f658099ec14"}}]}] BACKPORT--> --------- Co-authored-by: Alex Szabo <alex.szabo@elastic.co>	2025-03-25 18:23:20 +02:00
Umberto Pepato	a2a8a0e9a8	[8.x] [ResponseOps][Alerts] Create embeddable alerts table plugin (#213909) (#215861) ... # Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Alerts] Create embeddable alerts table plugin (#213909)](https://github.com/elastic/kibana/pull/213909) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T10:02:54Z","message":"[ResponseOps][Alerts] Create embeddable alerts table plugin (#213909)\n\n## Summary\n\nCreates a wrapper plugin around the alerts table, that registers a basic\nalerts table embeddable panel for dashboards.\n\n> [!NOTE]\n> This PR is a preparation work for the [embeddable alerts\ntable](https://github.com/elastic/kibana/issues/197483). The feature is\ndisabled for end-users while waiting for other dependent PRs to be\nintegrated with this, and uses a partially hard-coded table\nconfiguration for testing purposes. The final panel will be fully\nconfigurable by the user.\n\n## Verification steps\n\n1. Uncomment this line\n\n4d49e98b4d/x-pack/platform/plugins/shared/embeddable_alerts_table/public/plugin.ts (L34)\n(I'm using a comment to avoid polluting the embeddable examples app with\nthis panel for a short time)\n2. Create one or more ES Query rules that fire alerts\n3. Visit the Dashboards page and create a dashboard, then enter edit\nmode\n4. Click \"Add panel\"\n5. Under \"Visualizations\" choose \"Alerts table\"\n6. Check that the table panel was created correctly\n6.1. Shows any alerts fired by the ES Query rule(s)\n6.2. Check that the table adapts correctly to the panel when resizing,\nand all normal interactions with the alerts table work correctly\n(adding/removing fields, opening alerts in flyouts, using row/bulk\nactions)\n6.3. Check that panels respond to the global time filter (only time\nfilters, not KQL search or filters)\n6.4. Check that panels respond to individual time filters (⛭ icon >\nApply custom time range)\n11. Create a role with access to dashboards but without any alerting\ncapability and a user assigned to that role\n12. Repeat steps 3 and 4, and verify that the \"Alerts table\" option\nisn't available under \"Visualizations\"\n13. Add any alerting capability to the role, such as Management > Stack\nrules\n14. Repeat steps 3 and 4, and verify that the \"Alerts table\" is\navailable again\n\n## References\n\nCloses #203611\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4aab9d4c4832ae5f59c29cfa36d29b56317da344","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport missing","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][Alerts] Create embeddable alerts table plugin","number":213909,"url":"https://github.com/elastic/kibana/pull/213909","mergeCommit":{"message":"[ResponseOps][Alerts] Create embeddable alerts table plugin (#213909)\n\n## Summary\n\nCreates a wrapper plugin around the alerts table, that registers a basic\nalerts table embeddable panel for dashboards.\n\n> [!NOTE]\n> This PR is a preparation work for the [embeddable alerts\ntable](https://github.com/elastic/kibana/issues/197483). The feature is\ndisabled for end-users while waiting for other dependent PRs to be\nintegrated with this, and uses a partially hard-coded table\nconfiguration for testing purposes. The final panel will be fully\nconfigurable by the user.\n\n## Verification steps\n\n1. Uncomment this line\n\n4d49e98b4d/x-pack/platform/plugins/shared/embeddable_alerts_table/public/plugin.ts (L34)\n(I'm using a comment to avoid polluting the embeddable examples app with\nthis panel for a short time)\n2. Create one or more ES Query rules that fire alerts\n3. Visit the Dashboards page and create a dashboard, then enter edit\nmode\n4. Click \"Add panel\"\n5. Under \"Visualizations\" choose \"Alerts table\"\n6. Check that the table panel was created correctly\n6.1. Shows any alerts fired by the ES Query rule(s)\n6.2. Check that the table adapts correctly to the panel when resizing,\nand all normal interactions with the alerts table work correctly\n(adding/removing fields, opening alerts in flyouts, using row/bulk\nactions)\n6.3. Check that panels respond to the global time filter (only time\nfilters, not KQL search or filters)\n6.4. Check that panels respond to individual time filters (⛭ icon >\nApply custom time range)\n11. Create a role with access to dashboards but without any alerting\ncapability and a user assigned to that role\n12. Repeat steps 3 and 4, and verify that the \"Alerts table\" option\nisn't available under \"Visualizations\"\n13. Add any alerting capability to the role, such as Management > Stack\nrules\n14. Repeat steps 3 and 4, and verify that the \"Alerts table\" is\navailable again\n\n## References\n\nCloses #203611\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4aab9d4c4832ae5f59c29cfa36d29b56317da344"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213909","number":213909,"mergeCommit":{"message":"[ResponseOps][Alerts] Create embeddable alerts table plugin (#213909)\n\n## Summary\n\nCreates a wrapper plugin around the alerts table, that registers a basic\nalerts table embeddable panel for dashboards.\n\n> [!NOTE]\n> This PR is a preparation work for the [embeddable alerts\ntable](https://github.com/elastic/kibana/issues/197483). The feature is\ndisabled for end-users while waiting for other dependent PRs to be\nintegrated with this, and uses a partially hard-coded table\nconfiguration for testing purposes. The final panel will be fully\nconfigurable by the user.\n\n## Verification steps\n\n1. Uncomment this line\n\n4d49e98b4d/x-pack/platform/plugins/shared/embeddable_alerts_table/public/plugin.ts (L34)\n(I'm using a comment to avoid polluting the embeddable examples app with\nthis panel for a short time)\n2. Create one or more ES Query rules that fire alerts\n3. Visit the Dashboards page and create a dashboard, then enter edit\nmode\n4. Click \"Add panel\"\n5. Under \"Visualizations\" choose \"Alerts table\"\n6. Check that the table panel was created correctly\n6.1. Shows any alerts fired by the ES Query rule(s)\n6.2. Check that the table adapts correctly to the panel when resizing,\nand all normal interactions with the alerts table work correctly\n(adding/removing fields, opening alerts in flyouts, using row/bulk\nactions)\n6.3. Check that panels respond to the global time filter (only time\nfilters, not KQL search or filters)\n6.4. Check that panels respond to individual time filters (⛭ icon >\nApply custom time range)\n11. Create a role with access to dashboards but without any alerting\ncapability and a user assigned to that role\n12. Repeat steps 3 and 4, and verify that the \"Alerts table\" option\nisn't available under \"Visualizations\"\n13. Add any alerting capability to the role, such as Management > Stack\nrules\n14. Repeat steps 3 and 4, and verify that the \"Alerts table\" is\navailable again\n\n## References\n\nCloses #203611\n\n### Checklist\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"4aab9d4c4832ae5f59c29cfa36d29b56317da344"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-25 17:12:00 +02:00
Efe Gürkan YALAMAN	ca54d59f2f	[8.x] [Query Rules]Query rules UI plugin (#215029) (#215608) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Query Rules]Query rules UI plugin (#215029)](https://github.com/elastic/kibana/pull/215029) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Efe Gürkan YALAMAN","email":"efeguerkan.yalaman@elastic.co"},"sourceCommit":{"committedDate":"2025-03-21T14:19:25Z","message":"[Query Rules]Query rules UI plugin (#215029)\n\n## Summary\n\nAdds Query Rules UI Plugin. It is disabled and pretty much empty as we\nwant to split the implementation in multiple parts and enable the\nfeature once implementation is done.\n\nIt is disabled for Security.\nIt is disabled for Observability.\nIt is enabled but behind a feature flag for Search while it is not\nuseful to enable it with partial implementations.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"62f8027c57477ca5a7366b8046e73ac4dcb1789a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","backport:version","v9.1.0","v8.19.0"],"title":"[Query Rules]Query rules UI plugin","number":215029,"url":"https://github.com/elastic/kibana/pull/215029","mergeCommit":{"message":"[Query Rules]Query rules UI plugin (#215029)\n\n## Summary\n\nAdds Query Rules UI Plugin. It is disabled and pretty much empty as we\nwant to split the implementation in multiple parts and enable the\nfeature once implementation is done.\n\nIt is disabled for Security.\nIt is disabled for Observability.\nIt is enabled but behind a feature flag for Search while it is not\nuseful to enable it with partial implementations.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"62f8027c57477ca5a7366b8046e73ac4dcb1789a"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215029","number":215029,"mergeCommit":{"message":"[Query Rules]Query rules UI plugin (#215029)\n\n## Summary\n\nAdds Query Rules UI Plugin. It is disabled and pretty much empty as we\nwant to split the implementation in multiple parts and enable the\nfeature once implementation is done.\n\nIt is disabled for Security.\nIt is disabled for Observability.\nIt is enabled but behind a feature flag for Search while it is not\nuseful to enable it with partial implementations.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"62f8027c57477ca5a7366b8046e73ac4dcb1789a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-24 08:15:58 -04:00
Gerard Soldevila	b6ae9b0518	[8.x] SKA: Relocate /test to /src/platform/test (#210956) (#214791) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Relocate /test to /src/platform/test (#210956)](https://github.com/elastic/kibana/pull/210956) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T16:57:23Z","message":"SKA: Relocate /test to /src/platform/test (#210956)\n\n## Summary\n\nPart of https://github.com/elastic/kibana-team/issues/1503\n\nThis is a first step towards the relocation of all the Kibana tests.\n\nThe `/test/` folder at the root, which is in itself a package\n(`@kbn/test-suites-src`), and contains a large number of tests and test\nplugins, is being relocated under `src/platform/test`.\n\nAll the tests under this folder should be related to common platform\nfeatures, and they should not have any dependency towards\nsolution-specific components or features.\n\n<details >\n<summary>Updated relative paths</summary>\n\n```\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/jest.config.js:12\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/package.json:10\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/package.json:11\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/tsconfig.json:11\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/tsconfig.json:2\nsrc/platform/test/analytics/plugins/analytics_plugin_a/package.json:10\nsrc/platform/test/analytics/plugins/analytics_plugin_a/package.json:11\nsrc/platform/test/analytics/plugins/analytics_plugin_a/tsconfig.json:10\nsrc/platform/test/analytics/plugins/analytics_plugin_a/tsconfig.json:2\nsrc/platform/test/api_integration/jest.config.js:12\nsrc/platform/test/common/plugins/newsfeed/tsconfig.json:2\nsrc/platform/test/common/plugins/otel_metrics/tsconfig.json:2\nsrc/platform/test/functional/jest.config.js:12\nsrc/platform/test/harden/child_process.js:13\nsrc/platform/test/harden/lodash_template.js:13\nsrc/platform/test/harden/prototype.js:10\nsrc/platform/test/health_gateway/plugins/status/tsconfig.json:2\nsrc/platform/test/interactive_setup_api_integration/plugins/test_endpoints/tsconfig.json:2\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/package.json:11\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/package.json:12\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/tsconfig.json:11\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/tsconfig.json:2\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/package.json:11\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/package.json:12\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/tsconfig.json:2\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/tsconfig.json:9\nsrc/platform/test/package/Vagrantfile:2\nsrc/platform/test/plugin_functional/README.md:40\nsrc/platform/test/plugin_functional/plugins/app_link_test/package.json:11\nsrc/platform/test/plugin_functional/plugins/app_link_test/package.json:12\nsrc/platform/test/plugin_functional/plugins/app_link_test/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/app_link_test/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_app_status/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_app_status/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_app_status/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_app_status/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_history_block/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_history_block/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_history_block/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_history_block/tsconfig.json:6\nsrc/platform/test/plugin_functional/plugins/core_http/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_http/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_http/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_http/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/package.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/data_search/package.json:10\nsrc/platform/test/plugin_functional/plugins/data_search/package.json:9\nsrc/platform/test/plugin_functional/plugins/data_search/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/data_search/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/package.json:10\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/package.json:9\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/package.json:11\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/package.json:12\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/hardening/package.json:11\nsrc/platform/test/plugin_functional/plugins/hardening/package.json:12\nsrc/platform/test/plugin_functional/plugins/hardening/tsconfig.json:12\nsrc/platform/test/plugin_functional/plugins/hardening/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/index_patterns/package.json:11\nsrc/platform/test/plugin_functional/plugins/index_patterns/package.json:12\nsrc/platform/test/plugin_functional/plugins/index_patterns/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/index_patterns/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/session_notifications/package.json:11\nsrc/platform/test/plugin_functional/plugins/session_notifications/package.json:12\nsrc/platform/test/plugin_functional/plugins/session_notifications/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/session_notifications/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/telemetry/package.json:11\nsrc/platform/test/plugin_functional/plugins/telemetry/package.json:12\nsrc/platform/test/plugin_functional/plugins/telemetry/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/telemetry/tsconfig.json:6\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/usage_collection/package.json:11\nsrc/platform/test/plugin_functional/plugins/usage_collection/package.json:12\nsrc/platform/test/plugin_functional/plugins/usage_collection/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/usage_collection/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_a/package.json:10\nsrc/platform/test/server_integration/plugins/status_plugin_a/package.json:11\nsrc/platform/test/server_integration/plugins/status_plugin_a/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_a/tsconfig.json:9\nsrc/platform/test/server_integration/plugins/status_plugin_b/package.json:10\nsrc/platform/test/server_integration/plugins/status_plugin_b/package.json:11\nsrc/platform/test/server_integration/plugins/status_plugin_b/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_b/tsconfig.json:9\n```\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"355a834659b74333162008d54d44be0f2a14fb6b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:QA","release_note:skip","backport:skip","plugin groups","v9.1.0"],"title":"SKA: Relocate /test to /src/platform/test","number":210956,"url":"https://github.com/elastic/kibana/pull/210956","mergeCommit":{"message":"SKA: Relocate /test to /src/platform/test (#210956)\n\n## Summary\n\nPart of https://github.com/elastic/kibana-team/issues/1503\n\nThis is a first step towards the relocation of all the Kibana tests.\n\nThe `/test/` folder at the root, which is in itself a package\n(`@kbn/test-suites-src`), and contains a large number of tests and test\nplugins, is being relocated under `src/platform/test`.\n\nAll the tests under this folder should be related to common platform\nfeatures, and they should not have any dependency towards\nsolution-specific components or features.\n\n<details >\n<summary>Updated relative paths</summary>\n\n```\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/jest.config.js:12\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/package.json:10\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/package.json:11\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/tsconfig.json:11\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/tsconfig.json:2\nsrc/platform/test/analytics/plugins/analytics_plugin_a/package.json:10\nsrc/platform/test/analytics/plugins/analytics_plugin_a/package.json:11\nsrc/platform/test/analytics/plugins/analytics_plugin_a/tsconfig.json:10\nsrc/platform/test/analytics/plugins/analytics_plugin_a/tsconfig.json:2\nsrc/platform/test/api_integration/jest.config.js:12\nsrc/platform/test/common/plugins/newsfeed/tsconfig.json:2\nsrc/platform/test/common/plugins/otel_metrics/tsconfig.json:2\nsrc/platform/test/functional/jest.config.js:12\nsrc/platform/test/harden/child_process.js:13\nsrc/platform/test/harden/lodash_template.js:13\nsrc/platform/test/harden/prototype.js:10\nsrc/platform/test/health_gateway/plugins/status/tsconfig.json:2\nsrc/platform/test/interactive_setup_api_integration/plugins/test_endpoints/tsconfig.json:2\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/package.json:11\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/package.json:12\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/tsconfig.json:11\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/tsconfig.json:2\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/package.json:11\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/package.json:12\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/tsconfig.json:2\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/tsconfig.json:9\nsrc/platform/test/package/Vagrantfile:2\nsrc/platform/test/plugin_functional/README.md:40\nsrc/platform/test/plugin_functional/plugins/app_link_test/package.json:11\nsrc/platform/test/plugin_functional/plugins/app_link_test/package.json:12\nsrc/platform/test/plugin_functional/plugins/app_link_test/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/app_link_test/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_app_status/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_app_status/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_app_status/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_app_status/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_history_block/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_history_block/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_history_block/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_history_block/tsconfig.json:6\nsrc/platform/test/plugin_functional/plugins/core_http/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_http/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_http/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_http/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/package.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/data_search/package.json:10\nsrc/platform/test/plugin_functional/plugins/data_search/package.json:9\nsrc/platform/test/plugin_functional/plugins/data_search/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/data_search/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/package.json:10\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/package.json:9\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/package.json:11\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/package.json:12\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/hardening/package.json:11\nsrc/platform/test/plugin_functional/plugins/hardening/package.json:12\nsrc/platform/test/plugin_functional/plugins/hardening/tsconfig.json:12\nsrc/platform/test/plugin_functional/plugins/hardening/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/index_patterns/package.json:11\nsrc/platform/test/plugin_functional/plugins/index_patterns/package.json:12\nsrc/platform/test/plugin_functional/plugins/index_patterns/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/index_patterns/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/session_notifications/package.json:11\nsrc/platform/test/plugin_functional/plugins/session_notifications/package.json:12\nsrc/platform/test/plugin_functional/plugins/session_notifications/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/session_notifications/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/telemetry/package.json:11\nsrc/platform/test/plugin_functional/plugins/telemetry/package.json:12\nsrc/platform/test/plugin_functional/plugins/telemetry/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/telemetry/tsconfig.json:6\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/usage_collection/package.json:11\nsrc/platform/test/plugin_functional/plugins/usage_collection/package.json:12\nsrc/platform/test/plugin_functional/plugins/usage_collection/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/usage_collection/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_a/package.json:10\nsrc/platform/test/server_integration/plugins/status_plugin_a/package.json:11\nsrc/platform/test/server_integration/plugins/status_plugin_a/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_a/tsconfig.json:9\nsrc/platform/test/server_integration/plugins/status_plugin_b/package.json:10\nsrc/platform/test/server_integration/plugins/status_plugin_b/package.json:11\nsrc/platform/test/server_integration/plugins/status_plugin_b/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_b/tsconfig.json:9\n```\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"355a834659b74333162008d54d44be0f2a14fb6b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210956","number":210956,"mergeCommit":{"message":"SKA: Relocate /test to /src/platform/test (#210956)\n\n## Summary\n\nPart of https://github.com/elastic/kibana-team/issues/1503\n\nThis is a first step towards the relocation of all the Kibana tests.\n\nThe `/test/` folder at the root, which is in itself a package\n(`@kbn/test-suites-src`), and contains a large number of tests and test\nplugins, is being relocated under `src/platform/test`.\n\nAll the tests under this folder should be related to common platform\nfeatures, and they should not have any dependency towards\nsolution-specific components or features.\n\n<details >\n<summary>Updated relative paths</summary>\n\n```\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/jest.config.js:12\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/package.json:10\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/package.json:11\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/tsconfig.json:11\nsrc/platform/test/analytics/plugins/analytics_ftr_helpers/tsconfig.json:2\nsrc/platform/test/analytics/plugins/analytics_plugin_a/package.json:10\nsrc/platform/test/analytics/plugins/analytics_plugin_a/package.json:11\nsrc/platform/test/analytics/plugins/analytics_plugin_a/tsconfig.json:10\nsrc/platform/test/analytics/plugins/analytics_plugin_a/tsconfig.json:2\nsrc/platform/test/api_integration/jest.config.js:12\nsrc/platform/test/common/plugins/newsfeed/tsconfig.json:2\nsrc/platform/test/common/plugins/otel_metrics/tsconfig.json:2\nsrc/platform/test/functional/jest.config.js:12\nsrc/platform/test/harden/child_process.js:13\nsrc/platform/test/harden/lodash_template.js:13\nsrc/platform/test/harden/prototype.js:10\nsrc/platform/test/health_gateway/plugins/status/tsconfig.json:2\nsrc/platform/test/interactive_setup_api_integration/plugins/test_endpoints/tsconfig.json:2\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/package.json:11\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/package.json:12\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/tsconfig.json:11\nsrc/platform/test/interpreter_functional/plugins/kbn_tp_run_pipeline/tsconfig.json:2\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/package.json:11\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/package.json:12\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/tsconfig.json:2\nsrc/platform/test/node_roles_functional/plugins/core_plugin_initializer_context/tsconfig.json:9\nsrc/platform/test/package/Vagrantfile:2\nsrc/platform/test/plugin_functional/README.md:40\nsrc/platform/test/plugin_functional/plugins/app_link_test/package.json:11\nsrc/platform/test/plugin_functional/plugins/app_link_test/package.json:12\nsrc/platform/test/plugin_functional/plugins/app_link_test/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/app_link_test/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_app_status/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_app_status/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_app_status/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_app_status/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_a/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_dynamic_resolving_b/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_history_block/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_history_block/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_history_block/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_history_block/tsconfig.json:6\nsrc/platform/test/plugin_functional/plugins/core_http/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_http/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_http/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_http/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_a/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_appleave/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_b/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_chromeless/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_deep_links/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_deprecations/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/package.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_execution_context/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_helpmenu/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_plugin_route_timeouts/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_plugin_static_assets/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/core_provider_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/data_search/package.json:10\nsrc/platform/test/plugin_functional/plugins/data_search/package.json:9\nsrc/platform/test/plugin_functional/plugins/data_search/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/data_search/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/package.json:10\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/package.json:9\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/elasticsearch_client_plugin/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/package.json:11\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/package.json:12\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/eui_provider_dev_warning/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/hardening/package.json:11\nsrc/platform/test/plugin_functional/plugins/hardening/package.json:12\nsrc/platform/test/plugin_functional/plugins/hardening/tsconfig.json:12\nsrc/platform/test/plugin_functional/plugins/hardening/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/index_patterns/package.json:11\nsrc/platform/test/plugin_functional/plugins/index_patterns/package.json:12\nsrc/platform/test/plugin_functional/plugins/index_patterns/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/index_patterns/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/kbn_sample_panel_action/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_top_nav/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/package.json:11\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/package.json:12\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/kbn_tp_custom_visualizations/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/tsconfig.json:10\nsrc/platform/test/plugin_functional/plugins/management_test_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/rendering_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_object_export_transforms/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/saved_object_import_warnings/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_from_http_apis_type/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/package.json:11\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/package.json:12\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/saved_objects_hidden_type/tsconfig.json:9\nsrc/platform/test/plugin_functional/plugins/session_notifications/package.json:11\nsrc/platform/test/plugin_functional/plugins/session_notifications/package.json:12\nsrc/platform/test/plugin_functional/plugins/session_notifications/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/session_notifications/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/telemetry/package.json:11\nsrc/platform/test/plugin_functional/plugins/telemetry/package.json:12\nsrc/platform/test/plugin_functional/plugins/telemetry/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/telemetry/tsconfig.json:6\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/package.json:11\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/package.json:12\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/tsconfig.json:2\nsrc/platform/test/plugin_functional/plugins/ui_settings_plugin/tsconfig.json:8\nsrc/platform/test/plugin_functional/plugins/usage_collection/package.json:11\nsrc/platform/test/plugin_functional/plugins/usage_collection/package.json:12\nsrc/platform/test/plugin_functional/plugins/usage_collection/tsconfig.json:11\nsrc/platform/test/plugin_functional/plugins/usage_collection/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_a/package.json:10\nsrc/platform/test/server_integration/plugins/status_plugin_a/package.json:11\nsrc/platform/test/server_integration/plugins/status_plugin_a/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_a/tsconfig.json:9\nsrc/platform/test/server_integration/plugins/status_plugin_b/package.json:10\nsrc/platform/test/server_integration/plugins/status_plugin_b/package.json:11\nsrc/platform/test/server_integration/plugins/status_plugin_b/tsconfig.json:2\nsrc/platform/test/server_integration/plugins/status_plugin_b/tsconfig.json:9\n```\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"355a834659b74333162008d54d44be0f2a14fb6b"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-18 14:48:04 +01:00
Kibana Machine	cc35bc14b0	[8.x] [CI] Only emit .d.ts when running typecheck (#209259) (#214943) ... # Backport This will backport the following commits from `main` to `8.x`: - [[CI] Only emit .d.ts when running typecheck (#209259)](https://github.com/elastic/kibana/pull/209259) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T10:48:14Z","message":"[CI] Only emit .d.ts when running typecheck (#209259)\n\n## Summary\nStop emitting any `.js` files during typechecking. We only depend on the\ndeclarations, not the emitted, compiled javascript files.\n\nAn added benefit, is making some bad import errors more obvious. \nWe'll no longer try to build javascript files in place if a poor\nimport/require is made, rather the error of importing outside projects\n(in the forest of a bunch of errors possibly) will be visible in the\ntypescript logs:\n```\n# instead of:\nproc [tsc] error TS5055: Cannot write file '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1741789017236110254/elastic/kibana-pull-request/kibana/src/platform/packages/shared/kbn-babel-register/cache/no_cache_cache.js' because it would overwrite input file.\n\n# we'll see:\n... several others like this\n proc [tsc] src/platform/packages/shared/kbn-grok-ui/scripts/generate_patterns.js:10:9 - error TS6307: File '/Users/alex/Git/elastic-kibana/src/setup_node_env/index.js' is not listed within the file list of project '/Users/alex/Git/elastic-kibana/src/platform/packages/shared/kbn-grok-ui/tsconfig.type_check.json'. Projects must list all files or use an 'include' pattern.\n proc [tsc] \n proc [tsc] 10 require('../../../../../setup_node_env');\n... several others like this\n```","sha":"702c9c49dcbc9036af80ba5473c961cf96573030","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v9.1.0"],"title":"[CI] Only emit .d.ts when running typecheck","number":209259,"url":"https://github.com/elastic/kibana/pull/209259","mergeCommit":{"message":"[CI] Only emit .d.ts when running typecheck (#209259)\n\n## Summary\nStop emitting any `.js` files during typechecking. We only depend on the\ndeclarations, not the emitted, compiled javascript files.\n\nAn added benefit, is making some bad import errors more obvious. \nWe'll no longer try to build javascript files in place if a poor\nimport/require is made, rather the error of importing outside projects\n(in the forest of a bunch of errors possibly) will be visible in the\ntypescript logs:\n```\n# instead of:\nproc [tsc] error TS5055: Cannot write file '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1741789017236110254/elastic/kibana-pull-request/kibana/src/platform/packages/shared/kbn-babel-register/cache/no_cache_cache.js' because it would overwrite input file.\n\n# we'll see:\n... several others like this\n proc [tsc] src/platform/packages/shared/kbn-grok-ui/scripts/generate_patterns.js:10:9 - error TS6307: File '/Users/alex/Git/elastic-kibana/src/setup_node_env/index.js' is not listed within the file list of project '/Users/alex/Git/elastic-kibana/src/platform/packages/shared/kbn-grok-ui/tsconfig.type_check.json'. Projects must list all files or use an 'include' pattern.\n proc [tsc] \n proc [tsc] 10 require('../../../../../setup_node_env');\n... several others like this\n```","sha":"702c9c49dcbc9036af80ba5473c961cf96573030"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209259","number":209259,"mergeCommit":{"message":"[CI] Only emit .d.ts when running typecheck (#209259)\n\n## Summary\nStop emitting any `.js` files during typechecking. We only depend on the\ndeclarations, not the emitted, compiled javascript files.\n\nAn added benefit, is making some bad import errors more obvious. \nWe'll no longer try to build javascript files in place if a poor\nimport/require is made, rather the error of importing outside projects\n(in the forest of a bunch of errors possibly) will be visible in the\ntypescript logs:\n```\n# instead of:\nproc [tsc] error TS5055: Cannot write file '/opt/buildkite-agent/builds/bk-agent-prod-gcp-1741789017236110254/elastic/kibana-pull-request/kibana/src/platform/packages/shared/kbn-babel-register/cache/no_cache_cache.js' because it would overwrite input file.\n\n# we'll see:\n... several others like this\n proc [tsc] src/platform/packages/shared/kbn-grok-ui/scripts/generate_patterns.js:10:9 - error TS6307: File '/Users/alex/Git/elastic-kibana/src/setup_node_env/index.js' is not listed within the file list of project '/Users/alex/Git/elastic-kibana/src/platform/packages/shared/kbn-grok-ui/tsconfig.type_check.json'. Projects must list all files or use an 'include' pattern.\n proc [tsc] \n proc [tsc] 10 require('../../../../../setup_node_env');\n... several others like this\n```","sha":"702c9c49dcbc9036af80ba5473c961cf96573030"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co>	2025-03-18 15:05:07 +02:00
Davis McPhee	6d2411ffdc	[8.x] [Discover] Optimize Discover plugin page load bundle (#208298) (#214867) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Discover] Optimize Discover plugin page load bundle (#208298)](https://github.com/elastic/kibana/pull/208298) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-03-11T20:30:25Z","message":"[Discover] Optimize Discover plugin page load bundle (#208298)\n\n## Summary\n\nThis PR optimizes the Discover page load bundle by reducing it to only\ncode which is actually required on startup, and dynamically loading\nother code when it's needed, resulting in a 55% decrease in the bundle\nsize.\n\nBefore (44.15 KB):\n\n\n\nAfter (20.12 KB):\n\n\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e1bffa6a9b6a82e347b1c1f4dbfaa7571fff546b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:skip","backport missing","Team:DataDiscovery","backport:version","v9.1.0","v8.19.0"],"title":"[Discover] Optimize Discover plugin page load bundle","number":208298,"url":"https://github.com/elastic/kibana/pull/208298","mergeCommit":{"message":"[Discover] Optimize Discover plugin page load bundle (#208298)\n\n## Summary\n\nThis PR optimizes the Discover page load bundle by reducing it to only\ncode which is actually required on startup, and dynamically loading\nother code when it's needed, resulting in a 55% decrease in the bundle\nsize.\n\nBefore (44.15 KB):\n\n\n\nAfter (20.12 KB):\n\n\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e1bffa6a9b6a82e347b1c1f4dbfaa7571fff546b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208298","number":208298,"mergeCommit":{"message":"[Discover] Optimize Discover plugin page load bundle (#208298)\n\n## Summary\n\nThis PR optimizes the Discover page load bundle by reducing it to only\ncode which is actually required on startup, and dynamically loading\nother code when it's needed, resulting in a 55% decrease in the bundle\nsize.\n\nBefore (44.15 KB):\n\n\n\nAfter (20.12 KB):\n\n\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e1bffa6a9b6a82e347b1c1f4dbfaa7571fff546b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-18 13:42:08 +01:00
Nathan Reese	26506ae73d	[8.x] move static presentationUtil code into package @kbn/expression-utils (#213659) (#214015) ... # Backport This will backport the following commits from `main` to `8.x`: - [move static presentationUtil code into package @kbn/expression-utils (#213659)](https://github.com/elastic/kibana/pull/213659) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-03-11T20:24:00Z","message":"move static presentationUtil code into package @kbn/expression-utils (#213659)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"99d84003281ccfba9273b7eae7d2fc4bda3fa01d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","technical debt","release_note:skip","backport:version","v9.1.0","v8.19.0"],"title":"move static presentationUtil code into package @kbn/expression-utils","number":213659,"url":"https://github.com/elastic/kibana/pull/213659","mergeCommit":{"message":"move static presentationUtil code into package @kbn/expression-utils (#213659)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"99d84003281ccfba9273b7eae7d2fc4bda3fa01d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213659","number":213659,"mergeCommit":{"message":"move static presentationUtil code into package @kbn/expression-utils (#213659)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"99d84003281ccfba9273b7eae7d2fc4bda3fa01d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-12 09:25:56 +01:00
Shahzad	9b4b56824d	[8.x] [Synthetics] Fix overview error popover !! (#211431) (#213328) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Synthetics] Fix overview error popover !! (#211431)](https://github.com/elastic/kibana/pull/211431) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-02-21T16:38:54Z","message":"[Synthetics] Fix overview error popover !! (#211431)\n\n## Summary\n\nFix overview error popover !!\n\nPings aren't being returned as part of overview data anymore, so had to\nadd redux actions to fetch it separately via an existing API\n\nFixes https://github.com/elastic/kibana/issues/211745\n\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2244948f-e42d-443d-b6e7-42e0a72b1bfa\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Justin Kambic <jk@elastic.co>","sha":"aaf73ff5f67a9163773ff43868f329e3b5693242","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Synthetics] Fix overview error popover !!","number":211431,"url":"https://github.com/elastic/kibana/pull/211431","mergeCommit":{"message":"[Synthetics] Fix overview error popover !! (#211431)\n\n## Summary\n\nFix overview error popover !!\n\nPings aren't being returned as part of overview data anymore, so had to\nadd redux actions to fetch it separately via an existing API\n\nFixes https://github.com/elastic/kibana/issues/211745\n\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2244948f-e42d-443d-b6e7-42e0a72b1bfa\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Justin Kambic <jk@elastic.co>","sha":"aaf73ff5f67a9163773ff43868f329e3b5693242"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212123","number":212123,"state":"MERGED","mergeCommit":{"sha":"83e37babbff8e702c51c2746c790930510f4ccb4","message":"[9.0] [Synthetics] Fix overview error popover !! (#211431) (#212123)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Synthetics] Fix overview error popover !!\n(#211431)](https://github.com/elastic/kibana/pull/211431)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212620","number":212620,"state":"MERGED","mergeCommit":{"sha":"8dd76bedd8ede4bbd28e4037fe3a584507142e2d","message":"[8.18] [Synthetics] Fix overview error popover !! (#211431) (#212620)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Synthetics] Fix overview error popover !!\n(#211431)](https://github.com/elastic/kibana/pull/211431)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211431","number":211431,"mergeCommit":{"message":"[Synthetics] Fix overview error popover !! (#211431)\n\n## Summary\n\nFix overview error popover !!\n\nPings aren't being returned as part of overview data anymore, so had to\nadd redux actions to fetch it separately via an existing API\n\nFixes https://github.com/elastic/kibana/issues/211745\n\n\n<img width=\"1728\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/2244948f-e42d-443d-b6e7-42e0a72b1bfa\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Justin Kambic <jk@elastic.co>","sha":"aaf73ff5f67a9163773ff43868f329e3b5693242"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-03-06 13:01:22 +01:00
Marco Liberati	d7aa703a75	[8.x] [Lens][Embeddable] Make UI react faster to click actions like create or edit (#210810) (#212052) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Lens][Embeddable] Make UI react faster to click actions like create or edit (#210810)](https://github.com/elastic/kibana/pull/210810) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-20T17:19:46Z","message":"[Lens][Embeddable] Make UI react faster to click actions like create or edit (#210810)\n\n## Summary\n\nThis PR is based on the idea in #209361 and tries to improve perceived\nperformances for all the scenarios where the `editorFrame` is loaded.\n\nOn fast connections this is now perceived very fast:\n\n\n\nOn Fast 4g is still fast\n\n\n\nOn Slow 4g is acceptable\n\n\n\n\nEven on 3G connection the feedback is much better now\n\n\n\n\nAs a bonus extra tests have been added for the ES|QL creation flow.\n\ncc @thomasneirynck @nreese \n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Nick Partridge <nick.ryan.partridge@gmail.com>","sha":"1e92ae8afbec96f437040a7d3147b20e52478833","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Visualizations","release_note:skip","Feature:Lens","backport:version","v9.1.0","v8.19.0"],"title":"[Lens][Embeddable] Make UI react faster to click actions like create or edit","number":210810,"url":"https://github.com/elastic/kibana/pull/210810","mergeCommit":{"message":"[Lens][Embeddable] Make UI react faster to click actions like create or edit (#210810)\n\n## Summary\n\nThis PR is based on the idea in #209361 and tries to improve perceived\nperformances for all the scenarios where the `editorFrame` is loaded.\n\nOn fast connections this is now perceived very fast:\n\n\n\nOn Fast 4g is still fast\n\n\n\nOn Slow 4g is acceptable\n\n\n\n\nEven on 3G connection the feedback is much better now\n\n\n\n\nAs a bonus extra tests have been added for the ES|QL creation flow.\n\ncc @thomasneirynck @nreese \n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Nick Partridge <nick.ryan.partridge@gmail.com>","sha":"1e92ae8afbec96f437040a7d3147b20e52478833"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210810","number":210810,"mergeCommit":{"message":"[Lens][Embeddable] Make UI react faster to click actions like create or edit (#210810)\n\n## Summary\n\nThis PR is based on the idea in #209361 and tries to improve perceived\nperformances for all the scenarios where the `editorFrame` is loaded.\n\nOn fast connections this is now perceived very fast:\n\n\n\nOn Fast 4g is still fast\n\n\n\nOn Slow 4g is acceptable\n\n\n\n\nEven on 3G connection the feedback is much better now\n\n\n\n\nAs a bonus extra tests have been added for the ES|QL creation flow.\n\ncc @thomasneirynck @nreese \n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Nick Partridge <nick.ryan.partridge@gmail.com>","sha":"1e92ae8afbec96f437040a7d3147b20e52478833"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-03-03 12:14:06 +01:00
Gerard Soldevila	5acb5506ac	[8.x] SKA: Relocate "platform" packages that remain on /packages (#208704) (#212474) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Relocate "platform" packages that remain on `/packages` (#208704)](https://github.com/elastic/kibana/pull/208704) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-24T11:03:30Z","message":"SKA: Relocate \"platform\" packages that remain on `/packages` (#208704)\n\n## Summary\n\nThe `/packages` folder at the root of the Kibana repository used to\ncontain a lot of packages.\nIn the context of SKA, they have been gradually moved to various\nlocations:\n* `src/platform/packages`\n* `x-pack/platform/packages`\n* `src/core/packages`\n\nCurrently, only `devOnly: true` packages are left in this folder. This\ncomprises libraries for CLI scripts as well as testing utilities.\n\nWith this PR, we are moving ~half of these packages under\n`src/platform/packages/(private|shared)/`.\nIn particular, we are moving those packages that are being used from\nplatform and/or solutions.\n\nSince they are `\"devOnly\": true`, this means they are ONLY used from\ntests, cypress tests, storybook configs, ./scripts/ folders inside some\nmodules, or other non-prod-time logic. Nonetheless, they are effectively\nreferenced from platform and/or solutions code, hence I decided they\nshould be placed under `platform` folders.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6a7c904f921434fe21dfa00eceabfb5e64e915dc","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Relocate \"platform\" packages that remain on `/packages`","number":208704,"url":"https://github.com/elastic/kibana/pull/208704","mergeCommit":{"message":"SKA: Relocate \"platform\" packages that remain on `/packages` (#208704)\n\n## Summary\n\nThe `/packages` folder at the root of the Kibana repository used to\ncontain a lot of packages.\nIn the context of SKA, they have been gradually moved to various\nlocations:\n* `src/platform/packages`\n* `x-pack/platform/packages`\n* `src/core/packages`\n\nCurrently, only `devOnly: true` packages are left in this folder. This\ncomprises libraries for CLI scripts as well as testing utilities.\n\nWith this PR, we are moving ~half of these packages under\n`src/platform/packages/(private|shared)/`.\nIn particular, we are moving those packages that are being used from\nplatform and/or solutions.\n\nSince they are `\"devOnly\": true`, this means they are ONLY used from\ntests, cypress tests, storybook configs, ./scripts/ folders inside some\nmodules, or other non-prod-time logic. Nonetheless, they are effectively\nreferenced from platform and/or solutions code, hence I decided they\nshould be placed under `platform` folders.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6a7c904f921434fe21dfa00eceabfb5e64e915dc"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212224","number":212224,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208704","number":208704,"mergeCommit":{"message":"SKA: Relocate \"platform\" packages that remain on `/packages` (#208704)\n\n## Summary\n\nThe `/packages` folder at the root of the Kibana repository used to\ncontain a lot of packages.\nIn the context of SKA, they have been gradually moved to various\nlocations:\n* `src/platform/packages`\n* `x-pack/platform/packages`\n* `src/core/packages`\n\nCurrently, only `devOnly: true` packages are left in this folder. This\ncomprises libraries for CLI scripts as well as testing utilities.\n\nWith this PR, we are moving ~half of these packages under\n`src/platform/packages/(private|shared)/`.\nIn particular, we are moving those packages that are being used from\nplatform and/or solutions.\n\nSince they are `\"devOnly\": true`, this means they are ONLY used from\ntests, cypress tests, storybook configs, ./scripts/ folders inside some\nmodules, or other non-prod-time logic. Nonetheless, they are effectively\nreferenced from platform and/or solutions code, hence I decided they\nshould be placed under `platform` folders.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"6a7c904f921434fe21dfa00eceabfb5e64e915dc"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-28 10:12:01 +00:00
Gerard Soldevila	221205c0ee	[8.x] SKA: Misc cleanup and enhancements (#212207) (#212351) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Misc cleanup and enhancements (#212207)](https://github.com/elastic/kibana/pull/212207) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-24T13:31:00Z","message":"SKA: Misc cleanup and enhancements (#212207)\n\n## Summary\n\n* Remove some old paths pointing to `packages/kbn-pm` (no longer\nexists).\n* ~Fix group and visibility for `@kbn/streams-app-wrapper-plugin`~.\n(done in https://github.com/elastic/kibana/pull/212210)\n* Update `scripts/relocate` logic with latest enhancements.\n* Convert `@kbn/observability-synthetics-test-data` folder name to\ncamel-case (messes up with pre-commit hook).","sha":"a41badf96496c81587fca3d56c1c891abeb1a3a9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Misc cleanup and enhancements","number":212207,"url":"https://github.com/elastic/kibana/pull/212207","mergeCommit":{"message":"SKA: Misc cleanup and enhancements (#212207)\n\n## Summary\n\n* Remove some old paths pointing to `packages/kbn-pm` (no longer\nexists).\n* ~Fix group and visibility for `@kbn/streams-app-wrapper-plugin`~.\n(done in https://github.com/elastic/kibana/pull/212210)\n* Update `scripts/relocate` logic with latest enhancements.\n* Convert `@kbn/observability-synthetics-test-data` folder name to\ncamel-case (messes up with pre-commit hook).","sha":"a41badf96496c81587fca3d56c1c891abeb1a3a9"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212207","number":212207,"mergeCommit":{"message":"SKA: Misc cleanup and enhancements (#212207)\n\n## Summary\n\n* Remove some old paths pointing to `packages/kbn-pm` (no longer\nexists).\n* ~Fix group and visibility for `@kbn/streams-app-wrapper-plugin`~.\n(done in https://github.com/elastic/kibana/pull/212210)\n* Update `scripts/relocate` logic with latest enhancements.\n* Convert `@kbn/observability-synthetics-test-data` folder name to\ncamel-case (messes up with pre-commit hook).","sha":"a41badf96496c81587fca3d56c1c891abeb1a3a9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-25 12:57:23 +00:00
Joe Reuter	dd7020e994	[8.x] 🌊 Move streams to platform (#212113) ... # Backport This will backport the following commits from `main` to `8.x`: - 🌊 Move streams to platform (#211893)](https://github.com/elastic/kibana/pull/211893) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-24 10:14:05 +00:00
Kibana Machine	c6da5a53a5	[8.x] [scout] disable reporter for config validation command (#212072) (#212108) ... # Backport This will backport the following commits from `main` to `8.x`: - [[scout] disable reporter for config validation command (#212072)](https://github.com/elastic/kibana/pull/212072) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-21T15:42:32Z","message":"[scout] disable reporter for config validation command (#212072)\n\n## Summary\n\nIn #211918 I added config validation check to skip run if there are no\ntests in playwright config.\n\nIt turned out that Playwright init reporters even when `--list` command\nis passed and no tests are executed, that lead to Scout reports being\nloaded and then causing reporter error when the other command runs the\ntests:\n\n```\n proc [playwright] info Calling save with destination: /Users/dmle/github/kibana/.scout/reports/scout-playwright-9518363d47816953\n proc [playwright] ERROR Error: Save destination path '/Users/dmle/github/kibana/.scout/reports/scout-playwright-9518363d47816953' already exists\n proc [playwright] at ScoutEventsReport.save (/Users/dmle/github/kibana/packages/kbn-scout-reporting/src/reporting/report/events/report.ts:56:13)\n proc [playwright] at ScoutPlaywrightReporter.onEnd (/Users/dmle/github/kibana/packages/kbn-scout-reporting/src/reporting/playwright/events/playwright_reporter.ts:277:19)\n proc [playwright] at ReporterV2Wrapper.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/reporterV2.js:91:165)\n proc [playwright] at /Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:71:117\n proc [playwright] at wrapAsync (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:112:18)\n proc [playwright] at Multiplexer.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:69:31)\n proc [playwright] at InternalReporter.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/internalReporter.js:77:12)\n proc [playwright] at finishTaskRun (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/tasks.js:90:26)\n proc [playwright] at runTasks (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/tasks.js:73:10)\n proc [playwright] at Runner.runAllTests (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/runner.js:72:20)\n proc [playwright] at runTests (/Users/dmle/github/kibana/node_modules/playwright/lib/program.js:211:18)\n proc [playwright] at t.<anonymous> (/Users/dmle/github/kibana/node_modules/playwright/lib/program.js:54:7)\n```\n\nThe simplest solution is to explicitly disable Scout reporter for config\nvalidation command.","sha":"f5a1ead8cf053168cd94fdc45facaca8f2dbc35a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] disable reporter for config validation command","number":212072,"url":"https://github.com/elastic/kibana/pull/212072","mergeCommit":{"message":"[scout] disable reporter for config validation command (#212072)\n\n## Summary\n\nIn #211918 I added config validation check to skip run if there are no\ntests in playwright config.\n\nIt turned out that Playwright init reporters even when `--list` command\nis passed and no tests are executed, that lead to Scout reports being\nloaded and then causing reporter error when the other command runs the\ntests:\n\n```\n proc [playwright] info Calling save with destination: /Users/dmle/github/kibana/.scout/reports/scout-playwright-9518363d47816953\n proc [playwright] ERROR Error: Save destination path '/Users/dmle/github/kibana/.scout/reports/scout-playwright-9518363d47816953' already exists\n proc [playwright] at ScoutEventsReport.save (/Users/dmle/github/kibana/packages/kbn-scout-reporting/src/reporting/report/events/report.ts:56:13)\n proc [playwright] at ScoutPlaywrightReporter.onEnd (/Users/dmle/github/kibana/packages/kbn-scout-reporting/src/reporting/playwright/events/playwright_reporter.ts:277:19)\n proc [playwright] at ReporterV2Wrapper.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/reporterV2.js:91:165)\n proc [playwright] at /Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:71:117\n proc [playwright] at wrapAsync (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:112:18)\n proc [playwright] at Multiplexer.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:69:31)\n proc [playwright] at InternalReporter.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/internalReporter.js:77:12)\n proc [playwright] at finishTaskRun (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/tasks.js:90:26)\n proc [playwright] at runTasks (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/tasks.js:73:10)\n proc [playwright] at Runner.runAllTests (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/runner.js:72:20)\n proc [playwright] at runTests (/Users/dmle/github/kibana/node_modules/playwright/lib/program.js:211:18)\n proc [playwright] at t.<anonymous> (/Users/dmle/github/kibana/node_modules/playwright/lib/program.js:54:7)\n```\n\nThe simplest solution is to explicitly disable Scout reporter for config\nvalidation command.","sha":"f5a1ead8cf053168cd94fdc45facaca8f2dbc35a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212072","number":212072,"mergeCommit":{"message":"[scout] disable reporter for config validation command (#212072)\n\n## Summary\n\nIn #211918 I added config validation check to skip run if there are no\ntests in playwright config.\n\nIt turned out that Playwright init reporters even when `--list` command\nis passed and no tests are executed, that lead to Scout reports being\nloaded and then causing reporter error when the other command runs the\ntests:\n\n```\n proc [playwright] info Calling save with destination: /Users/dmle/github/kibana/.scout/reports/scout-playwright-9518363d47816953\n proc [playwright] ERROR Error: Save destination path '/Users/dmle/github/kibana/.scout/reports/scout-playwright-9518363d47816953' already exists\n proc [playwright] at ScoutEventsReport.save (/Users/dmle/github/kibana/packages/kbn-scout-reporting/src/reporting/report/events/report.ts:56:13)\n proc [playwright] at ScoutPlaywrightReporter.onEnd (/Users/dmle/github/kibana/packages/kbn-scout-reporting/src/reporting/playwright/events/playwright_reporter.ts:277:19)\n proc [playwright] at ReporterV2Wrapper.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/reporterV2.js:91:165)\n proc [playwright] at /Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:71:117\n proc [playwright] at wrapAsync (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:112:18)\n proc [playwright] at Multiplexer.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/multiplexer.js:69:31)\n proc [playwright] at InternalReporter.onEnd (/Users/dmle/github/kibana/node_modules/playwright/lib/reporters/internalReporter.js:77:12)\n proc [playwright] at finishTaskRun (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/tasks.js:90:26)\n proc [playwright] at runTasks (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/tasks.js:73:10)\n proc [playwright] at Runner.runAllTests (/Users/dmle/github/kibana/node_modules/playwright/lib/runner/runner.js:72:20)\n proc [playwright] at runTests (/Users/dmle/github/kibana/node_modules/playwright/lib/program.js:211:18)\n proc [playwright] at t.<anonymous> (/Users/dmle/github/kibana/node_modules/playwright/lib/program.js:54:7)\n```\n\nThe simplest solution is to explicitly disable Scout reporter for config\nvalidation command.","sha":"f5a1ead8cf053168cd94fdc45facaca8f2dbc35a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>	2025-02-21 18:03:54 +00:00
Kibana Machine	fe907479be	[8.x] [Synthtrace] Improve URL discovery when running locally in Serverless mode (#211670) (#212111) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Synthtrace] Improve URL discovery when running locally in Serverless mode (#211670)](https://github.com/elastic/kibana/pull/211670) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abdul Wahab Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2025-02-21T15:58:07Z","message":"[Synthtrace] Improve URL discovery when running locally in Serverless mode (#211670)\n\n## Summary\n\nThis PR improves how **Synthtrace** resolves the Kibana URL when only\n`--target` (Elasticsearch) is provided or when neither `--target` nor\n`--kibana` is specified. The CLI now attempts to **automatically\ndiscover** the appropriate URLs based on the provided arguments.\n\nSome adjustments were made to improve this discovery process, especially\nwhen running **locally in Serverless mode**, where Kibana may be using\n`http`, while Elasticsearch (ES) is on `https`. Additionally,\nself-signed certificates do not work with the IP address `127.0.0.1`, so\nthis PR defaults to `localhost` and warns the user if `127.0.0.1` is\ndetected in Serverless mode.\n\n### **Improvements**\n- If either of `--target` or `--kibana` or neither provided, the CLI\nattempts to **discovers the URLs** dynamically now in both Stateful and\nServerless.\n- Defaults to `localhost` instead of `127.0.0.1` to avoid SSL\ncertificate issues.\n- Provides a **clear error message and hint** when Kibana and ES use\ndifferent protocols (http vs https) and either or both are unreachable.\n\n### **Expected Behavior After This PR**\nThese commands should now work **seamlessly** in both **local Stateful**\nand **Serverless** modes:\n\n```sh\n✗ node scripts/synthtrace simple_logs\n```\n\nFor **Serverless mode**, these also work:\n\n```sh\n✗ node scripts/synthtrace simple_logs --kibana=http://elastic_serverless:changeme@localhost:5601\n```\n\n```sh\n✗ node scripts/synthtrace simple_logs --target=https://elastic_serverless:changeme@localhost:9200 --kibana=http://elastic_serverless:changeme@localhost:5601\n```\n\n### **(Side Note) Serverless Kibana with SSL Disabled**\nHowever, the following command will **fail** with an error message if\nKibana is running without SSL, while Elasticsearch is using `https`:\n\n```sh\n✗ node scripts/synthtrace simple_logs --target=https://elastic_serverless:changeme@localhost:9200\n```\n\n#### **Error Output:**\n```sh\nLoading scenario from kibana/packages/kbn-apm-synthtrace/src/scenarios/simple_logs.ts\nError: Could not connect to Kibana. request to https://elastic_serverless:changeme@localhost:5601/ failed, reason: write EPROTO 400882F501000000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:355:\n\nIf your Kibana URL differs, consider using the '--kibana' parameter to customize it.\n```\n\n**Solution:** \nIf you must have to provide `--target` (non defaults), also provide\n`--kibana` or start Kibana with SSL enabled.\n```sh\n✗ yarn start --serverless=oblt --ssl\n```","sha":"cb71dff86e042a088aa13cc11f90b0673438b365","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0"],"title":"[Synthtrace] Improve URL discovery when running locally in Serverless mode","number":211670,"url":"https://github.com/elastic/kibana/pull/211670","mergeCommit":{"message":"[Synthtrace] Improve URL discovery when running locally in Serverless mode (#211670)\n\n## Summary\n\nThis PR improves how **Synthtrace** resolves the Kibana URL when only\n`--target` (Elasticsearch) is provided or when neither `--target` nor\n`--kibana` is specified. The CLI now attempts to **automatically\ndiscover** the appropriate URLs based on the provided arguments.\n\nSome adjustments were made to improve this discovery process, especially\nwhen running **locally in Serverless mode**, where Kibana may be using\n`http`, while Elasticsearch (ES) is on `https`. Additionally,\nself-signed certificates do not work with the IP address `127.0.0.1`, so\nthis PR defaults to `localhost` and warns the user if `127.0.0.1` is\ndetected in Serverless mode.\n\n### **Improvements**\n- If either of `--target` or `--kibana` or neither provided, the CLI\nattempts to **discovers the URLs** dynamically now in both Stateful and\nServerless.\n- Defaults to `localhost` instead of `127.0.0.1` to avoid SSL\ncertificate issues.\n- Provides a **clear error message and hint** when Kibana and ES use\ndifferent protocols (http vs https) and either or both are unreachable.\n\n### **Expected Behavior After This PR**\nThese commands should now work **seamlessly** in both **local Stateful**\nand **Serverless** modes:\n\n```sh\n✗ node scripts/synthtrace simple_logs\n```\n\nFor **Serverless mode**, these also work:\n\n```sh\n✗ node scripts/synthtrace simple_logs --kibana=http://elastic_serverless:changeme@localhost:5601\n```\n\n```sh\n✗ node scripts/synthtrace simple_logs --target=https://elastic_serverless:changeme@localhost:9200 --kibana=http://elastic_serverless:changeme@localhost:5601\n```\n\n### **(Side Note) Serverless Kibana with SSL Disabled**\nHowever, the following command will **fail** with an error message if\nKibana is running without SSL, while Elasticsearch is using `https`:\n\n```sh\n✗ node scripts/synthtrace simple_logs --target=https://elastic_serverless:changeme@localhost:9200\n```\n\n#### **Error Output:**\n```sh\nLoading scenario from kibana/packages/kbn-apm-synthtrace/src/scenarios/simple_logs.ts\nError: Could not connect to Kibana. request to https://elastic_serverless:changeme@localhost:5601/ failed, reason: write EPROTO 400882F501000000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:355:\n\nIf your Kibana URL differs, consider using the '--kibana' parameter to customize it.\n```\n\n**Solution:** \nIf you must have to provide `--target` (non defaults), also provide\n`--kibana` or start Kibana with SSL enabled.\n```sh\n✗ yarn start --serverless=oblt --ssl\n```","sha":"cb71dff86e042a088aa13cc11f90b0673438b365"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211670","number":211670,"mergeCommit":{"message":"[Synthtrace] Improve URL discovery when running locally in Serverless mode (#211670)\n\n## Summary\n\nThis PR improves how **Synthtrace** resolves the Kibana URL when only\n`--target` (Elasticsearch) is provided or when neither `--target` nor\n`--kibana` is specified. The CLI now attempts to **automatically\ndiscover** the appropriate URLs based on the provided arguments.\n\nSome adjustments were made to improve this discovery process, especially\nwhen running **locally in Serverless mode**, where Kibana may be using\n`http`, while Elasticsearch (ES) is on `https`. Additionally,\nself-signed certificates do not work with the IP address `127.0.0.1`, so\nthis PR defaults to `localhost` and warns the user if `127.0.0.1` is\ndetected in Serverless mode.\n\n### **Improvements**\n- If either of `--target` or `--kibana` or neither provided, the CLI\nattempts to **discovers the URLs** dynamically now in both Stateful and\nServerless.\n- Defaults to `localhost` instead of `127.0.0.1` to avoid SSL\ncertificate issues.\n- Provides a **clear error message and hint** when Kibana and ES use\ndifferent protocols (http vs https) and either or both are unreachable.\n\n### **Expected Behavior After This PR**\nThese commands should now work **seamlessly** in both **local Stateful**\nand **Serverless** modes:\n\n```sh\n✗ node scripts/synthtrace simple_logs\n```\n\nFor **Serverless mode**, these also work:\n\n```sh\n✗ node scripts/synthtrace simple_logs --kibana=http://elastic_serverless:changeme@localhost:5601\n```\n\n```sh\n✗ node scripts/synthtrace simple_logs --target=https://elastic_serverless:changeme@localhost:9200 --kibana=http://elastic_serverless:changeme@localhost:5601\n```\n\n### **(Side Note) Serverless Kibana with SSL Disabled**\nHowever, the following command will **fail** with an error message if\nKibana is running without SSL, while Elasticsearch is using `https`:\n\n```sh\n✗ node scripts/synthtrace simple_logs --target=https://elastic_serverless:changeme@localhost:9200\n```\n\n#### **Error Output:**\n```sh\nLoading scenario from kibana/packages/kbn-apm-synthtrace/src/scenarios/simple_logs.ts\nError: Could not connect to Kibana. request to https://elastic_serverless:changeme@localhost:5601/ failed, reason: write EPROTO 400882F501000000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:355:\n\nIf your Kibana URL differs, consider using the '--kibana' parameter to customize it.\n```\n\n**Solution:** \nIf you must have to provide `--target` (non defaults), also provide\n`--kibana` or start Kibana with SSL enabled.\n```sh\n✗ yarn start --serverless=oblt --ssl\n```","sha":"cb71dff86e042a088aa13cc11f90b0673438b365"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com>	2025-02-21 17:50:16 +00:00
Kibana Machine	4e819674bf	[8.x] [scout] Don't mix await with promise callbacks (#211905) (#211915) ... # Backport This will backport the following commits from `main` to `8.x`: - [[scout] Don't mix `await` with promise callbacks (#211905)](https://github.com/elastic/kibana/pull/211905) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Olaru","email":"dolaru@elastic.co"},"sourceCommit":{"committedDate":"2025-02-20T15:05:17Z","message":"[scout] Don't mix `await` with promise callbacks (#211905)\n\n## Summary\n\nThere's a high likelihood that this causes some unwanted behavior where\nthe promise is not resolved and the `node` process just exists without\nany error.","sha":"1147bb65dd655d9dac42f866c61eb23af42d2d74","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[scout] Don't mix `await` with promise callbacks","number":211905,"url":"https://github.com/elastic/kibana/pull/211905","mergeCommit":{"message":"[scout] Don't mix `await` with promise callbacks (#211905)\n\n## Summary\n\nThere's a high likelihood that this causes some unwanted behavior where\nthe promise is not resolved and the `node` process just exists without\nany error.","sha":"1147bb65dd655d9dac42f866c61eb23af42d2d74"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211905","number":211905,"mergeCommit":{"message":"[scout] Don't mix `await` with promise callbacks (#211905)\n\n## Summary\n\nThere's a high likelihood that this causes some unwanted behavior where\nthe promise is not resolved and the `node` process just exists without\nany error.","sha":"1147bb65dd655d9dac42f866c61eb23af42d2d74"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: David Olaru <dolaru@elastic.co>	2025-02-21 10:26:14 +01:00
Kibana Machine	26841d07f0	[8.x] [scout] validate config has tests before starting servers (#211918) (#211940) ... # Backport This will backport the following commits from `main` to `8.x`: - [[scout] validate config has tests before starting servers (#211918)](https://github.com/elastic/kibana/pull/211918) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-20T17:20:21Z","message":"[scout] validate config has tests before starting servers (#211918)\n\n## Summary\n\nThere is no need to start servers (~1.5 min run time) if there are no\ntests matching filters or maybe config itself has all tests skipped.\n\nThis PR uses Playwright cli with `--list` flag to quickly validate\nplaywright config and exit with status code `2` (`1` is reserved for\nerrors during servers start or test failures). it also useful to know in\nadvance how many tests were about to run:\n\ncase 1: tests found\n\n```\n$ node scripts/scout.js run-tests --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts --serverless=security\n info scout: Test server configuration saved at /Users/dmle/github/kibana/.scout/servers/local.json\n info scout: Validate Playwright config has tests\n info scout: Total: 5 tests in 2 files\n info Verifying Docker is installed.\n │ info Docker version 20.10.14, build a224086349\n...\n```\n\ncase 2: no tests found\n```\n$ node scripts/scout.js run-tests --config x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts --stateful\n info scout: Test server configuration saved at /Users/dmle/github/kibana/.scout/servers/local.json\n info scout: Validate Playwright config has tests\nERROR scout: No tests found in [x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts]\n```","sha":"30c4275462bfb975f4eb86d45fc608971ebfcfbc","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:QA","release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] validate config has tests before starting servers","number":211918,"url":"https://github.com/elastic/kibana/pull/211918","mergeCommit":{"message":"[scout] validate config has tests before starting servers (#211918)\n\n## Summary\n\nThere is no need to start servers (~1.5 min run time) if there are no\ntests matching filters or maybe config itself has all tests skipped.\n\nThis PR uses Playwright cli with `--list` flag to quickly validate\nplaywright config and exit with status code `2` (`1` is reserved for\nerrors during servers start or test failures). it also useful to know in\nadvance how many tests were about to run:\n\ncase 1: tests found\n\n```\n$ node scripts/scout.js run-tests --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts --serverless=security\n info scout: Test server configuration saved at /Users/dmle/github/kibana/.scout/servers/local.json\n info scout: Validate Playwright config has tests\n info scout: Total: 5 tests in 2 files\n info Verifying Docker is installed.\n │ info Docker version 20.10.14, build a224086349\n...\n```\n\ncase 2: no tests found\n```\n$ node scripts/scout.js run-tests --config x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts --stateful\n info scout: Test server configuration saved at /Users/dmle/github/kibana/.scout/servers/local.json\n info scout: Validate Playwright config has tests\nERROR scout: No tests found in [x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts]\n```","sha":"30c4275462bfb975f4eb86d45fc608971ebfcfbc"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211918","number":211918,"mergeCommit":{"message":"[scout] validate config has tests before starting servers (#211918)\n\n## Summary\n\nThere is no need to start servers (~1.5 min run time) if there are no\ntests matching filters or maybe config itself has all tests skipped.\n\nThis PR uses Playwright cli with `--list` flag to quickly validate\nplaywright config and exit with status code `2` (`1` is reserved for\nerrors during servers start or test failures). it also useful to know in\nadvance how many tests were about to run:\n\ncase 1: tests found\n\n```\n$ node scripts/scout.js run-tests --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts --serverless=security\n info scout: Test server configuration saved at /Users/dmle/github/kibana/.scout/servers/local.json\n info scout: Validate Playwright config has tests\n info scout: Total: 5 tests in 2 files\n info Verifying Docker is installed.\n │ info Docker version 20.10.14, build a224086349\n...\n```\n\ncase 2: no tests found\n```\n$ node scripts/scout.js run-tests --config x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts --stateful\n info scout: Test server configuration saved at /Users/dmle/github/kibana/.scout/servers/local.json\n info scout: Validate Playwright config has tests\nERROR scout: No tests found in [x-pack/solutions/observability/plugins/observability_onboarding/ui_tests/playwright.config.ts]\n```","sha":"30c4275462bfb975f4eb86d45fc608971ebfcfbc"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>	2025-02-20 20:37:37 +01:00
Gerard Soldevila	23c60bec1d	[8.x] SKA: Fix kebab-case issues in security-threat-hunting packages (#211349) (#211732) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)](https://github.com/elastic/kibana/pull/211349) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T10:21:45Z","message":"SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/securitysolution-data-table` |\r\n`x-pack/solutions/security/packages/data-table` |\r\n| `@kbn/ecs-data-quality-dashboard` |\r\n`x-pack/solutions/security/packages/ecs-data-quality-dashboard` |\r\n| `@kbn/security-solution-side-nav` |\r\n`x-pack/solutions/security/packages/side-nav` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.i18nrc.json\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/solutions/security/packages/data-table/jest.config.js\r\n./x-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js\r\n./x-pack/solutions/security/packages/side-nav/jest.config.js\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nx-pack/solutions/security/packages/data-table/jest.config.js:11\r\nx-pack/solutions/security/packages/data-table/tsconfig.json:2\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js:24\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:10\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:2\r\nx-pack/solutions/security/packages/side-nav/jest.config.js:10\r\nx-pack/solutions/security/packages/side-nav/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"69a87194d17a8228d1643845c306a01201e921b7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Fix kebab-case issues in security-threat-hunting packages","number":211349,"url":"https://github.com/elastic/kibana/pull/211349","mergeCommit":{"message":"SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/securitysolution-data-table` |\r\n`x-pack/solutions/security/packages/data-table` |\r\n| `@kbn/ecs-data-quality-dashboard` |\r\n`x-pack/solutions/security/packages/ecs-data-quality-dashboard` |\r\n| `@kbn/security-solution-side-nav` |\r\n`x-pack/solutions/security/packages/side-nav` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.i18nrc.json\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/solutions/security/packages/data-table/jest.config.js\r\n./x-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js\r\n./x-pack/solutions/security/packages/side-nav/jest.config.js\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nx-pack/solutions/security/packages/data-table/jest.config.js:11\r\nx-pack/solutions/security/packages/data-table/tsconfig.json:2\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js:24\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:10\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:2\r\nx-pack/solutions/security/packages/side-nav/jest.config.js:10\r\nx-pack/solutions/security/packages/side-nav/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"69a87194d17a8228d1643845c306a01201e921b7"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211722","number":211722,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211349","number":211349,"mergeCommit":{"message":"SKA: Fix kebab-case issues in security-threat-hunting packages (#211349)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/securitysolution-data-table` |\r\n`x-pack/solutions/security/packages/data-table` |\r\n| `@kbn/ecs-data-quality-dashboard` |\r\n`x-pack/solutions/security/packages/ecs-data-quality-dashboard` |\r\n| `@kbn/security-solution-side-nav` |\r\n`x-pack/solutions/security/packages/side-nav` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./.i18nrc.json\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./tsconfig.base.json\r\n./tsconfig.base.type_check.json\r\n./tsconfig.refs.json\r\n./x-pack/solutions/security/packages/data-table/jest.config.js\r\n./x-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js\r\n./x-pack/solutions/security/packages/side-nav/jest.config.js\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nx-pack/solutions/security/packages/data-table/jest.config.js:11\r\nx-pack/solutions/security/packages/data-table/tsconfig.json:2\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/jest.config.js:24\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:10\r\nx-pack/solutions/security/packages/ecs-data-quality-dashboard/tsconfig.json:2\r\nx-pack/solutions/security/packages/side-nav/jest.config.js:10\r\nx-pack/solutions/security/packages/side-nav/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"69a87194d17a8228d1643845c306a01201e921b7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-19 13:45:13 +01:00
Kibana Machine	80b2580ede	[8.x] SKA: Categorise platform devOnly packages under /packages (#211560) (#211702) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Categorise platform devOnly packages under `/packages` (#211560)](https://github.com/elastic/kibana/pull/211560) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T09:38:42Z","message":"SKA: Categorise platform devOnly packages under `/packages` (#211560)\n\n## Summary\r\n\r\nMost of the packages under `/packages` have been relocated in the\r\ncontext of _Sustainable Kibana Architecture_.\r\n\r\nThe remaining packages are `devOnly: true`, and they can be grouped as\r\nfollows:\r\n\r\n1. Packages that are ONLY used from /scripts/\r\n2. Packages that are used from platform and solutions modules (they are\r\nused from tests, cypress tests, storybook configs, ./scripts/ folders\r\ninside some modules, or other non-prod-time logic).\r\n\r\nThis PR categorises the packages in (2) as `platform/(private|shared)`\r\nto reflect that they are being used from platform and solutions modules\r\n(even though they're used from non-production code).\r\n\r\nNext, we're gonna have to decide whether we want to relocate some of\r\nthem (1, 2 or both) under a different path.","sha":"a1fde9776552bae822f380195951f34996665c12","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:version","v9.1.0","v8.19.0"],"title":"SKA: Categorise platform devOnly packages under `/packages`","number":211560,"url":"https://github.com/elastic/kibana/pull/211560","mergeCommit":{"message":"SKA: Categorise platform devOnly packages under `/packages` (#211560)\n\n## Summary\r\n\r\nMost of the packages under `/packages` have been relocated in the\r\ncontext of _Sustainable Kibana Architecture_.\r\n\r\nThe remaining packages are `devOnly: true`, and they can be grouped as\r\nfollows:\r\n\r\n1. Packages that are ONLY used from /scripts/\r\n2. Packages that are used from platform and solutions modules (they are\r\nused from tests, cypress tests, storybook configs, ./scripts/ folders\r\ninside some modules, or other non-prod-time logic).\r\n\r\nThis PR categorises the packages in (2) as `platform/(private|shared)`\r\nto reflect that they are being used from platform and solutions modules\r\n(even though they're used from non-production code).\r\n\r\nNext, we're gonna have to decide whether we want to relocate some of\r\nthem (1, 2 or both) under a different path.","sha":"a1fde9776552bae822f380195951f34996665c12"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211560","number":211560,"mergeCommit":{"message":"SKA: Categorise platform devOnly packages under `/packages` (#211560)\n\n## Summary\r\n\r\nMost of the packages under `/packages` have been relocated in the\r\ncontext of _Sustainable Kibana Architecture_.\r\n\r\nThe remaining packages are `devOnly: true`, and they can be grouped as\r\nfollows:\r\n\r\n1. Packages that are ONLY used from /scripts/\r\n2. Packages that are used from platform and solutions modules (they are\r\nused from tests, cypress tests, storybook configs, ./scripts/ folders\r\ninside some modules, or other non-prod-time logic).\r\n\r\nThis PR categorises the packages in (2) as `platform/(private|shared)`\r\nto reflect that they are being used from platform and solutions modules\r\n(even though they're used from non-production code).\r\n\r\nNext, we're gonna have to decide whether we want to relocate some of\r\nthem (1, 2 or both) under a different path.","sha":"a1fde9776552bae822f380195951f34996665c12"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>	2025-02-19 12:29:40 +01:00
Gerard Soldevila	af941d801c	[8.x] SKA: Unify serverless modules + storybook config (#211570) (#211693) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Unify `serverless` modules + storybook config (#211570)](https://github.com/elastic/kibana/pull/211570) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T08:10:35Z","message":"SKA: Unify `serverless` modules + storybook config (#211570)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `serverless` modules, that are spread across:\r\n```\r\n- packages/serverless # storybook config\r\n- src/platform/packages/private/serverless\r\n- src/platform/packages/shared/serverless\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/severless`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management @elastic/appex-sharedux WDYT?\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8f7f6a7a81dd25d529b1d87c882f49afbe7bdf99","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","v9.0.0","Team:SharedUX","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Unify `serverless` modules + storybook config","number":211570,"url":"https://github.com/elastic/kibana/pull/211570","mergeCommit":{"message":"SKA: Unify `serverless` modules + storybook config (#211570)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `serverless` modules, that are spread across:\r\n```\r\n- packages/serverless # storybook config\r\n- src/platform/packages/private/serverless\r\n- src/platform/packages/shared/serverless\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/severless`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management @elastic/appex-sharedux WDYT?\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8f7f6a7a81dd25d529b1d87c882f49afbe7bdf99"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211570","number":211570,"mergeCommit":{"message":"SKA: Unify `serverless` modules + storybook config (#211570)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `serverless` modules, that are spread across:\r\n```\r\n- packages/serverless # storybook config\r\n- src/platform/packages/private/serverless\r\n- src/platform/packages/shared/serverless\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/severless`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management @elastic/appex-sharedux WDYT?\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8f7f6a7a81dd25d529b1d87c882f49afbe7bdf99"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-19 11:41:45 +01:00
Gerard Soldevila	9022827d4b	[8.x] SKA: Unify kbn-management folders + storybook config (#211564) (#211690) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Unify &#x60;kbn-management&#x60; folders + storybook config (#211564)](https://github.com/elastic/kibana/pull/211564) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-19T08:10:22Z","message":"SKA: Unify `kbn-management` folders + storybook config (#211564)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `kbn-management` modules, that are spread across:\r\n```\r\n- packages/kbn-management (storybook config)\r\n- src/platform/packages/private/kbn-management\r\n- src/platform/packages/shared/kbn-management\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/kbn-management`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management WDYT?\r\n\r\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"b2b3fa9a84034bf6a49a38ea3b434245582c7909","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Unify `kbn-management` folders + storybook config","number":211564,"url":"https://github.com/elastic/kibana/pull/211564","mergeCommit":{"message":"SKA: Unify `kbn-management` folders + storybook config (#211564)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `kbn-management` modules, that are spread across:\r\n```\r\n- packages/kbn-management (storybook config)\r\n- src/platform/packages/private/kbn-management\r\n- src/platform/packages/shared/kbn-management\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/kbn-management`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management WDYT?\r\n\r\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"b2b3fa9a84034bf6a49a38ea3b434245582c7909"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211564","number":211564,"mergeCommit":{"message":"SKA: Unify `kbn-management` folders + storybook config (#211564)\n\n## Summary\r\n\r\nAs part of the SKA, some groups of modules have been broken-down and\r\nrelocated in different folders, negatively impacting DX. This is the\r\ncase for `kbn-management` modules, that are spread across:\r\n```\r\n- packages/kbn-management (storybook config)\r\n- src/platform/packages/private/kbn-management\r\n- src/platform/packages/shared/kbn-management\r\n```\r\n\r\nThe goal of this PR is to unify them back under\r\n`src/platform/packages/shared/kbn-management`.\r\nIn this scenario, I believe the simplification is worth the trade off.\r\n\r\nCC @elastic/kibana-management WDYT?\r\n\r\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"b2b3fa9a84034bf6a49a38ea3b434245582c7909"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-19 11:37:12 +01:00
Kibana Machine	9483db5c4b	[8.x] fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121) (#211616) ... # Backport This will backport the following commits from `main` to `8.x`: - [fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)](https://github.com/elastic/kibana/pull/211121) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Rafael Lüder","email":"rlueder@pm.me"},"sourceCommit":{"committedDate":"2025-02-18T16:37:57Z","message":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)\n\n## Summary\r\n\r\nAdds `REACT_18` to `kbn-plugin-helpers` bazel config, this fixes an\r\nissue when trying to create plugins using the automatic plugin\r\ngenerator. For context see\r\nhttps://github.com/elastic/kibana/pull/210917#issuecomment-2657805726\r\n\r\nRelated user report: [Custom Plugin\r\nError](https://discuss.elastic.co/t/custom-plugin-error/366589)\r\n\r\nBefore fix:\r\n\r\n\r\n\r\n\r\n\r\nAfter fix:\r\n\r\n\r\n\r\n\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/src/platform/packages/shared/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_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Jon <jon@elastic.co>","sha":"9a6a349a466d4c21bd8d94b7be67996c102dbd5b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","v8.18.0","v9.1.0"],"title":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config","number":211121,"url":"https://github.com/elastic/kibana/pull/211121","mergeCommit":{"message":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)\n\n## Summary\r\n\r\nAdds `REACT_18` to `kbn-plugin-helpers` bazel config, this fixes an\r\nissue when trying to create plugins using the automatic plugin\r\ngenerator. For context see\r\nhttps://github.com/elastic/kibana/pull/210917#issuecomment-2657805726\r\n\r\nRelated user report: [Custom Plugin\r\nError](https://discuss.elastic.co/t/custom-plugin-error/366589)\r\n\r\nBefore fix:\r\n\r\n\r\n\r\n\r\n\r\nAfter fix:\r\n\r\n\r\n\r\n\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/src/platform/packages/shared/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_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Jon <jon@elastic.co>","sha":"9a6a349a466d4c21bd8d94b7be67996c102dbd5b"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211121","number":211121,"mergeCommit":{"message":"fix: add REACT_18 env variable to kbn-plugin-helpers bazel config (#211121)\n\n## Summary\r\n\r\nAdds `REACT_18` to `kbn-plugin-helpers` bazel config, this fixes an\r\nissue when trying to create plugins using the automatic plugin\r\ngenerator. For context see\r\nhttps://github.com/elastic/kibana/pull/210917#issuecomment-2657805726\r\n\r\nRelated user report: [Custom Plugin\r\nError](https://discuss.elastic.co/t/custom-plugin-error/366589)\r\n\r\nBefore fix:\r\n\r\n\r\n\r\n\r\n\r\nAfter fix:\r\n\r\n\r\n\r\n\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/src/platform/packages/shared/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_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\nCo-authored-by: Jon <jon@elastic.co>","sha":"9a6a349a466d4c21bd8d94b7be67996c102dbd5b"}}]}] BACKPORT--> Co-authored-by: Rafael Lüder <rlueder@pm.me>	2025-02-18 19:33:00 +01:00
Sergi Romeu	41a2c68d38	[8.x] [APM][Otel] Add service view e2e tests using otel service (#196542) (#211571) ... # Backport This will backport the following commits from `main` to `8.x`: - [[APM][Otel] Add service view e2e tests using otel service (#196542)](https://github.com/elastic/kibana/pull/196542) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2024-10-17T11:14:54Z","message":"[APM][Otel] Add service view e2e tests using otel service (#196542)\n\nCloses #193206\r\n\r\n## Summary\r\n\r\nThis PR adds service view e2e tests using otel service. \r\n\r\nTo run the tests:\r\n- Start server\r\n`node x-pack/plugins/observability_solution/apm/scripts/test/e2e\r\n--server`\r\n- Open Cypress \r\n`node x-pack/plugins/observability_solution/apm/scripts/test/e2e\r\n--runner --open`\r\n- Select `otel_service_overview_and_transactions`","sha":"98ebd0921d4ec2a4f1ee5c076ce9888c75addd5d","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[APM][Otel] Add service view e2e tests using otel service","number":196542,"url":"https://github.com/elastic/kibana/pull/196542","mergeCommit":{"message":"[APM][Otel] Add service view e2e tests using otel service (#196542)\n\nCloses #193206\r\n\r\n## Summary\r\n\r\nThis PR adds service view e2e tests using otel service. \r\n\r\nTo run the tests:\r\n- Start server\r\n`node x-pack/plugins/observability_solution/apm/scripts/test/e2e\r\n--server`\r\n- Open Cypress \r\n`node x-pack/plugins/observability_solution/apm/scripts/test/e2e\r\n--runner --open`\r\n- Select `otel_service_overview_and_transactions`","sha":"98ebd0921d4ec2a4f1ee5c076ce9888c75addd5d"}},"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/196542","number":196542,"mergeCommit":{"message":"[APM][Otel] Add service view e2e tests using otel service (#196542)\n\nCloses #193206\r\n\r\n## Summary\r\n\r\nThis PR adds service view e2e tests using otel service. \r\n\r\nTo run the tests:\r\n- Start server\r\n`node x-pack/plugins/observability_solution/apm/scripts/test/e2e\r\n--server`\r\n- Open Cypress \r\n`node x-pack/plugins/observability_solution/apm/scripts/test/e2e\r\n--runner --open`\r\n- Select `otel_service_overview_and_transactions`","sha":"98ebd0921d4ec2a4f1ee5c076ce9888c75addd5d"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>	2025-02-18 15:30:01 +01:00
Kibana Machine	52d5725aa2	[8.x] [kbn-scout] Add Synthtrace as a fixture (#210505) (#211524) ... # Backport This will backport the following commits from `main` to `8.x`: - [[kbn-scout] Add Synthtrace as a fixture (#210505)](https://github.com/elastic/kibana/pull/210505) <!--- Backport version: 9.6.5 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T18:52:22Z","message":"[kbn-scout] Add Synthtrace as a fixture (#210505)\n\n## Summary\n\nCloses #210340\n\nThis PR adds synthtrace clients to scout as a test fixture, so you can\nuse it in your test to generate data.\n\nThe clients added were `apmSynthtraceEsClient`,\n`infraSynthtraceEsClient` and `otelSynthtraceEsClient`.\n\n## How to use them in parallel tests\n\nAs `synthtrace` ingests data into our indices, and sequential runs would\nbe the perfect way to introduce flakiness in our tests, there is a\nbetter way to ingest data, using a hook, at the setup phase with\n`globalSetup`.\nWe need to create a `global_setup.ts` file and link it into our\nplaywright config.\nThen we can use something like\n```\nasync function globalSetup(config: FullConfig) {\n const data = {\n apm: [\n opbeans({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n }),\n ],\n infra: [\n generateHosts({\n from: new Date(start).toISOString(),\n to: new Date(end).toISOString(),\n }),\n ],\n otel: [\n sendotlp({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n }),\n ],\n };\n\n return ingestSynthtraceDataHook(config, data);\n}\n```\nEach key (apm, infra, otel) accepts an array of generators.\n\n## How to use them in sequential tests\n> [!WARNING] \n> This should not be the standard behaviour, we should embrace\nparallelism and use sequential testing when there is no other way.\n\n### apmSynthtraceEsClient\n```ts\n test.before(\n async ({ apmSynthtraceEsClient }) => {\n await apmSynthtraceEsClient.index(\n opbeans({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n })\n );\n }\n );\n```\n[opbeans\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/opbeans.ts)\nused in the example.\n\n### otelSynthtraceEsClient\n```ts\n test.before(\n async ({otelSynthtraceEsClient }) => {\n await otelSynthtraceEsClient.index(\n sendotlp({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n })\n );\n }\n );\n```\n[sendotlp\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/sendotlp.ts)\nwhich will create the data.\n\n### infraSynthtraceEsClient\n```ts\n test.before(\n async ({ infraSynthtraceEsClient }) => {\n await infraSynthtraceEsClient.index(\n generateHosts({\n from: new Date(start).toISOString(),\n to: new Date(end).toISOString(),\n })\n );\n }\n );\n```\n[generateHosts\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/inventory/e2e/cypress/e2e/alert_count/generate_data.ts#L82)\nused to generate data.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e21c5d0e9175ffd1bea0ad78ffe26cb973cc489f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","apm:synthtrace","Team:obs-ux-infra_services","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[kbn-scout] Add Synthtrace as a fixture","number":210505,"url":"https://github.com/elastic/kibana/pull/210505","mergeCommit":{"message":"[kbn-scout] Add Synthtrace as a fixture (#210505)\n\n## Summary\n\nCloses #210340\n\nThis PR adds synthtrace clients to scout as a test fixture, so you can\nuse it in your test to generate data.\n\nThe clients added were `apmSynthtraceEsClient`,\n`infraSynthtraceEsClient` and `otelSynthtraceEsClient`.\n\n## How to use them in parallel tests\n\nAs `synthtrace` ingests data into our indices, and sequential runs would\nbe the perfect way to introduce flakiness in our tests, there is a\nbetter way to ingest data, using a hook, at the setup phase with\n`globalSetup`.\nWe need to create a `global_setup.ts` file and link it into our\nplaywright config.\nThen we can use something like\n```\nasync function globalSetup(config: FullConfig) {\n const data = {\n apm: [\n opbeans({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n }),\n ],\n infra: [\n generateHosts({\n from: new Date(start).toISOString(),\n to: new Date(end).toISOString(),\n }),\n ],\n otel: [\n sendotlp({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n }),\n ],\n };\n\n return ingestSynthtraceDataHook(config, data);\n}\n```\nEach key (apm, infra, otel) accepts an array of generators.\n\n## How to use them in sequential tests\n> [!WARNING] \n> This should not be the standard behaviour, we should embrace\nparallelism and use sequential testing when there is no other way.\n\n### apmSynthtraceEsClient\n```ts\n test.before(\n async ({ apmSynthtraceEsClient }) => {\n await apmSynthtraceEsClient.index(\n opbeans({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n })\n );\n }\n );\n```\n[opbeans\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/opbeans.ts)\nused in the example.\n\n### otelSynthtraceEsClient\n```ts\n test.before(\n async ({otelSynthtraceEsClient }) => {\n await otelSynthtraceEsClient.index(\n sendotlp({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n })\n );\n }\n );\n```\n[sendotlp\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/sendotlp.ts)\nwhich will create the data.\n\n### infraSynthtraceEsClient\n```ts\n test.before(\n async ({ infraSynthtraceEsClient }) => {\n await infraSynthtraceEsClient.index(\n generateHosts({\n from: new Date(start).toISOString(),\n to: new Date(end).toISOString(),\n })\n );\n }\n );\n```\n[generateHosts\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/inventory/e2e/cypress/e2e/alert_count/generate_data.ts#L82)\nused to generate data.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e21c5d0e9175ffd1bea0ad78ffe26cb973cc489f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211351","number":211351,"state":"MERGED","mergeCommit":{"sha":"5b6ff1cd6e7cd703ed66337ee743a08abf0fa7a8","message":"[9.0] [kbn-scout] Add Synthtrace as a fixture (#210505) (#211351)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[kbn-scout] Add Synthtrace as a fixture\n(#210505)](https://github.com/elastic/kibana/pull/210505)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Sergi\nRomeu\",\"email\":\"sergi.romeu@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-14T18:52:22Z\",\"message\":\"[kbn-scout]\nAdd Synthtrace as a fixture (#210505)\\n\\n## Summary\\n\\nCloses\n#210340\\n\\nThis PR adds synthtrace clients to scout as a test fixture,\nso you can\\nuse it in your test to generate data.\\n\\nThe clients added\nwere `apmSynthtraceEsClient`,\\n`infraSynthtraceEsClient` and\n`otelSynthtraceEsClient`.\\n\\n## How to use them in parallel tests\\n\\nAs\n`synthtrace` ingests data into our indices, and sequential runs\nwould\\nbe the perfect way to introduce flakiness in our tests, there is\na\\nbetter way to ingest data, using a hook, at the setup phase\nwith\\n`globalSetup`.\\nWe need to create a `global_setup.ts` file and\nlink it into our\\nplaywright config.\\nThen we can use something\nlike\\n```\\nasync function globalSetup(config: FullConfig) {\\n const data\n= {\\n apm: [\\n opbeans({\\n from: new Date(start).getTime(),\\n to: new\nDate(end).getTime(),\\n }),\\n ],\\n infra: [\\n generateHosts({\\n from: new\nDate(start).toISOString(),\\n to: new Date(end).toISOString(),\\n }),\\n\n],\\n otel: [\\n sendotlp({\\n from: new Date(start).getTime(),\\n to: new\nDate(end).getTime(),\\n }),\\n ],\\n };\\n\\n return\ningestSynthtraceDataHook(config, data);\\n}\\n```\\nEach key (apm, infra,\notel) accepts an array of generators.\\n\\n## How to use them in\nsequential tests\\n> [!WARNING] \\n> This should not be the standard\nbehaviour, we should embrace\\nparallelism and use sequential testing\nwhen there is no other way.\\n\\n### apmSynthtraceEsClient\\n```ts\\n\ntest.before(\\n async ({ apmSynthtraceEsClient }) => {\\n await\napmSynthtraceEsClient.index(\\n opbeans({\\n from: new\nDate(start).getTime(),\\n to: new Date(end).getTime(),\\n })\\n );\\n }\\n\n);\\n```\\n[opbeans\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/opbeans.ts)\\nused\nin the example.\\n\\n### otelSynthtraceEsClient\\n```ts\\n test.before(\\n\nasync ({otelSynthtraceEsClient }) => {\\n await\notelSynthtraceEsClient.index(\\n sendotlp({\\n from: new\nDate(start).getTime(),\\n to: new Date(end).getTime(),\\n })\\n );\\n }\\n\n);\\n```\\n[sendotlp\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/sendotlp.ts)\\nwhich\nwill create the data.\\n\\n### infraSynthtraceEsClient\\n```ts\\n\ntest.before(\\n async ({ infraSynthtraceEsClient }) => {\\n await\ninfraSynthtraceEsClient.index(\\n generateHosts({\\n from: new\nDate(start).toISOString(),\\n to: new Date(end).toISOString(),\\n })\\n\n);\\n }\\n\n);\\n```\\n[generateHosts\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/inventory/e2e/cypress/e2e/alert_count/generate_data.ts#L82)\\nused\nto generate data.\\n\\n---------\\n\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"e21c5d0e9175ffd1bea0ad78ffe26cb973cc489f\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"apm:synthtrace\",\"Team:obs-ux-infra_services\",\"backport:version\",\"test:scout\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[kbn-scout]\nAdd Synthtrace as a\nfixture\",\"number\":210505,\"url\":\"https://github.com/elastic/kibana/pull/210505\",\"mergeCommit\":{\"message\":\"[kbn-scout]\nAdd Synthtrace as a fixture (#210505)\\n\\n## Summary\\n\\nCloses\n#210340\\n\\nThis PR adds synthtrace clients to scout as a test fixture,\nso you can\\nuse it in your test to generate data.\\n\\nThe clients added\nwere `apmSynthtraceEsClient`,\\n`infraSynthtraceEsClient` and\n`otelSynthtraceEsClient`.\\n\\n## How to use them in parallel tests\\n\\nAs\n`synthtrace` ingests data into our indices, and sequential runs\nwould\\nbe the perfect way to introduce flakiness in our tests, there is\na\\nbetter way to ingest data, using a hook, at the setup phase\nwith\\n`globalSetup`.\\nWe need to create a `global_setup.ts` file and\nlink it into our\\nplaywright config.\\nThen we can use something\nlike\\n```\\nasync function globalSetup(config: FullConfig) {\\n const data\n= {\\n apm: [\\n opbeans({\\n from: new Date(start).getTime(),\\n to: new\nDate(end).getTime(),\\n }),\\n ],\\n infra: [\\n generateHosts({\\n from: new\nDate(start).toISOString(),\\n to: new Date(end).toISOString(),\\n }),\\n\n],\\n otel: [\\n sendotlp({\\n from: new Date(start).getTime(),\\n to: new\nDate(end).getTime(),\\n }),\\n ],\\n };\\n\\n return\ningestSynthtraceDataHook(config, data);\\n}\\n```\\nEach key (apm, infra,\notel) accepts an array of generators.\\n\\n## How to use them in\nsequential tests\\n> [!WARNING] \\n> This should not be the standard\nbehaviour, we should embrace\\nparallelism and use sequential testing\nwhen there is no other way.\\n\\n### apmSynthtraceEsClient\\n```ts\\n\ntest.before(\\n async ({ apmSynthtraceEsClient }) => {\\n await\napmSynthtraceEsClient.index(\\n opbeans({\\n from: new\nDate(start).getTime(),\\n to: new Date(end).getTime(),\\n })\\n );\\n }\\n\n);\\n```\\n[opbeans\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/opbeans.ts)\\nused\nin the example.\\n\\n### otelSynthtraceEsClient\\n```ts\\n test.before(\\n\nasync ({otelSynthtraceEsClient }) => {\\n await\notelSynthtraceEsClient.index(\\n sendotlp({\\n from: new\nDate(start).getTime(),\\n to: new Date(end).getTime(),\\n })\\n );\\n }\\n\n);\\n```\\n[sendotlp\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/sendotlp.ts)\\nwhich\nwill create the data.\\n\\n### infraSynthtraceEsClient\\n```ts\\n\ntest.before(\\n async ({ infraSynthtraceEsClient }) => {\\n await\ninfraSynthtraceEsClient.index(\\n generateHosts({\\n from: new\nDate(start).toISOString(),\\n to: new Date(end).toISOString(),\\n })\\n\n);\\n }\\n\n);\\n```\\n[generateHosts\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/inventory/e2e/cypress/e2e/alert_count/generate_data.ts#L82)\\nused\nto generate data.\\n\\n---------\\n\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"e21c5d0e9175ffd1bea0ad78ffe26cb973cc489f\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/210505\",\"number\":210505,\"mergeCommit\":{\"message\":\"[kbn-scout]\nAdd Synthtrace as a fixture (#210505)\\n\\n## Summary\\n\\nCloses\n#210340\\n\\nThis PR adds synthtrace clients to scout as a test fixture,\nso you can\\nuse it in your test to generate data.\\n\\nThe clients added\nwere `apmSynthtraceEsClient`,\\n`infraSynthtraceEsClient` and\n`otelSynthtraceEsClient`.\\n\\n## How to use them in parallel tests\\n\\nAs\n`synthtrace` ingests data into our indices, and sequential runs\nwould\\nbe the perfect way to introduce flakiness in our tests, there is\na\\nbetter way to ingest data, using a hook, at the setup phase\nwith\\n`globalSetup`.\\nWe need to create a `global_setup.ts` file and\nlink it into our\\nplaywright config.\\nThen we can use something\nlike\\n```\\nasync function globalSetup(config: FullConfig) {\\n const data\n= {\\n apm: [\\n opbeans({\\n from: new Date(start).getTime(),\\n to: new\nDate(end).getTime(),\\n }),\\n ],\\n infra: [\\n generateHosts({\\n from: new\nDate(start).toISOString(),\\n to: new Date(end).toISOString(),\\n }),\\n\n],\\n otel: [\\n sendotlp({\\n from: new Date(start).getTime(),\\n to: new\nDate(end).getTime(),\\n }),\\n ],\\n };\\n\\n return\ningestSynthtraceDataHook(config, data);\\n}\\n```\\nEach key (apm, infra,\notel) accepts an array of generators.\\n\\n## How to use them in\nsequential tests\\n> [!WARNING] \\n> This should not be the standard\nbehaviour, we should embrace\\nparallelism and use sequential testing\nwhen there is no other way.\\n\\n### apmSynthtraceEsClient\\n```ts\\n\ntest.before(\\n async ({ apmSynthtraceEsClient }) => {\\n await\napmSynthtraceEsClient.index(\\n opbeans({\\n from: new\nDate(start).getTime(),\\n to: new Date(end).getTime(),\\n })\\n );\\n }\\n\n);\\n```\\n[opbeans\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/opbeans.ts)\\nused\nin the example.\\n\\n### otelSynthtraceEsClient\\n```ts\\n test.before(\\n\nasync ({otelSynthtraceEsClient }) => {\\n await\notelSynthtraceEsClient.index(\\n sendotlp({\\n from: new\nDate(start).getTime(),\\n to: new Date(end).getTime(),\\n })\\n );\\n }\\n\n);\\n```\\n[sendotlp\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/sendotlp.ts)\\nwhich\nwill create the data.\\n\\n### infraSynthtraceEsClient\\n```ts\\n\ntest.before(\\n async ({ infraSynthtraceEsClient }) => {\\n await\ninfraSynthtraceEsClient.index(\\n generateHosts({\\n from: new\nDate(start).toISOString(),\\n to: new Date(end).toISOString(),\\n })\\n\n);\\n }\\n\n);\\n```\\n[generateHosts\\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/inventory/e2e/cypress/e2e/alert_count/generate_data.ts#L82)\\nused\nto generate data.\\n\\n---------\\n\\nCo-authored-by: kibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"e21c5d0e9175ffd1bea0ad78ffe26cb973cc489f\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Sergi Romeu <sergi.romeu@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210505","number":210505,"mergeCommit":{"message":"[kbn-scout] Add Synthtrace as a fixture (#210505)\n\n## Summary\n\nCloses #210340\n\nThis PR adds synthtrace clients to scout as a test fixture, so you can\nuse it in your test to generate data.\n\nThe clients added were `apmSynthtraceEsClient`,\n`infraSynthtraceEsClient` and `otelSynthtraceEsClient`.\n\n## How to use them in parallel tests\n\nAs `synthtrace` ingests data into our indices, and sequential runs would\nbe the perfect way to introduce flakiness in our tests, there is a\nbetter way to ingest data, using a hook, at the setup phase with\n`globalSetup`.\nWe need to create a `global_setup.ts` file and link it into our\nplaywright config.\nThen we can use something like\n```\nasync function globalSetup(config: FullConfig) {\n const data = {\n apm: [\n opbeans({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n }),\n ],\n infra: [\n generateHosts({\n from: new Date(start).toISOString(),\n to: new Date(end).toISOString(),\n }),\n ],\n otel: [\n sendotlp({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n }),\n ],\n };\n\n return ingestSynthtraceDataHook(config, data);\n}\n```\nEach key (apm, infra, otel) accepts an array of generators.\n\n## How to use them in sequential tests\n> [!WARNING] \n> This should not be the standard behaviour, we should embrace\nparallelism and use sequential testing when there is no other way.\n\n### apmSynthtraceEsClient\n```ts\n test.before(\n async ({ apmSynthtraceEsClient }) => {\n await apmSynthtraceEsClient.index(\n opbeans({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n })\n );\n }\n );\n```\n[opbeans\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/opbeans.ts)\nused in the example.\n\n### otelSynthtraceEsClient\n```ts\n test.before(\n async ({otelSynthtraceEsClient }) => {\n await otelSynthtraceEsClient.index(\n sendotlp({\n from: new Date(start).getTime(),\n to: new Date(end).getTime(),\n })\n );\n }\n );\n```\n[sendotlp\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/apm/ftr_e2e/cypress/fixtures/synthtrace/sendotlp.ts)\nwhich will create the data.\n\n### infraSynthtraceEsClient\n```ts\n test.before(\n async ({ infraSynthtraceEsClient }) => {\n await infraSynthtraceEsClient.index(\n generateHosts({\n from: new Date(start).toISOString(),\n to: new Date(end).toISOString(),\n })\n );\n }\n );\n```\n[generateHosts\nfile](https://github.com/elastic/kibana/blob/main/x-pack/solutions/observability/plugins/inventory/e2e/cypress/e2e/alert_count/generate_data.ts#L82)\nused to generate data.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"e21c5d0e9175ffd1bea0ad78ffe26cb973cc489f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co>	2025-02-18 15:28:33 +01:00
Sergi Romeu	398c1bf795	[8.x] [APM][Otel] Add Otel client based on PoC data (#192293) (#211541) ... # Backport This will backport the following commits from `main` to `8.x`: - [[APM][Otel] Add Otel client based on PoC data (#192293)](https://github.com/elastic/kibana/pull/192293) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2024-10-14T12:33:22Z","message":"[APM][Otel] Add Otel client based on PoC data (#192293)\n\nCloses [#192115](https://github.com/elastic/kibana/issues/192115)\r\nCloses [#192465](https://github.com/elastic/kibana/issues/192465)\r\n\r\n\r\n## Summary\r\n\r\nThis PR adds synthrace client for Otel native data and a simple\r\nscenario. This is the first step of adding it and in the future it will\r\ninclude more metrics and use cases.\r\n\r\n>[!NOTE]\r\n> To run ES the command needs \"xpack.otel_data.registry.enabled=true\"\r\nflag\r\n> `yarn es snapshot --license trial --E\r\n\"xpack.otel_data.registry.enabled=true\"`\r\n\r\n## Next steps\r\n- We currently have only `service_destination` in the metrics indices we\r\ncan include the other types in the future\r\n- After we have all the UI changes we can add more scenarios (also using\r\nthe opentelemetry demo data and not only the e2e PoC example)\r\n\r\n## Testing\r\n- Run ES: \r\n```bash \r\nyarn es snapshot --license trial --E \"xpack.otel_data.registry.enabled=true\"\r\n```\r\n- Run Kibana:\r\n```bash \r\nyarn start\r\n```\r\n\r\n>[!WARNING]\r\nIf the e2e PoC is used the first 2 steps should be skipped\r\n\r\n- Run syntrace: \r\n```bash\r\nnode scripts/synthtrace otel_simple_trace.ts --clean\r\n```\r\n- Check indices in DevTools for the generated data: \r\n```bash \r\nGET *metrics-generic.otel*/_search\r\n\r\nGET *traces-generic.otel*/_search\r\n\r\nGET *logs-generic.otel*/_search\r\n```\r\n- Check in the APM UI (all the tabs) \r\n>[!WARNING]\r\nCurrently the UI changes done in APM are not merged so some errors are\r\nexpected)\r\n\r\n\r\nhttps://github.com/user-attachments/assets/92f63610-82da-40f3-89bb-00be83c55377\r\n\r\n---------\r\n\r\nCo-authored-by: miriam.aparicio <miriam.aparicio@gmail.com>","sha":"5067f1554cb5fc7f23442d5f9ab5d255e26a3b37","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","OpenTelemetry","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[APM][Otel] Add Otel client based on PoC data","number":192293,"url":"https://github.com/elastic/kibana/pull/192293","mergeCommit":{"message":"[APM][Otel] Add Otel client based on PoC data (#192293)\n\nCloses [#192115](https://github.com/elastic/kibana/issues/192115)\r\nCloses [#192465](https://github.com/elastic/kibana/issues/192465)\r\n\r\n\r\n## Summary\r\n\r\nThis PR adds synthrace client for Otel native data and a simple\r\nscenario. This is the first step of adding it and in the future it will\r\ninclude more metrics and use cases.\r\n\r\n>[!NOTE]\r\n> To run ES the command needs \"xpack.otel_data.registry.enabled=true\"\r\nflag\r\n> `yarn es snapshot --license trial --E\r\n\"xpack.otel_data.registry.enabled=true\"`\r\n\r\n## Next steps\r\n- We currently have only `service_destination` in the metrics indices we\r\ncan include the other types in the future\r\n- After we have all the UI changes we can add more scenarios (also using\r\nthe opentelemetry demo data and not only the e2e PoC example)\r\n\r\n## Testing\r\n- Run ES: \r\n```bash \r\nyarn es snapshot --license trial --E \"xpack.otel_data.registry.enabled=true\"\r\n```\r\n- Run Kibana:\r\n```bash \r\nyarn start\r\n```\r\n\r\n>[!WARNING]\r\nIf the e2e PoC is used the first 2 steps should be skipped\r\n\r\n- Run syntrace: \r\n```bash\r\nnode scripts/synthtrace otel_simple_trace.ts --clean\r\n```\r\n- Check indices in DevTools for the generated data: \r\n```bash \r\nGET *metrics-generic.otel*/_search\r\n\r\nGET *traces-generic.otel*/_search\r\n\r\nGET *logs-generic.otel*/_search\r\n```\r\n- Check in the APM UI (all the tabs) \r\n>[!WARNING]\r\nCurrently the UI changes done in APM are not merged so some errors are\r\nexpected)\r\n\r\n\r\nhttps://github.com/user-attachments/assets/92f63610-82da-40f3-89bb-00be83c55377\r\n\r\n---------\r\n\r\nCo-authored-by: miriam.aparicio <miriam.aparicio@gmail.com>","sha":"5067f1554cb5fc7f23442d5f9ab5d255e26a3b37"}},"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/192293","number":192293,"mergeCommit":{"message":"[APM][Otel] Add Otel client based on PoC data (#192293)\n\nCloses [#192115](https://github.com/elastic/kibana/issues/192115)\r\nCloses [#192465](https://github.com/elastic/kibana/issues/192465)\r\n\r\n\r\n## Summary\r\n\r\nThis PR adds synthrace client for Otel native data and a simple\r\nscenario. This is the first step of adding it and in the future it will\r\ninclude more metrics and use cases.\r\n\r\n>[!NOTE]\r\n> To run ES the command needs \"xpack.otel_data.registry.enabled=true\"\r\nflag\r\n> `yarn es snapshot --license trial --E\r\n\"xpack.otel_data.registry.enabled=true\"`\r\n\r\n## Next steps\r\n- We currently have only `service_destination` in the metrics indices we\r\ncan include the other types in the future\r\n- After we have all the UI changes we can add more scenarios (also using\r\nthe opentelemetry demo data and not only the e2e PoC example)\r\n\r\n## Testing\r\n- Run ES: \r\n```bash \r\nyarn es snapshot --license trial --E \"xpack.otel_data.registry.enabled=true\"\r\n```\r\n- Run Kibana:\r\n```bash \r\nyarn start\r\n```\r\n\r\n>[!WARNING]\r\nIf the e2e PoC is used the first 2 steps should be skipped\r\n\r\n- Run syntrace: \r\n```bash\r\nnode scripts/synthtrace otel_simple_trace.ts --clean\r\n```\r\n- Check indices in DevTools for the generated data: \r\n```bash \r\nGET *metrics-generic.otel*/_search\r\n\r\nGET *traces-generic.otel*/_search\r\n\r\nGET *logs-generic.otel*/_search\r\n```\r\n- Check in the APM UI (all the tabs) \r\n>[!WARNING]\r\nCurrently the UI changes done in APM are not merged so some errors are\r\nexpected)\r\n\r\n\r\nhttps://github.com/user-attachments/assets/92f63610-82da-40f3-89bb-00be83c55377\r\n\r\n---------\r\n\r\nCo-authored-by: miriam.aparicio <miriam.aparicio@gmail.com>","sha":"5067f1554cb5fc7f23442d5f9ab5d255e26a3b37"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co>	2025-02-18 12:49:55 +01:00
Dzmitry Lemechko	975485161c	[8.x] [scout] adding test helper @kbn/scout-oblt package and uptate onboarding tests (#209761) (#211490) ... # Backport This will backport the following commits from `main` to `8.x`: - [[scout] adding test helper &#x60;@kbn/scout-oblt&#x60; package and uptate onboarding tests (#209761)](https://github.com/elastic/kibana/pull/209761) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T17:38:41Z","message":"[scout] adding test helper `@kbn/scout-oblt` package and uptate onboarding tests (#209761)\n\n## Summary\r\n\r\n`@kbn/scout-oblt` is a test library that extends `@kbn/scout` with test\r\nhelpers specifically designed to test `Observability` applications in\r\nKibana. All Oblt plugins should only import from `@kbn/scout-oblt`\r\n\r\nIts primary goal is to simplify the test development experience for\r\nteams working on `Observability` plugins by providing custom Playwright\r\nfixtures, page objects, and utilities tailored for Observability-related\r\ntesting scenarios.\r\n\r\nContributing:\r\n- when Fixture/Page Object is sharable across all Solutions and Platform\r\n(`fleetApi` fixture), it should be added in `@kbn/scout`\r\n- when Fixture/Page Object is Oblt-specific but is shared across tests\r\nunder the multiple plugins (`OnboardingHome` page), it should be added\r\nin `@kbn/scout-oblt`\r\n- when Fixture/Page Object is only used in a single plugin (`onboarding`\r\ninternal APIs ?), it should be added in this plugin.\r\n\r\nI also re-worked existing tests with few ideas in mind:\r\n- Scout is **e2e testing tool** and should target primary e2e test\r\nscenarios; We have _API integration tests_ to test multiple short\r\nscenarios for APIs behavior (response, status code) and _jest/React\r\ntesting library_ to test components in isolation (elements rendering,\r\nfields validation). Doing all the testing with e2e tool like Playwright\r\nwill dramatically affect cost efficiency and stability of tests, but\r\nalso slows overall CI execution and PRs delivery. The goal is to follow\r\ntesting pyramid and keep in mind its principles.\r\n- We on purpose spin up new browser context for each `test` block to\r\nmake sure our **tests are independent**. Having too many short `test`\r\nblocks in the file significantly slows down the execution: every block\r\ntriggers browser context, saml authentication, adding/removing Fleet\r\nintegrations (each call up to 2 seconds) and other beforeEach/afterEach\r\nhooks. Real browser-based testing is expensive. It is not about putting\r\nevery step into 1 `test` block, but also not a Jest unit-test-style\r\ndesign. When it is possible to group similar actions on the same page\r\nand if it is a part of the same user flow - we should do it. It also\r\ndoesn't bring the testing value repeating the same UI steps multiple\r\ntimes in different scenarios. _Our CI costs are critical to cut when it\r\nis possible_\r\n- Avoid **nesting describe** blocks: it complicates test readability and\r\nalso complicates for CI bot to properly skip the failing block (it will\r\nskip the top level one). We encourage **Scout parallel test execution**\r\nbased on running test spec files in multiple workers, not the `test`\r\nblocks within the same file. Having too many `test` blocks in the same\r\nfile will be slowly run in the single thread and in case of flakiness,\r\nit means Team lose more test coverage than they probably expect.\r\n\r\nBefore (**59** test blocks - **8-8.5 min** per distro):\r\n<img width=\"1709\" alt=\"Screenshot 2025-02-08 at 18 01 40\"\r\nsrc=\"https://github.com/user-attachments/assets/5fd65a1c-85f9-4594-9dae-3f8e99a005ab\"\r\n/>\r\n\r\nAfter (**15** test blocks - **3.5-4 min** per distro):\r\n<img width=\"1578\" alt=\"Screenshot 2025-02-10 at 18 14 42\"\r\nsrc=\"https://github.com/user-attachments/assets/6846898f-7dd2-4f6b-8bc5-d06741b0b120\"\r\n/>\r\n\r\nFor reviewers: updated tests are possible to run in 2 parallel workers\r\nagainst the same Kibana/ES instance and run time is dropping to **2.5-3\r\nmin** 🚀 . It is up to UX-Logs team to decide if you want to keep\r\nparallel run (new tests can be added either to parallel or sequential\r\nrun)\r\n<img width=\"1578\" alt=\"Screenshot 2025-02-11 at 12 14 30\"\r\nsrc=\"https://github.com/user-attachments/assets/e94113f2-d7f1-470e-a6d5-cb5154d99c41\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bd13e829498032c07bf8490f770a563f34e9f856","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] adding test helper `@kbn/scout-oblt` package and uptate onboarding tests","number":209761,"url":"https://github.com/elastic/kibana/pull/209761","mergeCommit":{"message":"[scout] adding test helper `@kbn/scout-oblt` package and uptate onboarding tests (#209761)\n\n## Summary\r\n\r\n`@kbn/scout-oblt` is a test library that extends `@kbn/scout` with test\r\nhelpers specifically designed to test `Observability` applications in\r\nKibana. All Oblt plugins should only import from `@kbn/scout-oblt`\r\n\r\nIts primary goal is to simplify the test development experience for\r\nteams working on `Observability` plugins by providing custom Playwright\r\nfixtures, page objects, and utilities tailored for Observability-related\r\ntesting scenarios.\r\n\r\nContributing:\r\n- when Fixture/Page Object is sharable across all Solutions and Platform\r\n(`fleetApi` fixture), it should be added in `@kbn/scout`\r\n- when Fixture/Page Object is Oblt-specific but is shared across tests\r\nunder the multiple plugins (`OnboardingHome` page), it should be added\r\nin `@kbn/scout-oblt`\r\n- when Fixture/Page Object is only used in a single plugin (`onboarding`\r\ninternal APIs ?), it should be added in this plugin.\r\n\r\nI also re-worked existing tests with few ideas in mind:\r\n- Scout is **e2e testing tool** and should target primary e2e test\r\nscenarios; We have _API integration tests_ to test multiple short\r\nscenarios for APIs behavior (response, status code) and _jest/React\r\ntesting library_ to test components in isolation (elements rendering,\r\nfields validation). Doing all the testing with e2e tool like Playwright\r\nwill dramatically affect cost efficiency and stability of tests, but\r\nalso slows overall CI execution and PRs delivery. The goal is to follow\r\ntesting pyramid and keep in mind its principles.\r\n- We on purpose spin up new browser context for each `test` block to\r\nmake sure our **tests are independent**. Having too many short `test`\r\nblocks in the file significantly slows down the execution: every block\r\ntriggers browser context, saml authentication, adding/removing Fleet\r\nintegrations (each call up to 2 seconds) and other beforeEach/afterEach\r\nhooks. Real browser-based testing is expensive. It is not about putting\r\nevery step into 1 `test` block, but also not a Jest unit-test-style\r\ndesign. When it is possible to group similar actions on the same page\r\nand if it is a part of the same user flow - we should do it. It also\r\ndoesn't bring the testing value repeating the same UI steps multiple\r\ntimes in different scenarios. _Our CI costs are critical to cut when it\r\nis possible_\r\n- Avoid **nesting describe** blocks: it complicates test readability and\r\nalso complicates for CI bot to properly skip the failing block (it will\r\nskip the top level one). We encourage **Scout parallel test execution**\r\nbased on running test spec files in multiple workers, not the `test`\r\nblocks within the same file. Having too many `test` blocks in the same\r\nfile will be slowly run in the single thread and in case of flakiness,\r\nit means Team lose more test coverage than they probably expect.\r\n\r\nBefore (**59** test blocks - **8-8.5 min** per distro):\r\n<img width=\"1709\" alt=\"Screenshot 2025-02-08 at 18 01 40\"\r\nsrc=\"https://github.com/user-attachments/assets/5fd65a1c-85f9-4594-9dae-3f8e99a005ab\"\r\n/>\r\n\r\nAfter (**15** test blocks - **3.5-4 min** per distro):\r\n<img width=\"1578\" alt=\"Screenshot 2025-02-10 at 18 14 42\"\r\nsrc=\"https://github.com/user-attachments/assets/6846898f-7dd2-4f6b-8bc5-d06741b0b120\"\r\n/>\r\n\r\nFor reviewers: updated tests are possible to run in 2 parallel workers\r\nagainst the same Kibana/ES instance and run time is dropping to **2.5-3\r\nmin** 🚀 . It is up to UX-Logs team to decide if you want to keep\r\nparallel run (new tests can be added either to parallel or sequential\r\nrun)\r\n<img width=\"1578\" alt=\"Screenshot 2025-02-11 at 12 14 30\"\r\nsrc=\"https://github.com/user-attachments/assets/e94113f2-d7f1-470e-a6d5-cb5154d99c41\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bd13e829498032c07bf8490f770a563f34e9f856"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210675","number":210675,"state":"MERGED","mergeCommit":{"sha":"187b2307220a1f54776b0b3b05d131b0e75b6e03","message":"[9.0] [scout] adding test helper &#x60;@kbn/scout-oblt&#x60; package and uptate onboarding tests (#209761) (#210675)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[scout] adding test helper &#x60;@kbn/scout-oblt&#x60; package and\nuptate onboarding tests\n(#209761)](https://github.com/elastic/kibana/pull/209761)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dzmitry\nLemechko\",\"email\":\"dzmitry.lemechko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-11T17:38:41Z\",\"message\":\"[scout]\nadding test helper `@kbn/scout-oblt` package and uptate onboarding tests\n(#209761)\\n\\n## Summary\\r\\n\\r\\n`@kbn/scout-oblt` is a test library that\nextends `@kbn/scout` with test\\r\\nhelpers specifically designed to test\n`Observability` applications in\\r\\nKibana. All Oblt plugins should only\nimport from `@kbn/scout-oblt`\\r\\n\\r\\nIts primary goal is to simplify the\ntest development experience for\\r\\nteams working on `Observability`\nplugins by providing custom Playwright\\r\\nfixtures, page objects, and\nutilities tailored for Observability-related\\r\\ntesting\nscenarios.\\r\\n\\r\\nContributing:\\r\\n- when Fixture/Page Object is\nsharable across all Solutions and Platform\\r\\n(`fleetApi` fixture), it\nshould be added in `@kbn/scout`\\r\\n- when Fixture/Page Object is\nOblt-specific but is shared across tests\\r\\nunder the multiple plugins\n(`OnboardingHome` page), it should be added\\r\\nin `@kbn/scout-oblt`\\r\\n-\nwhen Fixture/Page Object is only used in a single plugin\n(`onboarding`\\r\\ninternal APIs ?), it should be added in this\nplugin.\\r\\n\\r\\nI also re-worked existing tests with few ideas in\nmind:\\r\\n- Scout is **e2e testing tool** and should target primary e2e\ntest\\r\\nscenarios; We have _API integration tests_ to test multiple\nshort\\r\\nscenarios for APIs behavior (response, status code) and\n_jest/React\\r\\ntesting library_ to test components in isolation\n(elements rendering,\\r\\nfields validation). Doing all the testing with\ne2e tool like Playwright\\r\\nwill dramatically affect cost efficiency and\nstability of tests, but\\r\\nalso slows overall CI execution and PRs\ndelivery. The goal is to follow\\r\\ntesting pyramid and keep in mind its\nprinciples.\\r\\n- We on purpose spin up new browser context for each\n`test` block to\\r\\nmake sure our **tests are independent**. Having too\nmany short `test`\\r\\nblocks in the file significantly slows down the\nexecution: every block\\r\\ntriggers browser context, saml authentication,\nadding/removing Fleet\\r\\nintegrations (each call up to 2 seconds) and\nother beforeEach/afterEach\\r\\nhooks. Real browser-based testing is\nexpensive. It is not about putting\\r\\nevery step into 1 `test` block,\nbut also not a Jest unit-test-style\\r\\ndesign. When it is possible to\ngroup similar actions on the same page\\r\\nand if it is a part of the\nsame user flow - we should do it. It also\\r\\ndoesn't bring the testing\nvalue repeating the same UI steps multiple\\r\\ntimes in different\nscenarios. _Our CI costs are critical to cut when it\\r\\nis\npossible_\\r\\n- Avoid **nesting describe** blocks: it complicates test\nreadability and\\r\\nalso complicates for CI bot to properly skip the\nfailing block (it will\\r\\nskip the top level one). We encourage **Scout\nparallel test execution**\\r\\nbased on running test spec files in\nmultiple workers, not the `test`\\r\\nblocks within the same file. Having\ntoo many `test` blocks in the same\\r\\nfile will be slowly run in the\nsingle thread and in case of flakiness,\\r\\nit means Team lose more test\ncoverage than they probably expect.\\r\\n\\r\\nBefore (**59** test blocks -\n**8-8.5 min** per distro):\\r\\n<img width=\\\"1709\\\" alt=\\\"Screenshot\n2025-02-08 at 18 01\n40\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5fd65a1c-85f9-4594-9dae-3f8e99a005ab\\\"\\r\\n/>\\r\\n\\r\\nAfter\n(**15** test blocks - **3.5-4 min** per distro):\\r\\n<img width=\\\"1578\\\"\nalt=\\\"Screenshot 2025-02-10 at 18 14\n42\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/6846898f-7dd2-4f6b-8bc5-d06741b0b120\\\"\\r\\n/>\\r\\n\\r\\nFor\nreviewers: updated tests are possible to run in 2 parallel\nworkers\\r\\nagainst the same Kibana/ES instance and run time is dropping\nto **2.5-3\\r\\nmin** 🚀 . It is up to UX-Logs team to decide if you want\nto keep\\r\\nparallel run (new tests can be added either to parallel or\nsequential\\r\\nrun)\\r\\n<img width=\\\"1578\\\" alt=\\\"Screenshot 2025-02-11 at\n12 14\n30\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/e94113f2-d7f1-470e-a6d5-cb5154d99c41\\\"\\r\\n/>\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"bd13e829498032c07bf8490f770a563f34e9f856\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:version\",\"test:scout\",\"v9.1.0\",\"v8.19.0\"],\"title\":\"[scout]\nadding test helper `@kbn/scout-oblt` package and uptate onboarding\ntests\",\"number\":209761,\"url\":\"https://github.com/elastic/kibana/pull/209761\",\"mergeCommit\":{\"message\":\"[scout]\nadding test helper `@kbn/scout-oblt` package and uptate onboarding tests\n(#209761)\\n\\n## Summary\\r\\n\\r\\n`@kbn/scout-oblt` is a test library that\nextends `@kbn/scout` with test\\r\\nhelpers specifically designed to test\n`Observability` applications in\\r\\nKibana. All Oblt plugins should only\nimport from `@kbn/scout-oblt`\\r\\n\\r\\nIts primary goal is to simplify the\ntest development experience for\\r\\nteams working on `Observability`\nplugins by providing custom Playwright\\r\\nfixtures, page objects, and\nutilities tailored for Observability-related\\r\\ntesting\nscenarios.\\r\\n\\r\\nContributing:\\r\\n- when Fixture/Page Object is\nsharable across all Solutions and Platform\\r\\n(`fleetApi` fixture), it\nshould be added in `@kbn/scout`\\r\\n- when Fixture/Page Object is\nOblt-specific but is shared across tests\\r\\nunder the multiple plugins\n(`OnboardingHome` page), it should be added\\r\\nin `@kbn/scout-oblt`\\r\\n-\nwhen Fixture/Page Object is only used in a single plugin\n(`onboarding`\\r\\ninternal APIs ?), it should be added in this\nplugin.\\r\\n\\r\\nI also re-worked existing tests with few ideas in\nmind:\\r\\n- Scout is **e2e testing tool** and should target primary e2e\ntest\\r\\nscenarios; We have _API integration tests_ to test multiple\nshort\\r\\nscenarios for APIs behavior (response, status code) and\n_jest/React\\r\\ntesting library_ to test components in isolation\n(elements rendering,\\r\\nfields validation). Doing all the testing with\ne2e tool like Playwright\\r\\nwill dramatically affect cost efficiency and\nstability of tests, but\\r\\nalso slows overall CI execution and PRs\ndelivery. The goal is to follow\\r\\ntesting pyramid and keep in mind its\nprinciples.\\r\\n- We on purpose spin up new browser context for each\n`test` block to\\r\\nmake sure our **tests are independent**. Having too\nmany short `test`\\r\\nblocks in the file significantly slows down the\nexecution: every block\\r\\ntriggers browser context, saml authentication,\nadding/removing Fleet\\r\\nintegrations (each call up to 2 seconds) and\nother beforeEach/afterEach\\r\\nhooks. Real browser-based testing is\nexpensive. It is not about putting\\r\\nevery step into 1 `test` block,\nbut also not a Jest unit-test-style\\r\\ndesign. When it is possible to\ngroup similar actions on the same page\\r\\nand if it is a part of the\nsame user flow - we should do it. It also\\r\\ndoesn't bring the testing\nvalue repeating the same UI steps multiple\\r\\ntimes in different\nscenarios. _Our CI costs are critical to cut when it\\r\\nis\npossible_\\r\\n- Avoid **nesting describe** blocks: it complicates test\nreadability and\\r\\nalso complicates for CI bot to properly skip the\nfailing block (it will\\r\\nskip the top level one). We encourage **Scout\nparallel test execution**\\r\\nbased on running test spec files in\nmultiple workers, not the `test`\\r\\nblocks within the same file. Having\ntoo many `test` blocks in the same\\r\\nfile will be slowly run in the\nsingle thread and in case of flakiness,\\r\\nit means Team lose more test\ncoverage than they probably expect.\\r\\n\\r\\nBefore (**59** test blocks -\n**8-8.5 min** per distro):\\r\\n<img width=\\\"1709\\\" alt=\\\"Screenshot\n2025-02-08 at 18 01\n40\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5fd65a1c-85f9-4594-9dae-3f8e99a005ab\\\"\\r\\n/>\\r\\n\\r\\nAfter\n(**15** test blocks - **3.5-4 min** per distro):\\r\\n<img width=\\\"1578\\\"\nalt=\\\"Screenshot 2025-02-10 at 18 14\n42\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/6846898f-7dd2-4f6b-8bc5-d06741b0b120\\\"\\r\\n/>\\r\\n\\r\\nFor\nreviewers: updated tests are possible to run in 2 parallel\nworkers\\r\\nagainst the same Kibana/ES instance and run time is dropping\nto **2.5-3\\r\\nmin** 🚀 . It is up to UX-Logs team to decide if you want\nto keep\\r\\nparallel run (new tests can be added either to parallel or\nsequential\\r\\nrun)\\r\\n<img width=\\\"1578\\\" alt=\\\"Screenshot 2025-02-11 at\n12 14\n30\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/e94113f2-d7f1-470e-a6d5-cb5154d99c41\\\"\\r\\n/>\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"bd13e829498032c07bf8490f770a563f34e9f856\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209761\",\"number\":209761,\"mergeCommit\":{\"message\":\"[scout]\nadding test helper `@kbn/scout-oblt` package and uptate onboarding tests\n(#209761)\\n\\n## Summary\\r\\n\\r\\n`@kbn/scout-oblt` is a test library that\nextends `@kbn/scout` with test\\r\\nhelpers specifically designed to test\n`Observability` applications in\\r\\nKibana. All Oblt plugins should only\nimport from `@kbn/scout-oblt`\\r\\n\\r\\nIts primary goal is to simplify the\ntest development experience for\\r\\nteams working on `Observability`\nplugins by providing custom Playwright\\r\\nfixtures, page objects, and\nutilities tailored for Observability-related\\r\\ntesting\nscenarios.\\r\\n\\r\\nContributing:\\r\\n- when Fixture/Page Object is\nsharable across all Solutions and Platform\\r\\n(`fleetApi` fixture), it\nshould be added in `@kbn/scout`\\r\\n- when Fixture/Page Object is\nOblt-specific but is shared across tests\\r\\nunder the multiple plugins\n(`OnboardingHome` page), it should be added\\r\\nin `@kbn/scout-oblt`\\r\\n-\nwhen Fixture/Page Object is only used in a single plugin\n(`onboarding`\\r\\ninternal APIs ?), it should be added in this\nplugin.\\r\\n\\r\\nI also re-worked existing tests with few ideas in\nmind:\\r\\n- Scout is **e2e testing tool** and should target primary e2e\ntest\\r\\nscenarios; We have _API integration tests_ to test multiple\nshort\\r\\nscenarios for APIs behavior (response, status code) and\n_jest/React\\r\\ntesting library_ to test components in isolation\n(elements rendering,\\r\\nfields validation). Doing all the testing with\ne2e tool like Playwright\\r\\nwill dramatically affect cost efficiency and\nstability of tests, but\\r\\nalso slows overall CI execution and PRs\ndelivery. The goal is to follow\\r\\ntesting pyramid and keep in mind its\nprinciples.\\r\\n- We on purpose spin up new browser context for each\n`test` block to\\r\\nmake sure our **tests are independent**. Having too\nmany short `test`\\r\\nblocks in the file significantly slows down the\nexecution: every block\\r\\ntriggers browser context, saml authentication,\nadding/removing Fleet\\r\\nintegrations (each call up to 2 seconds) and\nother beforeEach/afterEach\\r\\nhooks. Real browser-based testing is\nexpensive. It is not about putting\\r\\nevery step into 1 `test` block,\nbut also not a Jest unit-test-style\\r\\ndesign. When it is possible to\ngroup similar actions on the same page\\r\\nand if it is a part of the\nsame user flow - we should do it. It also\\r\\ndoesn't bring the testing\nvalue repeating the same UI steps multiple\\r\\ntimes in different\nscenarios. _Our CI costs are critical to cut when it\\r\\nis\npossible_\\r\\n- Avoid **nesting describe** blocks: it complicates test\nreadability and\\r\\nalso complicates for CI bot to properly skip the\nfailing block (it will\\r\\nskip the top level one). We encourage **Scout\nparallel test execution**\\r\\nbased on running test spec files in\nmultiple workers, not the `test`\\r\\nblocks within the same file. Having\ntoo many `test` blocks in the same\\r\\nfile will be slowly run in the\nsingle thread and in case of flakiness,\\r\\nit means Team lose more test\ncoverage than they probably expect.\\r\\n\\r\\nBefore (**59** test blocks -\n**8-8.5 min** per distro):\\r\\n<img width=\\\"1709\\\" alt=\\\"Screenshot\n2025-02-08 at 18 01\n40\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/5fd65a1c-85f9-4594-9dae-3f8e99a005ab\\\"\\r\\n/>\\r\\n\\r\\nAfter\n(**15** test blocks - **3.5-4 min** per distro):\\r\\n<img width=\\\"1578\\\"\nalt=\\\"Screenshot 2025-02-10 at 18 14\n42\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/6846898f-7dd2-4f6b-8bc5-d06741b0b120\\\"\\r\\n/>\\r\\n\\r\\nFor\nreviewers: updated tests are possible to run in 2 parallel\nworkers\\r\\nagainst the same Kibana/ES instance and run time is dropping\nto **2.5-3\\r\\nmin** 🚀 . It is up to UX-Logs team to decide if you want\nto keep\\r\\nparallel run (new tests can be added either to parallel or\nsequential\\r\\nrun)\\r\\n<img width=\\\"1578\\\" alt=\\\"Screenshot 2025-02-11 at\n12 14\n30\\\"\\r\\nsrc=\\\"https://github.com/user-attachments/assets/e94113f2-d7f1-470e-a6d5-cb5154d99c41\\\"\\r\\n/>\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"bd13e829498032c07bf8490f770a563f34e9f856\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209761","number":209761,"mergeCommit":{"message":"[scout] adding test helper `@kbn/scout-oblt` package and uptate onboarding tests (#209761)\n\n## Summary\r\n\r\n`@kbn/scout-oblt` is a test library that extends `@kbn/scout` with test\r\nhelpers specifically designed to test `Observability` applications in\r\nKibana. All Oblt plugins should only import from `@kbn/scout-oblt`\r\n\r\nIts primary goal is to simplify the test development experience for\r\nteams working on `Observability` plugins by providing custom Playwright\r\nfixtures, page objects, and utilities tailored for Observability-related\r\ntesting scenarios.\r\n\r\nContributing:\r\n- when Fixture/Page Object is sharable across all Solutions and Platform\r\n(`fleetApi` fixture), it should be added in `@kbn/scout`\r\n- when Fixture/Page Object is Oblt-specific but is shared across tests\r\nunder the multiple plugins (`OnboardingHome` page), it should be added\r\nin `@kbn/scout-oblt`\r\n- when Fixture/Page Object is only used in a single plugin (`onboarding`\r\ninternal APIs ?), it should be added in this plugin.\r\n\r\nI also re-worked existing tests with few ideas in mind:\r\n- Scout is **e2e testing tool** and should target primary e2e test\r\nscenarios; We have _API integration tests_ to test multiple short\r\nscenarios for APIs behavior (response, status code) and _jest/React\r\ntesting library_ to test components in isolation (elements rendering,\r\nfields validation). Doing all the testing with e2e tool like Playwright\r\nwill dramatically affect cost efficiency and stability of tests, but\r\nalso slows overall CI execution and PRs delivery. The goal is to follow\r\ntesting pyramid and keep in mind its principles.\r\n- We on purpose spin up new browser context for each `test` block to\r\nmake sure our **tests are independent**. Having too many short `test`\r\nblocks in the file significantly slows down the execution: every block\r\ntriggers browser context, saml authentication, adding/removing Fleet\r\nintegrations (each call up to 2 seconds) and other beforeEach/afterEach\r\nhooks. Real browser-based testing is expensive. It is not about putting\r\nevery step into 1 `test` block, but also not a Jest unit-test-style\r\ndesign. When it is possible to group similar actions on the same page\r\nand if it is a part of the same user flow - we should do it. It also\r\ndoesn't bring the testing value repeating the same UI steps multiple\r\ntimes in different scenarios. _Our CI costs are critical to cut when it\r\nis possible_\r\n- Avoid **nesting describe** blocks: it complicates test readability and\r\nalso complicates for CI bot to properly skip the failing block (it will\r\nskip the top level one). We encourage **Scout parallel test execution**\r\nbased on running test spec files in multiple workers, not the `test`\r\nblocks within the same file. Having too many `test` blocks in the same\r\nfile will be slowly run in the single thread and in case of flakiness,\r\nit means Team lose more test coverage than they probably expect.\r\n\r\nBefore (**59** test blocks - **8-8.5 min** per distro):\r\n<img width=\"1709\" alt=\"Screenshot 2025-02-08 at 18 01 40\"\r\nsrc=\"https://github.com/user-attachments/assets/5fd65a1c-85f9-4594-9dae-3f8e99a005ab\"\r\n/>\r\n\r\nAfter (**15** test blocks - **3.5-4 min** per distro):\r\n<img width=\"1578\" alt=\"Screenshot 2025-02-10 at 18 14 42\"\r\nsrc=\"https://github.com/user-attachments/assets/6846898f-7dd2-4f6b-8bc5-d06741b0b120\"\r\n/>\r\n\r\nFor reviewers: updated tests are possible to run in 2 parallel workers\r\nagainst the same Kibana/ES instance and run time is dropping to **2.5-3\r\nmin** 🚀 . It is up to UX-Logs team to decide if you want to keep\r\nparallel run (new tests can be added either to parallel or sequential\r\nrun)\r\n<img width=\"1578\" alt=\"Screenshot 2025-02-11 at 12 14 30\"\r\nsrc=\"https://github.com/user-attachments/assets/e94113f2-d7f1-470e-a6d5-cb5154d99c41\"\r\n/>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"bd13e829498032c07bf8490f770a563f34e9f856"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-17 20:36:15 +01:00
Kibana Machine	f8abd586a4	[8.x] [kbn-scout][maps] waitForRenderComplete (#211265) (#211445) ... # Backport This will backport the following commits from `main` to `8.x`: - [[kbn-scout][maps] waitForRenderComplete (#211265)](https://github.com/elastic/kibana/pull/211265) <!--- Backport version: 9.6.5 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-17T13:46:44Z","message":"[kbn-scout][maps] waitForRenderComplete (#211265)\n\n## Summary\n\nThis PR add a method to wait for map to be loaded to replace generic\n`renderable.waitForRender()`.\n\nWhile investigating the recent test failure on CI I found out that for\nmaps case we can simplify the logic with few facts:\n- before start waiting for render to complete, we need to wait for main\ncontainer `#maps-plugin` to be in DOM. It takes 2-3 seconds.\n- there is always a single div block with `data-render-complete`\nattribute, and there is a comment in source code stating `See if the\n\"data-render-complete\" attribute is \"true\". If so we're done!` which\nmeans we can simply wait for\n`div[data-dom-id][data-render-complete=\"true\"]`\n\n\n6de2ef0e6d/x-pack/platform/plugins/shared/maps/public/connected_components/map_container/map_container.tsx (L103-L116)\n\n`renderable.waitForRender()` is a good waiter, but probably for\ndashboard with multiple panels.","sha":"08400b1f4225bcc20b3c28262432ba269e117750","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[kbn-scout][maps] waitForRenderComplete","number":211265,"url":"https://github.com/elastic/kibana/pull/211265","mergeCommit":{"message":"[kbn-scout][maps] waitForRenderComplete (#211265)\n\n## Summary\n\nThis PR add a method to wait for map to be loaded to replace generic\n`renderable.waitForRender()`.\n\nWhile investigating the recent test failure on CI I found out that for\nmaps case we can simplify the logic with few facts:\n- before start waiting for render to complete, we need to wait for main\ncontainer `#maps-plugin` to be in DOM. It takes 2-3 seconds.\n- there is always a single div block with `data-render-complete`\nattribute, and there is a comment in source code stating `See if the\n\"data-render-complete\" attribute is \"true\". If so we're done!` which\nmeans we can simply wait for\n`div[data-dom-id][data-render-complete=\"true\"]`\n\n\n6de2ef0e6d/x-pack/platform/plugins/shared/maps/public/connected_components/map_container/map_container.tsx (L103-L116)\n\n`renderable.waitForRender()` is a good waiter, but probably for\ndashboard with multiple panels.","sha":"08400b1f4225bcc20b3c28262432ba269e117750"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211265","number":211265,"mergeCommit":{"message":"[kbn-scout][maps] waitForRenderComplete (#211265)\n\n## Summary\n\nThis PR add a method to wait for map to be loaded to replace generic\n`renderable.waitForRender()`.\n\nWhile investigating the recent test failure on CI I found out that for\nmaps case we can simplify the logic with few facts:\n- before start waiting for render to complete, we need to wait for main\ncontainer `#maps-plugin` to be in DOM. It takes 2-3 seconds.\n- there is always a single div block with `data-render-complete`\nattribute, and there is a comment in source code stating `See if the\n\"data-render-complete\" attribute is \"true\". If so we're done!` which\nmeans we can simply wait for\n`div[data-dom-id][data-render-complete=\"true\"]`\n\n\n6de2ef0e6d/x-pack/platform/plugins/shared/maps/public/connected_components/map_container/map_container.tsx (L103-L116)\n\n`renderable.waitForRender()` is a good waiter, but probably for\ndashboard with multiple panels.","sha":"08400b1f4225bcc20b3c28262432ba269e117750"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>	2025-02-17 17:02:31 +01:00
Gerard Soldevila	9181d0cd1c	[8.x] SKA: Relocate new response-ops packages (#211241) (#211400) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Relocate new response-ops packages (#211241)](https://github.com/elastic/kibana/pull/211241) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-17T09:57:15Z","message":"SKA: Relocate new response-ops packages (#211241)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/response-ops-alerts-apis` |\r\n`src/platform/packages/shared/response-ops/alerts-apis` |\r\n| `@kbn/response-ops-alerts-fields-browser` |\r\n`src/platform/packages/shared/response-ops/alerts-fields-browser` |\r\n| `@kbn/response-ops-alerts-table` |\r\n`src/platform/packages/shared/response-ops/alerts-table` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./src/platform/packages/shared/response-ops/alerts-apis/jest.config.js\r\n./src/platform/packages/shared/response-ops/alerts-fields-browser/jest.config.js\r\n./src/platform/packages/shared/response-ops/alerts-table/jest.config.js\r\n./tsconfig.base.json\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/platform/packages/shared/response-ops/alerts-apis/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-apis/tsconfig.json:2\r\nsrc/platform/packages/shared/response-ops/alerts-fields-browser/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-fields-browser/tsconfig.json:2\r\nsrc/platform/packages/shared/response-ops/alerts-table/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-table/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>","sha":"e527f2b79a02d9f4b3eea00dad149c8b05ea85de","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"SKA: Relocate new response-ops packages","number":211241,"url":"https://github.com/elastic/kibana/pull/211241","mergeCommit":{"message":"SKA: Relocate new response-ops packages (#211241)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/response-ops-alerts-apis` |\r\n`src/platform/packages/shared/response-ops/alerts-apis` |\r\n| `@kbn/response-ops-alerts-fields-browser` |\r\n`src/platform/packages/shared/response-ops/alerts-fields-browser` |\r\n| `@kbn/response-ops-alerts-table` |\r\n`src/platform/packages/shared/response-ops/alerts-table` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./src/platform/packages/shared/response-ops/alerts-apis/jest.config.js\r\n./src/platform/packages/shared/response-ops/alerts-fields-browser/jest.config.js\r\n./src/platform/packages/shared/response-ops/alerts-table/jest.config.js\r\n./tsconfig.base.json\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/platform/packages/shared/response-ops/alerts-apis/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-apis/tsconfig.json:2\r\nsrc/platform/packages/shared/response-ops/alerts-fields-browser/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-fields-browser/tsconfig.json:2\r\nsrc/platform/packages/shared/response-ops/alerts-table/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-table/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>","sha":"e527f2b79a02d9f4b3eea00dad149c8b05ea85de"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211241","number":211241,"mergeCommit":{"message":"SKA: Relocate new response-ops packages (#211241)\n\n## Summary\r\n\r\nThis PR aims at relocating some of the Kibana modules (plugins and\r\npackages) into a new folder structure, according to the _Sustainable\r\nKibana Architecture_ initiative.\r\n\r\n> [!IMPORTANT]\r\n> * We kindly ask you to:\r\n> * Manually fix the errors in the error section below (if there are\r\nany).\r\n> * Search for the `packages[\\/\\\\]` and `plugins[\\/\\\\]` patterns in the\r\nsource code (Babel and Eslint config files), and update them\r\nappropriately.\r\n> * Manually review\r\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to ensure that\r\nany CI pipeline customizations continue to be correctly applied after\r\nthe changed path names\r\n> * Review all of the updated files, specially the `.ts` and `.js` files\r\nlisted in the sections below, as some of them contain relative paths\r\nthat have been updated.\r\n> * Think of potential impact of the move, including tooling and\r\nconfiguration files that can be pointing to the relocated modules. E.g.:\r\n> * customised eslint rules\r\n> * docs pointing to source code\r\n\r\n> [!NOTE]\r\n> * This PR has been auto-generated.\r\n> * Any manual contributions will be lost if the 'relocate' script is\r\nre-run.\r\n> * Try to obtain the missing reviews / approvals before applying manual\r\nfixes, and/or keep your changes in a .patch / git stash.\r\n> * Please use\r\n[#sustainable_kibana_architecture](https://elastic.slack.com/archives/C07TCKTA22E)\r\nSlack channel for feedback.\r\n\r\nAre you trying to rebase this PR to solve merge conflicts? Please follow\r\nthe steps describe\r\n[here](https://elastic.slack.com/archives/C07TCKTA22E/p1734019532879269?thread_ts=1734019339.935419&cid=C07TCKTA22E).\r\n\r\n#### 3 packages(s) are going to be relocated:\r\n\r\n| Id | Target folder |\r\n| -- | ------------- |\r\n| `@kbn/response-ops-alerts-apis` |\r\n`src/platform/packages/shared/response-ops/alerts-apis` |\r\n| `@kbn/response-ops-alerts-fields-browser` |\r\n`src/platform/packages/shared/response-ops/alerts-fields-browser` |\r\n| `@kbn/response-ops-alerts-table` |\r\n`src/platform/packages/shared/response-ops/alerts-table` |\r\n\r\n\r\n<details >\r\n<summary>Updated references</summary>\r\n\r\n```\r\n./package.json\r\n./packages/kbn-ts-projects/config-paths.json\r\n./src/platform/packages/private/kbn-repo-packages/package-map.json\r\n./src/platform/packages/shared/response-ops/alerts-apis/jest.config.js\r\n./src/platform/packages/shared/response-ops/alerts-fields-browser/jest.config.js\r\n./src/platform/packages/shared/response-ops/alerts-table/jest.config.js\r\n./tsconfig.base.json\r\n./yarn.lock\r\n.github/CODEOWNERS\r\n```\r\n\r\n</details><details >\r\n<summary>Updated relative paths</summary>\r\n\r\n```\r\nsrc/platform/packages/shared/response-ops/alerts-apis/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-apis/tsconfig.json:2\r\nsrc/platform/packages/shared/response-ops/alerts-fields-browser/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-fields-browser/tsconfig.json:2\r\nsrc/platform/packages/shared/response-ops/alerts-table/jest.config.js:12\r\nsrc/platform/packages/shared/response-ops/alerts-table/tsconfig.json:2\r\n```\r\n\r\n</details>\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Umberto Pepato <umbopepato@users.noreply.github.com>","sha":"e527f2b79a02d9f4b3eea00dad149c8b05ea85de"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-17 14:40:09 +01:00
Dzmitry Lemechko	a4e5dabf7f	[8.x] [Scout] add maps test (#204607) (#211350) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Scout] add maps test (#204607)](https://github.com/elastic/kibana/pull/204607) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tre","email":"wayne.seymour@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T11:55:35Z","message":"[Scout] add maps test (#204607)\n\n## Summary\r\n\r\nAdd MapsPage to the scout core to be re-used by others.\r\nAdd rudimentary docs to show how to run these tests.\r\nAdded a `waitForRender` method.\r\nAdd test id.\r\n\r\n---------\r\n\r\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>\r\nCo-authored-by: Nick Partridge <nicholas.partridge@elastic.co>\r\nCo-authored-by: Nick Partridge <nick.ryan.partridge@gmail.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>","sha":"ce1904533d46e3b1e02d0d177fe4503ad0e495df","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[Scout] add maps test","number":204607,"url":"https://github.com/elastic/kibana/pull/204607","mergeCommit":{"message":"[Scout] add maps test (#204607)\n\n## Summary\r\n\r\nAdd MapsPage to the scout core to be re-used by others.\r\nAdd rudimentary docs to show how to run these tests.\r\nAdded a `waitForRender` method.\r\nAdd test id.\r\n\r\n---------\r\n\r\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>\r\nCo-authored-by: Nick Partridge <nicholas.partridge@elastic.co>\r\nCo-authored-by: Nick Partridge <nick.ryan.partridge@gmail.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>","sha":"ce1904533d46e3b1e02d0d177fe4503ad0e495df"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/204607","number":204607,"mergeCommit":{"message":"[Scout] add maps test (#204607)\n\n## Summary\r\n\r\nAdd MapsPage to the scout core to be re-used by others.\r\nAdd rudimentary docs to show how to run these tests.\r\nAdded a `waitForRender` method.\r\nAdd test id.\r\n\r\n---------\r\n\r\nCo-authored-by: Robert Oskamp <traeluki@gmail.com>\r\nCo-authored-by: Nick Partridge <nicholas.partridge@elastic.co>\r\nCo-authored-by: Nick Partridge <nick.ryan.partridge@gmail.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>","sha":"ce1904533d46e3b1e02d0d177fe4503ad0e495df"}},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tre <wayne.seymour@elastic.co>	2025-02-17 13:51:34 +01:00
Kibana Machine	73a5339547	[8.x] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211285) ... # Backport This will backport the following commits from `main` to `8.x`: - [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)](https://github.com/elastic/kibana/pull/211231) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:07:41Z","message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin","number":211231,"url":"https://github.com/elastic/kibana/pull/211231","mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211231","number":211231,"mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}}]}] BACKPORT--> Co-authored-by: Tiago Costa <tiago.costa@elastic.co>	2025-02-14 17:33:07 +00:00
Karen Grigoryan	7ed5290798	[8.x] [Security Solution][Explore] Migrate from styled-components in shared (#210311) (#211224) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][Explore] Migrate from styled-components in shared (#210311)](https://github.com/elastic/kibana/pull/210311) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Karen Grigoryan","email":"karen.grigoryan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T16:14:34Z","message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0","v8.19.0"],"title":"[Security Solution][Explore] Migrate from styled-components in shared","number":210311,"url":"https://github.com/elastic/kibana/pull/210311","mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210311","number":210311,"mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-14 17:04:32 +01:00
Tiago Costa	6b8710abec	[8.x] chore(NA): upgrade to webpack 5 (#191106) (#211146) ... # Backport This will backport the following commits from `main` to `8.x`: - [chore(NA): upgrade to webpack 5 (#191106)](https://github.com/elastic/kibana/pull/191106) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T03:01:36Z","message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","v9.1.0"],"title":"chore(NA): upgrade to webpack 5","number":191106,"url":"https://github.com/elastic/kibana/pull/191106","mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211145","number":211145,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191106","number":191106,"mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-14 13:36:07 +00:00
Kibana Machine	88a796ea33	[8.x] [scout] enable authc debug logs for ES (#211055) (#211192) ... # Backport This will backport the following commits from `main` to `8.x`: - [[scout] enable authc debug logs for ES (#211055)](https://github.com/elastic/kibana/pull/211055) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T10:20:25Z","message":"[scout] enable authc debug logs for ES (#211055)\n\n## Summary\r\n\r\nTemporarily enabling ES authc debug logging to get more details for 401\r\nSAML callback response.","sha":"4f0eafc7c38e441ffa35cf822b042288d35d9ebe","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] enable authc debug logs for ES","number":211055,"url":"https://github.com/elastic/kibana/pull/211055","mergeCommit":{"message":"[scout] enable authc debug logs for ES (#211055)\n\n## Summary\r\n\r\nTemporarily enabling ES authc debug logging to get more details for 401\r\nSAML callback response.","sha":"4f0eafc7c38e441ffa35cf822b042288d35d9ebe"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211055","number":211055,"mergeCommit":{"message":"[scout] enable authc debug logs for ES (#211055)\n\n## Summary\r\n\r\nTemporarily enabling ES authc debug logging to get more details for 401\r\nSAML callback response.","sha":"4f0eafc7c38e441ffa35cf822b042288d35d9ebe"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>	2025-02-14 13:32:59 +01:00
Kibana Machine	9347de1cf4	[8.x] [kbn-test] retry 5xx in saml callback (#208977) (#211023) ... # Backport This will backport the following commits from `main` to `8.x`: - [[kbn-test] retry 5xx in saml callback (#208977)](https://github.com/elastic/kibana/pull/208977) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-06T17:39:47Z","message":"[kbn-test] retry 5xx in saml callback (#208977)\n\n## Summary\r\n\r\nWhen we run Scout tests in parallel, we call SAML authentication in\r\nparallel too and since by default `.security-profile-8` index does not\r\nexist, we periodically getting 503 response:\r\n\r\n```\r\n proc [kibana] [2025-01-29T11:13:10.420+01:00][ERROR][plugins.security.user-profile] \r\nFailed to activate user profile: {\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\r\n\"at least one search shard for the index [.security-profile-8] is unavailable\"}],\r\n\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard\r\nfor the index [.security-profile-8] is unavailable\"},\"status\":503}. {\"service\":{\"node\":\r\n{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n```\r\n\r\nThe solution is to retry the SAML callback assuming that index will be\r\ncreated and the issue will be solved.\r\nWe agreed with Kibana-Security to retry only **5xx** errors, because for\r\n**4xx** we most likely have to start the authentication from the start.\r\n\r\nFor reviews: it is not 100% reproducible, so I added unit tests to\r\nverify the retry logic is working only for 5xx requests. Please let me\r\nknow if I miss something\r\n\r\nRetry was verified locally, you might be seeing this logs output:\r\n\r\n```\r\n proc [kibana] [2025-01-30T18:40:41.348+01:00][ERROR][plugins.security.user-profile] Failed to activate user profile:\r\n{\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard for the index\r\n[.security-profile-8] is unavailable\"}],\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard\r\nfor the index [.security-profile-8] is unavailable\"},\"status\":503}. {\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n proc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][plugins.security.authentication] Login attempt with \"saml\"\r\nprovider failed due to unexpected error: {\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\r\n\"at least one search shard for the index [.security-profile-8] is unavailable\"}],\"type\":\"unavailable_shards_exception\",\r\n\"reason\":\"at least one search shard for the index [.security-profile-8] is unavailable\"},\"status\":503}\r\n{\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n proc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][http] 500 Server Error {\"http\":{\"response\":{\"status_code\":500},\"request\":{\"method\":\"post\",\"path\":\"/api/security/saml/callback\"}},\"error\":\r\n{\"message\":\"unavailable_shards_exception\\n\\tRoot causes:\\n\\t\\tunavailable_shards_exception: at least one\r\nsearch shard for the index [.security-profile-8] is\r\n ERROR [scout] SAML callback failed: expected 302, got 500\r\n Waiting 939 ms before the next attempt\r\n proc [playwright]\r\n info [o.e.c.r.a.AllocationService] [scout] current.health=\"GREEN\" message=\"Cluster health status changed\r\nfrom [YELLOW] to [GREEN] (reason: [shards started [[.security-profile-8][0]]]).\"\r\nprevious.health=\"YELLOW\" reason=\"shards started [[.security-profile-8][0]]\"\r\n```\r\n\r\nTo reproduce: \r\n```\r\nnode scripts/scout.js run-tests --stateful --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b5bbf8f86f0c6e0e05ab5e6381bba4919c64e33","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[kbn-test] retry 5xx in saml callback","number":208977,"url":"https://github.com/elastic/kibana/pull/208977","mergeCommit":{"message":"[kbn-test] retry 5xx in saml callback (#208977)\n\n## Summary\r\n\r\nWhen we run Scout tests in parallel, we call SAML authentication in\r\nparallel too and since by default `.security-profile-8` index does not\r\nexist, we periodically getting 503 response:\r\n\r\n```\r\n proc [kibana] [2025-01-29T11:13:10.420+01:00][ERROR][plugins.security.user-profile] \r\nFailed to activate user profile: {\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\r\n\"at least one search shard for the index [.security-profile-8] is unavailable\"}],\r\n\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard\r\nfor the index [.security-profile-8] is unavailable\"},\"status\":503}. {\"service\":{\"node\":\r\n{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n```\r\n\r\nThe solution is to retry the SAML callback assuming that index will be\r\ncreated and the issue will be solved.\r\nWe agreed with Kibana-Security to retry only **5xx** errors, because for\r\n**4xx** we most likely have to start the authentication from the start.\r\n\r\nFor reviews: it is not 100% reproducible, so I added unit tests to\r\nverify the retry logic is working only for 5xx requests. Please let me\r\nknow if I miss something\r\n\r\nRetry was verified locally, you might be seeing this logs output:\r\n\r\n```\r\n proc [kibana] [2025-01-30T18:40:41.348+01:00][ERROR][plugins.security.user-profile] Failed to activate user profile:\r\n{\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard for the index\r\n[.security-profile-8] is unavailable\"}],\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard\r\nfor the index [.security-profile-8] is unavailable\"},\"status\":503}. {\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n proc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][plugins.security.authentication] Login attempt with \"saml\"\r\nprovider failed due to unexpected error: {\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\r\n\"at least one search shard for the index [.security-profile-8] is unavailable\"}],\"type\":\"unavailable_shards_exception\",\r\n\"reason\":\"at least one search shard for the index [.security-profile-8] is unavailable\"},\"status\":503}\r\n{\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n proc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][http] 500 Server Error {\"http\":{\"response\":{\"status_code\":500},\"request\":{\"method\":\"post\",\"path\":\"/api/security/saml/callback\"}},\"error\":\r\n{\"message\":\"unavailable_shards_exception\\n\\tRoot causes:\\n\\t\\tunavailable_shards_exception: at least one\r\nsearch shard for the index [.security-profile-8] is\r\n ERROR [scout] SAML callback failed: expected 302, got 500\r\n Waiting 939 ms before the next attempt\r\n proc [playwright]\r\n info [o.e.c.r.a.AllocationService] [scout] current.health=\"GREEN\" message=\"Cluster health status changed\r\nfrom [YELLOW] to [GREEN] (reason: [shards started [[.security-profile-8][0]]]).\"\r\nprevious.health=\"YELLOW\" reason=\"shards started [[.security-profile-8][0]]\"\r\n```\r\n\r\nTo reproduce: \r\n```\r\nnode scripts/scout.js run-tests --stateful --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b5bbf8f86f0c6e0e05ab5e6381bba4919c64e33"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210085","number":210085,"state":"MERGED","mergeCommit":{"sha":"a51bfa88db6493a6b18f8def3908e10110e6c499","message":"[9.0] [kbn-test] retry 5xx in saml callback (#208977) (#210085)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[kbn-test] retry 5xx in saml callback\n(#208977)](https://github.com/elastic/kibana/pull/208977)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dzmitry\nLemechko\",\"email\":\"dzmitry.lemechko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-06T17:39:47Z\",\"message\":\"[kbn-test]\nretry 5xx in saml callback (#208977)\\n\\n## Summary\\r\\n\\r\\nWhen we run\nScout tests in parallel, we call SAML authentication in\\r\\nparallel too\nand since by default `.security-profile-8` index does not\\r\\nexist, we\nperiodically getting 503 response:\\r\\n\\r\\n```\\r\\n proc [kibana]\n[2025-01-29T11:13:10.420+01:00][ERROR][plugins.security.user-profile]\n\\r\\nFailed to activate user profile:\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\r\\n\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"}],\\r\\n\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard\\r\\nfor the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}.\n{\\\"service\\\":{\\\"node\\\":\\r\\n{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n```\\r\\n\\r\\nThe\nsolution is to retry the SAML callback assuming that index will\nbe\\r\\ncreated and the issue will be solved.\\r\\nWe agreed with\nKibana-Security to retry only **5xx** errors, because for\\r\\n**4xx** we\nmost likely have to start the authentication from the start.\\r\\n\\r\\nFor\nreviews: it is not 100% reproducible, so I added unit tests to\\r\\nverify\nthe retry logic is working only for 5xx requests. Please let me\\r\\nknow\nif I miss something\\r\\n\\r\\nRetry was verified locally, you might be\nseeing this logs output:\\r\\n\\r\\n```\\r\\n proc [kibana]\n[2025-01-30T18:40:41.348+01:00][ERROR][plugins.security.user-profile]\nFailed to activate user\nprofile:\\r\\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard for the index\\r\\n[.security-profile-8] is\nunavailable\\\"}],\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard\\r\\nfor the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}.\n{\\\"service\\\":{\\\"node\\\":{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n\nproc [kibana]\n[2025-01-30T18:40:41.349+01:00][ERROR][plugins.security.authentication]\nLogin attempt with \\\"saml\\\"\\r\\nprovider failed due to unexpected error:\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\r\\n\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"}],\\\"type\\\":\\\"unavailable_shards_exception\\\",\\r\\n\\\"reason\\\":\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}\\r\\n{\\\"service\\\":{\\\"node\\\":{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n\nproc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][http] 500 Server\nError\n{\\\"http\\\":{\\\"response\\\":{\\\"status_code\\\":500},\\\"request\\\":{\\\"method\\\":\\\"post\\\",\\\"path\\\":\\\"/api/security/saml/callback\\\"}},\\\"error\\\":\\r\\n{\\\"message\\\":\\\"unavailable_shards_exception\\\\n\\\\tRoot\ncauses:\\\\n\\\\t\\\\tunavailable_shards_exception: at least one\\r\\nsearch\nshard for the index [.security-profile-8] is\\r\\n ERROR [scout] SAML\ncallback failed: expected 302, got 500\\r\\n Waiting 939 ms before the\nnext attempt\\r\\n proc [playwright]\\r\\n info\n[o.e.c.r.a.AllocationService] [scout] current.health=\\\"GREEN\\\"\nmessage=\\\"Cluster health status changed\\r\\nfrom [YELLOW] to [GREEN]\n(reason: [shards started\n[[.security-profile-8][0]]]).\\\"\\r\\nprevious.health=\\\"YELLOW\\\"\nreason=\\\"shards started [[.security-profile-8][0]]\\\"\\r\\n```\\r\\n\\r\\nTo\nreproduce: \\r\\n```\\r\\nnode scripts/scout.js run-tests --stateful\n--config\nx-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\\r\\n```\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"2b5bbf8f86f0c6e0e05ab5e6381bba4919c64e33\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"test:scout\",\"v9.1.0\"],\"title\":\"[kbn-test]\nretry 5xx in saml\ncallback\",\"number\":208977,\"url\":\"https://github.com/elastic/kibana/pull/208977\",\"mergeCommit\":{\"message\":\"[kbn-test]\nretry 5xx in saml callback (#208977)\\n\\n## Summary\\r\\n\\r\\nWhen we run\nScout tests in parallel, we call SAML authentication in\\r\\nparallel too\nand since by default `.security-profile-8` index does not\\r\\nexist, we\nperiodically getting 503 response:\\r\\n\\r\\n```\\r\\n proc [kibana]\n[2025-01-29T11:13:10.420+01:00][ERROR][plugins.security.user-profile]\n\\r\\nFailed to activate user profile:\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\r\\n\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"}],\\r\\n\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard\\r\\nfor the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}.\n{\\\"service\\\":{\\\"node\\\":\\r\\n{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n```\\r\\n\\r\\nThe\nsolution is to retry the SAML callback assuming that index will\nbe\\r\\ncreated and the issue will be solved.\\r\\nWe agreed with\nKibana-Security to retry only **5xx** errors, because for\\r\\n**4xx** we\nmost likely have to start the authentication from the start.\\r\\n\\r\\nFor\nreviews: it is not 100% reproducible, so I added unit tests to\\r\\nverify\nthe retry logic is working only for 5xx requests. Please let me\\r\\nknow\nif I miss something\\r\\n\\r\\nRetry was verified locally, you might be\nseeing this logs output:\\r\\n\\r\\n```\\r\\n proc [kibana]\n[2025-01-30T18:40:41.348+01:00][ERROR][plugins.security.user-profile]\nFailed to activate user\nprofile:\\r\\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard for the index\\r\\n[.security-profile-8] is\nunavailable\\\"}],\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard\\r\\nfor the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}.\n{\\\"service\\\":{\\\"node\\\":{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n\nproc [kibana]\n[2025-01-30T18:40:41.349+01:00][ERROR][plugins.security.authentication]\nLogin attempt with \\\"saml\\\"\\r\\nprovider failed due to unexpected error:\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\r\\n\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"}],\\\"type\\\":\\\"unavailable_shards_exception\\\",\\r\\n\\\"reason\\\":\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}\\r\\n{\\\"service\\\":{\\\"node\\\":{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n\nproc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][http] 500 Server\nError\n{\\\"http\\\":{\\\"response\\\":{\\\"status_code\\\":500},\\\"request\\\":{\\\"method\\\":\\\"post\\\",\\\"path\\\":\\\"/api/security/saml/callback\\\"}},\\\"error\\\":\\r\\n{\\\"message\\\":\\\"unavailable_shards_exception\\\\n\\\\tRoot\ncauses:\\\\n\\\\t\\\\tunavailable_shards_exception: at least one\\r\\nsearch\nshard for the index [.security-profile-8] is\\r\\n ERROR [scout] SAML\ncallback failed: expected 302, got 500\\r\\n Waiting 939 ms before the\nnext attempt\\r\\n proc [playwright]\\r\\n info\n[o.e.c.r.a.AllocationService] [scout] current.health=\\\"GREEN\\\"\nmessage=\\\"Cluster health status changed\\r\\nfrom [YELLOW] to [GREEN]\n(reason: [shards started\n[[.security-profile-8][0]]]).\\\"\\r\\nprevious.health=\\\"YELLOW\\\"\nreason=\\\"shards started [[.security-profile-8][0]]\\\"\\r\\n```\\r\\n\\r\\nTo\nreproduce: \\r\\n```\\r\\nnode scripts/scout.js run-tests --stateful\n--config\nx-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\\r\\n```\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"2b5bbf8f86f0c6e0e05ab5e6381bba4919c64e33\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/208977\",\"number\":208977,\"mergeCommit\":{\"message\":\"[kbn-test]\nretry 5xx in saml callback (#208977)\\n\\n## Summary\\r\\n\\r\\nWhen we run\nScout tests in parallel, we call SAML authentication in\\r\\nparallel too\nand since by default `.security-profile-8` index does not\\r\\nexist, we\nperiodically getting 503 response:\\r\\n\\r\\n```\\r\\n proc [kibana]\n[2025-01-29T11:13:10.420+01:00][ERROR][plugins.security.user-profile]\n\\r\\nFailed to activate user profile:\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\r\\n\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"}],\\r\\n\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard\\r\\nfor the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}.\n{\\\"service\\\":{\\\"node\\\":\\r\\n{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n```\\r\\n\\r\\nThe\nsolution is to retry the SAML callback assuming that index will\nbe\\r\\ncreated and the issue will be solved.\\r\\nWe agreed with\nKibana-Security to retry only **5xx** errors, because for\\r\\n**4xx** we\nmost likely have to start the authentication from the start.\\r\\n\\r\\nFor\nreviews: it is not 100% reproducible, so I added unit tests to\\r\\nverify\nthe retry logic is working only for 5xx requests. Please let me\\r\\nknow\nif I miss something\\r\\n\\r\\nRetry was verified locally, you might be\nseeing this logs output:\\r\\n\\r\\n```\\r\\n proc [kibana]\n[2025-01-30T18:40:41.348+01:00][ERROR][plugins.security.user-profile]\nFailed to activate user\nprofile:\\r\\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard for the index\\r\\n[.security-profile-8] is\nunavailable\\\"}],\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\\"at\nleast one search shard\\r\\nfor the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}.\n{\\\"service\\\":{\\\"node\\\":{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n\nproc [kibana]\n[2025-01-30T18:40:41.349+01:00][ERROR][plugins.security.authentication]\nLogin attempt with \\\"saml\\\"\\r\\nprovider failed due to unexpected error:\n{\\\"error\\\":{\\\"root_cause\\\":[{\\\"type\\\":\\\"unavailable_shards_exception\\\",\\\"reason\\\":\\r\\n\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"}],\\\"type\\\":\\\"unavailable_shards_exception\\\",\\r\\n\\\"reason\\\":\\\"at\nleast one search shard for the index [.security-profile-8] is\nunavailable\\\"},\\\"status\\\":503}\\r\\n{\\\"service\\\":{\\\"node\\\":{\\\"roles\\\":[\\\"background_tasks\\\",\\\"ui\\\"]}}}\\r\\n\nproc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][http] 500 Server\nError\n{\\\"http\\\":{\\\"response\\\":{\\\"status_code\\\":500},\\\"request\\\":{\\\"method\\\":\\\"post\\\",\\\"path\\\":\\\"/api/security/saml/callback\\\"}},\\\"error\\\":\\r\\n{\\\"message\\\":\\\"unavailable_shards_exception\\\\n\\\\tRoot\ncauses:\\\\n\\\\t\\\\tunavailable_shards_exception: at least one\\r\\nsearch\nshard for the index [.security-profile-8] is\\r\\n ERROR [scout] SAML\ncallback failed: expected 302, got 500\\r\\n Waiting 939 ms before the\nnext attempt\\r\\n proc [playwright]\\r\\n info\n[o.e.c.r.a.AllocationService] [scout] current.health=\\\"GREEN\\\"\nmessage=\\\"Cluster health status changed\\r\\nfrom [YELLOW] to [GREEN]\n(reason: [shards started\n[[.security-profile-8][0]]]).\\\"\\r\\nprevious.health=\\\"YELLOW\\\"\nreason=\\\"shards started [[.security-profile-8][0]]\\\"\\r\\n```\\r\\n\\r\\nTo\nreproduce: \\r\\n```\\r\\nnode scripts/scout.js run-tests --stateful\n--config\nx-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\\r\\n```\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<42973632+kibanamachine@users.noreply.github.com>\",\"sha\":\"2b5bbf8f86f0c6e0e05ab5e6381bba4919c64e33\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208977","number":208977,"mergeCommit":{"message":"[kbn-test] retry 5xx in saml callback (#208977)\n\n## Summary\r\n\r\nWhen we run Scout tests in parallel, we call SAML authentication in\r\nparallel too and since by default `.security-profile-8` index does not\r\nexist, we periodically getting 503 response:\r\n\r\n```\r\n proc [kibana] [2025-01-29T11:13:10.420+01:00][ERROR][plugins.security.user-profile] \r\nFailed to activate user profile: {\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\r\n\"at least one search shard for the index [.security-profile-8] is unavailable\"}],\r\n\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard\r\nfor the index [.security-profile-8] is unavailable\"},\"status\":503}. {\"service\":{\"node\":\r\n{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n```\r\n\r\nThe solution is to retry the SAML callback assuming that index will be\r\ncreated and the issue will be solved.\r\nWe agreed with Kibana-Security to retry only **5xx** errors, because for\r\n**4xx** we most likely have to start the authentication from the start.\r\n\r\nFor reviews: it is not 100% reproducible, so I added unit tests to\r\nverify the retry logic is working only for 5xx requests. Please let me\r\nknow if I miss something\r\n\r\nRetry was verified locally, you might be seeing this logs output:\r\n\r\n```\r\n proc [kibana] [2025-01-30T18:40:41.348+01:00][ERROR][plugins.security.user-profile] Failed to activate user profile:\r\n{\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard for the index\r\n[.security-profile-8] is unavailable\"}],\"type\":\"unavailable_shards_exception\",\"reason\":\"at least one search shard\r\nfor the index [.security-profile-8] is unavailable\"},\"status\":503}. {\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n proc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][plugins.security.authentication] Login attempt with \"saml\"\r\nprovider failed due to unexpected error: {\"error\":{\"root_cause\":[{\"type\":\"unavailable_shards_exception\",\"reason\":\r\n\"at least one search shard for the index [.security-profile-8] is unavailable\"}],\"type\":\"unavailable_shards_exception\",\r\n\"reason\":\"at least one search shard for the index [.security-profile-8] is unavailable\"},\"status\":503}\r\n{\"service\":{\"node\":{\"roles\":[\"background_tasks\",\"ui\"]}}}\r\n proc [kibana] [2025-01-30T18:40:41.349+01:00][ERROR][http] 500 Server Error {\"http\":{\"response\":{\"status_code\":500},\"request\":{\"method\":\"post\",\"path\":\"/api/security/saml/callback\"}},\"error\":\r\n{\"message\":\"unavailable_shards_exception\\n\\tRoot causes:\\n\\t\\tunavailable_shards_exception: at least one\r\nsearch shard for the index [.security-profile-8] is\r\n ERROR [scout] SAML callback failed: expected 302, got 500\r\n Waiting 939 ms before the next attempt\r\n proc [playwright]\r\n info [o.e.c.r.a.AllocationService] [scout] current.health=\"GREEN\" message=\"Cluster health status changed\r\nfrom [YELLOW] to [GREEN] (reason: [shards started [[.security-profile-8][0]]]).\"\r\nprevious.health=\"YELLOW\" reason=\"shards started [[.security-profile-8][0]]\"\r\n```\r\n\r\nTo reproduce: \r\n```\r\nnode scripts/scout.js run-tests --stateful --config x-pack/platform/plugins/private/discover_enhanced/ui_tests/parallel.playwright.config.ts\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"2b5bbf8f86f0c6e0e05ab5e6381bba4919c64e33"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>	2025-02-13 20:54:28 +01:00
Karen Grigoryan	12738e9f5f	[8.x] [Security Solution] [EUI Refresh] styled component migration Dashboards (#208731) (#210967) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)](https://github.com/elastic/kibana/pull/208731) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Agustina Nahir Ruidiaz","email":"61565784+agusruidiazgd@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T15:05:27Z","message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Explore","ci:cloud-deploy","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0","v8.19.0"],"title":"[Security Solution] [EUI Refresh] styled component migration Dashboards","number":208731,"url":"https://github.com/elastic/kibana/pull/208731","mergeCommit":{"message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210886","number":210886,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/208731","number":208731,"mergeCommit":{"message":"[Security Solution] [EUI Refresh] styled component migration Dashboards (#208731)\n\n## Summary\r\n\r\nAddresses https://github.com/elastic/kibana/issues/206439\r\nThis PR migrates explore page from styled-components to @emotion/styled.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\nhttps://github.com/user-attachments/assets/6cdfbf15-9a77-488c-a0b9-42acc3fe1768\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>","sha":"f92e50a4a1d9bdea781d1e0fb45b4f8560a27ab5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Agustina Nahir Ruidiaz <61565784+agusruidiazgd@users.noreply.github.com>	2025-02-13 16:37:28 +01:00
Umberto Pepato	f1d15570a9	[8.x] [ResponseOps][Alerts] Move the alerts table to a dedicated package (#207878) (#210895) ... # Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Alerts] Move the alerts table to a dedicated package (#207878)](https://github.com/elastic/kibana/pull/207878) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Umberto Pepato","email":"umbopepato@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T10:07:55Z","message":"[ResponseOps][Alerts] Move the alerts table to a dedicated package (#207878)\n\n## Summary\r\n\r\nThis PR turns the AlertsTable into a standalone component, making it\r\nindependent from the `TriggersActionsUI` plugin.\r\n\r\n#### Removes the alerts table registry\r\n\r\nAll configuration is now managed through the AlertsTable component\r\nprops. Shared configurations are handled by giving consumers the ability\r\nto directly provide alerts table wrapper components (see for example the\r\n`renderAlertsTable` prop of `getCases`).\r\n\r\n#### Moves the alerts table to dedicated package(s)\r\n\r\nFollowing the feature-driven structure we're introducing for ResponseOps\r\n(alerting) client-side packages:\r\n- `@kbn/response-ops-alerts-table`\r\n- `@kbn/response-ops-alerts-apis`\r\n- `@kbn/response-ops-alerts-fields-browser`\r\n\r\n#### Initial work on improving composition and organization\r\n\r\n- Reorganizes the table code into a by-entity-type folder structure\r\n(`components/`, `hooks/`, ...)\r\n- Simplifies some components and breaks into smaller units when possible\r\n\r\n## To verify\r\n\r\nFor consumers of the alerts table:\r\n- Check that all your tables have the same behavior as before (columns,\r\nsort, row actions, bulk actions, etc.)\r\n- Check that your \"shared\" tables (i.e. cases alerts view in O11y and\r\nSecurity) have the expected configuration and behavior\r\n\r\n> [!WARNING]\r\n> This PR moves a lot of files. Git might not always recognize the\r\ncorrect delete/add file pairs. If you see weird diffs feel free to reach\r\nout for help!\r\n\r\n### Checklist\r\n\r\n- [x]\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- [x] [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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n### Identify risks\r\n\r\n| Risk | Description | Severity | Mitigation |\r\n|---|---|---|---|\r\n| Table misconfigurations | Some table configurations might slightly\r\ndiffer from the previous AlertsTableRegistry-backed version | Low |\r\nQuick fix |\r\n\r\n## References\r\n\r\nCloses #195180\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Christos Nasikas <xristosnasikas@gmail.com>","sha":"a74066d6f83fc38feaa4d7e7b1cf7d3afd53c6f7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","backport:version","v9.1.0","v8.19.0"],"title":"[ResponseOps][Alerts] Move the alerts table to a dedicated package","number":207878,"url":"https://github.com/elastic/kibana/pull/207878","mergeCommit":{"message":"[ResponseOps][Alerts] Move the alerts table to a dedicated package (#207878)\n\n## Summary\r\n\r\nThis PR turns the AlertsTable into a standalone component, making it\r\nindependent from the `TriggersActionsUI` plugin.\r\n\r\n#### Removes the alerts table registry\r\n\r\nAll configuration is now managed through the AlertsTable component\r\nprops. Shared configurations are handled by giving consumers the ability\r\nto directly provide alerts table wrapper components (see for example the\r\n`renderAlertsTable` prop of `getCases`).\r\n\r\n#### Moves the alerts table to dedicated package(s)\r\n\r\nFollowing the feature-driven structure we're introducing for ResponseOps\r\n(alerting) client-side packages:\r\n- `@kbn/response-ops-alerts-table`\r\n- `@kbn/response-ops-alerts-apis`\r\n- `@kbn/response-ops-alerts-fields-browser`\r\n\r\n#### Initial work on improving composition and organization\r\n\r\n- Reorganizes the table code into a by-entity-type folder structure\r\n(`components/`, `hooks/`, ...)\r\n- Simplifies some components and breaks into smaller units when possible\r\n\r\n## To verify\r\n\r\nFor consumers of the alerts table:\r\n- Check that all your tables have the same behavior as before (columns,\r\nsort, row actions, bulk actions, etc.)\r\n- Check that your \"shared\" tables (i.e. cases alerts view in O11y and\r\nSecurity) have the expected configuration and behavior\r\n\r\n> [!WARNING]\r\n> This PR moves a lot of files. Git might not always recognize the\r\ncorrect delete/add file pairs. If you see weird diffs feel free to reach\r\nout for help!\r\n\r\n### Checklist\r\n\r\n- [x]\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- [x] [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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n### Identify risks\r\n\r\n| Risk | Description | Severity | Mitigation |\r\n|---|---|---|---|\r\n| Table misconfigurations | Some table configurations might slightly\r\ndiffer from the previous AlertsTableRegistry-backed version | Low |\r\nQuick fix |\r\n\r\n## References\r\n\r\nCloses #195180\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Christos Nasikas <xristosnasikas@gmail.com>","sha":"a74066d6f83fc38feaa4d7e7b1cf7d3afd53c6f7"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207878","number":207878,"mergeCommit":{"message":"[ResponseOps][Alerts] Move the alerts table to a dedicated package (#207878)\n\n## Summary\r\n\r\nThis PR turns the AlertsTable into a standalone component, making it\r\nindependent from the `TriggersActionsUI` plugin.\r\n\r\n#### Removes the alerts table registry\r\n\r\nAll configuration is now managed through the AlertsTable component\r\nprops. Shared configurations are handled by giving consumers the ability\r\nto directly provide alerts table wrapper components (see for example the\r\n`renderAlertsTable` prop of `getCases`).\r\n\r\n#### Moves the alerts table to dedicated package(s)\r\n\r\nFollowing the feature-driven structure we're introducing for ResponseOps\r\n(alerting) client-side packages:\r\n- `@kbn/response-ops-alerts-table`\r\n- `@kbn/response-ops-alerts-apis`\r\n- `@kbn/response-ops-alerts-fields-browser`\r\n\r\n#### Initial work on improving composition and organization\r\n\r\n- Reorganizes the table code into a by-entity-type folder structure\r\n(`components/`, `hooks/`, ...)\r\n- Simplifies some components and breaks into smaller units when possible\r\n\r\n## To verify\r\n\r\nFor consumers of the alerts table:\r\n- Check that all your tables have the same behavior as before (columns,\r\nsort, row actions, bulk actions, etc.)\r\n- Check that your \"shared\" tables (i.e. cases alerts view in O11y and\r\nSecurity) have the expected configuration and behavior\r\n\r\n> [!WARNING]\r\n> This PR moves a lot of files. Git might not always recognize the\r\ncorrect delete/add file pairs. If you see weird diffs feel free to reach\r\nout for help!\r\n\r\n### Checklist\r\n\r\n- [x]\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- [x] [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- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n### Identify risks\r\n\r\n| Risk | Description | Severity | Mitigation |\r\n|---|---|---|---|\r\n| Table misconfigurations | Some table configurations might slightly\r\ndiffer from the previous AlertsTableRegistry-backed version | Low |\r\nQuick fix |\r\n\r\n## References\r\n\r\nCloses #195180\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Christos Nasikas <xristosnasikas@gmail.com>","sha":"a74066d6f83fc38feaa4d7e7b1cf7d3afd53c6f7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-13 16:12:15 +01:00
Dzmitry Lemechko	81b5e2d452	[8.x] [kbn-test] error message if MFA is enabled for test account (#196906) (#210984) ... # Backport This will backport the following commits from `main` to `8.x`: - [[kbn-test] error message if MFA is enabled for test account (#196906)](https://github.com/elastic/kibana/pull/196906) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2024-10-21T11:41:00Z","message":"[kbn-test] error message if MFA is enabled for test account (#196906)\n\n## Summary\r\n\r\nRecently few engineers reported issues when running FTR **locally**\r\nagainst MKI project on QA env. It turned out MFA was enabled for the\r\ntest cloud accounts, that breaks automatic login to the Cloud.\r\n\r\nThis PR checks response for `mfa_required: true` and fails without\r\nretrying asking to disable MFA for test account.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63ebd41c6c88cedc39a70079a70580027836eabd","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0"],"title":"[kbn-test] error message if MFA is enabled for test account","number":196906,"url":"https://github.com/elastic/kibana/pull/196906","mergeCommit":{"message":"[kbn-test] error message if MFA is enabled for test account (#196906)\n\n## Summary\r\n\r\nRecently few engineers reported issues when running FTR **locally**\r\nagainst MKI project on QA env. It turned out MFA was enabled for the\r\ntest cloud accounts, that breaks automatic login to the Cloud.\r\n\r\nThis PR checks response for `mfa_required: true` and fails without\r\nretrying asking to disable MFA for test account.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63ebd41c6c88cedc39a70079a70580027836eabd"}},"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/196906","number":196906,"mergeCommit":{"message":"[kbn-test] error message if MFA is enabled for test account (#196906)\n\n## Summary\r\n\r\nRecently few engineers reported issues when running FTR **locally**\r\nagainst MKI project on QA env. It turned out MFA was enabled for the\r\ntest cloud accounts, that breaks automatic login to the Cloud.\r\n\r\nThis PR checks response for `mfa_required: true` and fails without\r\nretrying asking to disable MFA for test account.\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"63ebd41c6c88cedc39a70079a70580027836eabd"}}]}] BACKPORT-->	2025-02-13 14:24:25 +01:00
Angela Chuang	a7b2f9a6e6	[8.x] [Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631) (#210565) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)](https://github.com/elastic/kibana/pull/204631) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-09T12:46:55Z","message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","v9.0.0","ci:cloud-deploy","EUI Visual Refresh"],"title":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex","number":204631,"url":"https://github.com/elastic/kibana/pull/204631","mergeCommit":{"message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85"}},"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/204631","number":204631,"mergeCommit":{"message":"[Security Solution][threat hunting explore] EUI refresh: Remove custom color hex (#204631)\n\n## Summary\r\n\r\nhttps://github.com/elastic/kibana/issues/202498\r\nhttps://github.com/elastic/kibana/issues/202503\r\n\r\n1. This PR does **Not** include the severity color change. It will be\r\nimplemented in a follow up PR once color tokens have been decided.\r\n2. This PR updates the type `GetLensAttributes` to accept `euiTheme`, so\r\nall the functions in this type are updated accordingly.\r\n\r\nhttps://github.com/elastic/kibana/pull/204631/files#diff-abe20658865cad59eadcff945552b40832d96da0264ed89ddd5ab25ded1420a3R30\r\n\r\n----\r\n\r\n## To test:\r\n\r\nPlease verify if visualizations are displayed properly.\r\n\r\n### Running Kibana with the Borealis theme\r\nIn order to run Kibana with `Borealis`, you'll need to do the following:\r\n\r\n1. Set the following in kibana.dev.yml:\r\n`uiSettings.experimental.themeSwitcherEnabled: true`\r\n4. Run Kibana with the following environment variable set: \r\n```KBN_OPTIMIZER_THEMES=\"borealislight,borealisdark,v8light,v8dark\" yarn start```\r\n\r\n5. This will expose a toggle under Stack Management > Advanced Settings > Theme version, which you can use to toggle between Amsterdam and Borealis.\r\n\r\n\r\n\r\n\r\n----\r\n\r\n\r\n### Explore\r\n\r\n\r\n<img width=\"2557\" alt=\"host_after\" src=\"https://github.com/user-attachments/assets/f69b6e2a-58f6-4ed4-9f38-dcdbcf9919ed\" />\r\n<img width=\"1281\" alt=\"users_after\" src=\"https://github.com/user-attachments/assets/0eec8e9c-e678-4a66-83ee-4b8d11380b8e\" />\r\n<img width=\"2552\" alt=\"network_dns\" src=\"https://github.com/user-attachments/assets/19f06d2a-6e51-419b-9f89-233bfa5727ba\" />\r\n<img width=\"2557\" alt=\"network_after\" src=\"https://github.com/user-attachments/assets/3b90c5e2-23a1-4f15-a2d0-f9290a39af30\" />\r\n\r\n----\r\n\r\n### Dashboards\r\n\r\n<img width=\"2557\" alt=\"dashboard_overview\" src=\"https://github.com/user-attachments/assets/c1873359-fee9-42c6-addd-fe2bc1c98aee\" />\r\n<img width=\"2558\" alt=\"dashboard_detection_response_2\" src=\"https://github.com/user-attachments/assets/f6853710-0938-402b-b326-fa00d586b5d6\" />\r\n<img width=\"2559\" alt=\"dashboard_detection_response_1\" src=\"https://github.com/user-attachments/assets/4eb75526-9a57-46e9-b090-b53353956ea1\" />\r\n\r\n----\r\n\r\n\r\n### Alerts\r\n<img width=\"2555\" alt=\"alerts_chart_collapsed\" src=\"https://github.com/user-attachments/assets/6ecf5dd5-a785-4701-900b-0454f024b36d\" />\r\n<img width=\"2554\" alt=\"summary\" src=\"https://github.com/user-attachments/assets/1731a6ea-ef2b-4d7d-bf21-4041e59f0ad4\" />\r\n<img width=\"2559\" alt=\"trend\" src=\"https://github.com/user-attachments/assets/b9a741d1-a359-4273-9555-850cdcbc8932\" />\r\n<img width=\"2557\" alt=\"counts\" src=\"https://github.com/user-attachments/assets/a6193ccc-86b8-4974-ad9f-9417e200e859\" />\r\n<img width=\"1281\" alt=\"treemap\" src=\"https://github.com/user-attachments/assets/7b6e163a-a660-4bb1-a6de-88e21934b98a\" />\r\n\r\n----\r\n\r\n### Rules preview\r\n<img width=\"2556\" alt=\"Screenshot 2024-12-18 at 13 45 33\" src=\"https://github.com/user-attachments/assets/47099c18-86ee-455a-a5af-ebd6a29904a5\" />\r\n\r\n\r\n----\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"78dfe5f81e8307aea2233a109401489828840b85"}}]}] BACKPORT-->	2025-02-13 13:31:09 +01:00
Jared Burgett	6e2891d62b	[8.x] [Entity Analytics] Consider Closed alerts for Risk Scoring (#193667) (#210940) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)](https://github.com/elastic/kibana/pull/193667) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-10-08T07:28:54Z","message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"93f03e5939c897c620b36595e5fcc67e74340e38","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","backport","v9.0.0","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Entity Analytics] Consider Closed alerts for Risk Scoring","number":193667,"url":"https://github.com/elastic/kibana/pull/193667","mergeCommit":{"message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"93f03e5939c897c620b36595e5fcc67e74340e38"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/193667","number":193667,"mergeCommit":{"message":"[Entity Analytics] Consider Closed alerts for Risk Scoring (#193667)\n\n## Summary\r\n\r\n- The changes included in this PR allows the alerts in closed state to\r\nbe included in risk score calculation.\r\n- It also includes the changes to backfill existing data with the\r\nrequired key so that older alerts could also be considered for risk\r\nscore calculation if need be.\r\n- Unit tests and integration tests are also included for the\r\nchanges.Tests for backfill changes are not included in this PR\r\n\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [x] [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- [x] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"93f03e5939c897c620b36595e5fcc67e74340e38"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.1","label":"v9.1.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com>	2025-02-13 11:20:39 +05:30
Robert Oskamp	84c90d5bb4	[8.x] [kbn-scout] add test config category to reporting (#210167) (#210802) ... # Backport This will backport the following commits from `main` to `8.x`: - [[kbn-scout] add test config category to reporting (#210167)](https://github.com/elastic/kibana/pull/210167) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Robert Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T10:17:04Z","message":"[kbn-scout] add test config category to reporting (#210167)\n\n## Summary\r\n\r\nThis PR adds a test config category to the scout reporting. This allows\r\nus to distinguish between UI and API FTR tests.\r\nA new property `testConfigCategory` has been added to all FTR configs\r\nthat don't already inherit it from a higher level config.","sha":"4bd80160b24fc2d136608d95e320291d3074eba2","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","ci:project-deploy-observability","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0"],"title":"[kbn-scout] add test config category to reporting","number":210167,"url":"https://github.com/elastic/kibana/pull/210167","mergeCommit":{"message":"[kbn-scout] add test config category to reporting (#210167)\n\n## Summary\r\n\r\nThis PR adds a test config category to the scout reporting. This allows\r\nus to distinguish between UI and API FTR tests.\r\nA new property `testConfigCategory` has been added to all FTR configs\r\nthat don't already inherit it from a higher level config.","sha":"4bd80160b24fc2d136608d95e320291d3074eba2"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210167","number":210167,"mergeCommit":{"message":"[kbn-scout] add test config category to reporting (#210167)\n\n## Summary\r\n\r\nThis PR adds a test config category to the scout reporting. This allows\r\nus to distinguish between UI and API FTR tests.\r\nA new property `testConfigCategory` has been added to all FTR configs\r\nthat don't already inherit it from a higher level config.","sha":"4bd80160b24fc2d136608d95e320291d3074eba2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT-->	2025-02-12 14:34:12 +01:00
Kibana Machine	fae24a980f	[8.x] [Security Solution][THI] remove usages of EUI json tokens (#210482) (#210700) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution][THI] remove usages of EUI json tokens (#210482)](https://github.com/elastic/kibana/pull/210482) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T21:11:55Z","message":"[Security Solution][THI] remove usages of EUI json tokens (#210482)\n\n## Summary\r\n\r\nThis PR is probably the final PR that makes the changes to support EUI\r\nBorealis. It focuses on removing all the usage of EUI Json tokens.\r\n\r\nYou will notice different approaches while removing the tokens:\r\n- for some cases, the changes were done using `css from\r\n'@emotions/react'` as the components using the tokens were already using\r\n`euiTheme` or adding it was straightforward and required the minimal\r\namount of changes\r\n- for some cases, where the css changes were pretty involved, a hook was\r\ncreated to be able to import the styles and apply them in the components\r\n- finally for other cases, esepcially if the styled components were\r\nextracted in a different file and were used within many others, I\r\ndecided to create reusable components. This allowed to not change all\r\nthe files impacted and limit the number of files modified in this PR.\r\n\r\nFeel free to comment on any of the approaches and suggest better\r\noptions!\r\n\r\nhttps://github.com/elastic/kibana/issues/201889\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"161ce34cf7f38faed884421976b10494df0a4075","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat Hunting:Investigations","backport:version","v9.1.0","v8.19.0"],"title":"[Security Solution][THI] remove usages of EUI json tokens","number":210482,"url":"https://github.com/elastic/kibana/pull/210482","mergeCommit":{"message":"[Security Solution][THI] remove usages of EUI json tokens (#210482)\n\n## Summary\r\n\r\nThis PR is probably the final PR that makes the changes to support EUI\r\nBorealis. It focuses on removing all the usage of EUI Json tokens.\r\n\r\nYou will notice different approaches while removing the tokens:\r\n- for some cases, the changes were done using `css from\r\n'@emotions/react'` as the components using the tokens were already using\r\n`euiTheme` or adding it was straightforward and required the minimal\r\namount of changes\r\n- for some cases, where the css changes were pretty involved, a hook was\r\ncreated to be able to import the styles and apply them in the components\r\n- finally for other cases, esepcially if the styled components were\r\nextracted in a different file and were used within many others, I\r\ndecided to create reusable components. This allowed to not change all\r\nthe files impacted and limit the number of files modified in this PR.\r\n\r\nFeel free to comment on any of the approaches and suggest better\r\noptions!\r\n\r\nhttps://github.com/elastic/kibana/issues/201889\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"161ce34cf7f38faed884421976b10494df0a4075"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210482","number":210482,"mergeCommit":{"message":"[Security Solution][THI] remove usages of EUI json tokens (#210482)\n\n## Summary\r\n\r\nThis PR is probably the final PR that makes the changes to support EUI\r\nBorealis. It focuses on removing all the usage of EUI Json tokens.\r\n\r\nYou will notice different approaches while removing the tokens:\r\n- for some cases, the changes were done using `css from\r\n'@emotions/react'` as the components using the tokens were already using\r\n`euiTheme` or adding it was straightforward and required the minimal\r\namount of changes\r\n- for some cases, where the css changes were pretty involved, a hook was\r\ncreated to be able to import the styles and apply them in the components\r\n- finally for other cases, esepcially if the styled components were\r\nextracted in a different file and were used within many others, I\r\ndecided to create reusable components. This allowed to not change all\r\nthe files impacted and limit the number of files modified in this PR.\r\n\r\nFeel free to comment on any of the approaches and suggest better\r\noptions!\r\n\r\nhttps://github.com/elastic/kibana/issues/201889\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"161ce34cf7f38faed884421976b10494df0a4075"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co>	2025-02-11 23:56:44 +01:00
Kibana Machine	ad10df99c5	[8.x] [Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318) (#208928) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318)](https://github.com/elastic/kibana/pull/207318) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Agustina Nahir Ruidiaz","email":"61565784+agusruidiazgd@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-30T12:24:05Z","message":"[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318)\n\n## Summary\r\nAddresses [#206437](https://github.com/elastic/kibana/issues/206437)\r\nThis PR migrates `explore page` from `styled-components` to\r\n`@emotion/styled`.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/f1702c0d-78f7-4e17-a8d6-c7c9ae19d3b7\r\n\r\n\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- [ ] [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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1e63b5ae999eb5022f9f02626db9f70e17d28a92","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting:Explore","backport:prev-minor","ci:cloud-deploy","EUI Visual Refresh"],"title":"[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components","number":207318,"url":"https://github.com/elastic/kibana/pull/207318","mergeCommit":{"message":"[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318)\n\n## Summary\r\nAddresses [#206437](https://github.com/elastic/kibana/issues/206437)\r\nThis PR migrates `explore page` from `styled-components` to\r\n`@emotion/styled`.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/f1702c0d-78f7-4e17-a8d6-c7c9ae19d3b7\r\n\r\n\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- [ ] [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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1e63b5ae999eb5022f9f02626db9f70e17d28a92"}},"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/207318","number":207318,"mergeCommit":{"message":"[Security Solution] [EUI Refresh] [Explore page] Migrate styled-components (#207318)\n\n## Summary\r\nAddresses [#206437](https://github.com/elastic/kibana/issues/206437)\r\nThis PR migrates `explore page` from `styled-components` to\r\n`@emotion/styled`.\r\nIn the process I also convert the kbn/ui-theme json tokens to euiTheme\r\ncounterparts.\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/f1702c0d-78f7-4e17-a8d6-c7c9ae19d3b7\r\n\r\n\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- [ ] [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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1e63b5ae999eb5022f9f02626db9f70e17d28a92"}}]}] BACKPORT--> --------- Co-authored-by: Agustina Nahir Ruidiaz <61565784+agusruidiazgd@users.noreply.github.com> Co-authored-by: Karen Grigoryan <karen.grigoryan@elastic.co>	2025-02-11 21:06:51 +01:00
Nathan Reese	b28c80e5f6	[8.x] [maps] lazy load map actions (#210252) (#210653) ... # Backport This will backport the following commits from `main` to `8.x`: - [[maps] lazy load map actions (#210252)](https://github.com/elastic/kibana/pull/210252) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T16:37:34Z","message":"[maps] lazy load map actions (#210252)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8a30b862cc1c4aee11559f34f6c6c0c453a674e5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","release_note:skip","backport:version","v9.1.0","v8.19.0"],"title":"[maps] lazy load map actions","number":210252,"url":"https://github.com/elastic/kibana/pull/210252","mergeCommit":{"message":"[maps] lazy load map actions (#210252)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8a30b862cc1c4aee11559f34f6c6c0c453a674e5"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210252","number":210252,"mergeCommit":{"message":"[maps] lazy load map actions (#210252)\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8a30b862cc1c4aee11559f34f6c6c0c453a674e5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>	2025-02-11 20:30:08 +01:00
Kibana Machine	5d11caa37b	[8.x] [Authz] Migrated routes with access tags to security config (#209756) (#210596) ... # Backport This will backport the following commits from `main` to `8.x`: - [[Authz] Migrated routes with access tags to security config (#209756)](https://github.com/elastic/kibana/pull/209756) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T14:36:38Z","message":"[Authz] Migrated routes with access tags to security config (#209756)\n\n## Summary\r\n\r\nThis PR migrates the last routes with `access:<privilege>` tags used in\r\nroute definitions to new security configuration.\r\nPlease refer to the documentation for more information: [Authorization\r\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\r\n\r\n### **Before Migration:**\r\nAccess control tags were defined in the `options` object of the route:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n options: {\r\n tags: ['access:<privilege_1>', 'access:<privilege_2>'],\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### **After Migration:**\r\nTags have been replaced with the more robust\r\n`security.authz.requiredPrivileges` field under `security`:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n security: {\r\n authz: {\r\n requiredPrivileges: ['<privilege_1>', '<privilege_2>'],\r\n },\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### Checklist\r\n\r\n- [x]\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- [x] [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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ad0e1d9d9d5ffba3c0bd7839affe0e885c3f2f03","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"[Authz] Migrated routes with access tags to security config","number":209756,"url":"https://github.com/elastic/kibana/pull/209756","mergeCommit":{"message":"[Authz] Migrated routes with access tags to security config (#209756)\n\n## Summary\r\n\r\nThis PR migrates the last routes with `access:<privilege>` tags used in\r\nroute definitions to new security configuration.\r\nPlease refer to the documentation for more information: [Authorization\r\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\r\n\r\n### **Before Migration:**\r\nAccess control tags were defined in the `options` object of the route:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n options: {\r\n tags: ['access:<privilege_1>', 'access:<privilege_2>'],\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### **After Migration:**\r\nTags have been replaced with the more robust\r\n`security.authz.requiredPrivileges` field under `security`:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n security: {\r\n authz: {\r\n requiredPrivileges: ['<privilege_1>', '<privilege_2>'],\r\n },\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### Checklist\r\n\r\n- [x]\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- [x] [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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ad0e1d9d9d5ffba3c0bd7839affe0e885c3f2f03"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209756","number":209756,"mergeCommit":{"message":"[Authz] Migrated routes with access tags to security config (#209756)\n\n## Summary\r\n\r\nThis PR migrates the last routes with `access:<privilege>` tags used in\r\nroute definitions to new security configuration.\r\nPlease refer to the documentation for more information: [Authorization\r\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\r\n\r\n### **Before Migration:**\r\nAccess control tags were defined in the `options` object of the route:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n options: {\r\n tags: ['access:<privilege_1>', 'access:<privilege_2>'],\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### **After Migration:**\r\nTags have been replaced with the more robust\r\n`security.authz.requiredPrivileges` field under `security`:\r\n\r\n```ts\r\nrouter.get({\r\n path: '/api/path',\r\n security: {\r\n authz: {\r\n requiredPrivileges: ['<privilege_1>', '<privilege_2>'],\r\n },\r\n },\r\n ...\r\n}, handler);\r\n```\r\n\r\n### Checklist\r\n\r\n- [x]\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- [x] [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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"ad0e1d9d9d5ffba3c0bd7839affe0e885c3f2f03"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com>	2025-02-11 17:37:06 +01:00
Gerard Soldevila	bfcfe55bc8	[8.x] SKA: Follow-up relocations (#209477) (#210501) ... # Backport This will backport the following commits from `main` to `8.x`: - [SKA: Follow-up relocations (#209477)](https://github.com/elastic/kibana/pull/209477) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T18:53:36Z","message":"SKA: Follow-up relocations (#209477)\n\n## Summary\r\n\r\n* Categorise and move `@kbn/timelines-plugin` as _platform/shared_,\r\ntarget location: `x-pack/platform/plugins/shared/timelines`.\r\nThis helps reduce the scope of the illegal dependencies from `osquery`\r\nplugin towards _security/private_ code.\r\ncc @tomsonpl \r\n\r\n* Simplify path and rename `@kbn/observability-alerting-rule-utils`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-alerting-rule-utils\r\nx-pack/platform/packages/shared/observability/alerting_rule_utils/\r\n\r\n# After\r\n@kbn/alerting-rule-utils\r\nx-pack/platform/packages/shared/alerting_rule_utils/\r\n```\r\n\r\n* Simplify path and rename `@kbn/observability-logs-overview`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-logs-overview\r\nx-pack/platform/packages/shared/observability/logs_overview/\r\n\r\n# After\r\n@kbn/logs-overview\r\nx-pack/platform/packages/shared/logs_overview/\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b1c74a7a85c1e07449ab92dac7e4b62ad1b8f4b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport missing","backport:prev-minor","backport:prev-major","Team:obs-ux-management","v9.1.0"],"title":"SKA: Follow-up relocations","number":209477,"url":"https://github.com/elastic/kibana/pull/209477","mergeCommit":{"message":"SKA: Follow-up relocations (#209477)\n\n## Summary\r\n\r\n* Categorise and move `@kbn/timelines-plugin` as _platform/shared_,\r\ntarget location: `x-pack/platform/plugins/shared/timelines`.\r\nThis helps reduce the scope of the illegal dependencies from `osquery`\r\nplugin towards _security/private_ code.\r\ncc @tomsonpl \r\n\r\n* Simplify path and rename `@kbn/observability-alerting-rule-utils`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-alerting-rule-utils\r\nx-pack/platform/packages/shared/observability/alerting_rule_utils/\r\n\r\n# After\r\n@kbn/alerting-rule-utils\r\nx-pack/platform/packages/shared/alerting_rule_utils/\r\n```\r\n\r\n* Simplify path and rename `@kbn/observability-logs-overview`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-logs-overview\r\nx-pack/platform/packages/shared/observability/logs_overview/\r\n\r\n# After\r\n@kbn/logs-overview\r\nx-pack/platform/packages/shared/logs_overview/\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b1c74a7a85c1e07449ab92dac7e4b62ad1b8f4b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209477","number":209477,"mergeCommit":{"message":"SKA: Follow-up relocations (#209477)\n\n## Summary\r\n\r\n* Categorise and move `@kbn/timelines-plugin` as _platform/shared_,\r\ntarget location: `x-pack/platform/plugins/shared/timelines`.\r\nThis helps reduce the scope of the illegal dependencies from `osquery`\r\nplugin towards _security/private_ code.\r\ncc @tomsonpl \r\n\r\n* Simplify path and rename `@kbn/observability-alerting-rule-utils`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-alerting-rule-utils\r\nx-pack/platform/packages/shared/observability/alerting_rule_utils/\r\n\r\n# After\r\n@kbn/alerting-rule-utils\r\nx-pack/platform/packages/shared/alerting_rule_utils/\r\n```\r\n\r\n* Simplify path and rename `@kbn/observability-logs-overview`\r\n(platform/shared):\r\n```\r\n# Before \r\n@kbn/observability-logs-overview\r\nx-pack/platform/packages/shared/observability/logs_overview/\r\n\r\n# After\r\n@kbn/logs-overview\r\nx-pack/platform/packages/shared/logs_overview/\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"7b1c74a7a85c1e07449ab92dac7e4b62ad1b8f4b"}}]}] BACKPORT-->	2025-02-11 14:59:57 +01:00
Kibana Machine	2046aed6a6	[8.x] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#210088) ... # Backport This will backport the following commits from `main` to `8.x`: - [[scout] unique runId for reporting, disabled failed test reporter locally (#209507)](https://github.com/elastic/kibana/pull/209507) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-02-05T15:35:26Z","message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","backport:prev-major","test:scout","v9.1.0"],"title":"[scout] unique runId for reporting, disabled failed test reporter locally","number":209507,"url":"https://github.com/elastic/kibana/pull/209507","mergeCommit":{"message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/209808","number":209808,"state":"MERGED","mergeCommit":{"sha":"2c04505bd6ad9db59e0ea3aa617d649b41134294","message":"[9.0] [scout] unique runId for reporting, disabled failed test reporter locally (#209507) (#209808)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[scout] unique runId for reporting, disabled failed test reporter\nlocally (#209507)](https://github.com/elastic/kibana/pull/209507)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Dzmitry\nLemechko\",\"email\":\"dzmitry.lemechko@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-05T15:35:26Z\",\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"backport:prev-minor\",\"test:scout\",\"v9.1.0\"],\"title\":\"[scout]\nunique runId for reporting, disabled failed test reporter\nlocally\",\"number\":209507,\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"mergeCommit\":{\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be\nenough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\"],\"targetPullRequestStates\":[{\"branch\":\"9.0\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"main\",\"label\":\"v9.1.0\",\"branchLabelMappingKey\":\"^v9.1.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/209507\",\"number\":209507,\"mergeCommit\":{\"message\":\"[scout]\nunique runId for reporting, disabled failed test reporter locally\n(#209507)\\n\\n## Summary\\r\\n\\r\\nThis PR makes few changes to scout\nreporter:\\r\\n\\r\\nRecently I found out that Playwright load configuration\nfile _multiple\\r\\ntimes_:\\r\\n- first time after you run `npx playwright\ntest -c ...`\\r\\n- on every worker start\\r\\n\\r\\nlog\nbefore:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 18f35f735a10155c\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n2633b4e4c20afa15\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch\n@ess\\r\\n```\\r\\n\\r\\nWith our current logic unique `runId` will be\ngenerated on each\\r\\nconfiguration load, meaning for parallel run we\nwill report failures in\\r\\ndifferent directories instead of the same\none.\\r\\n\\r\\nPlaywright doesn't expose any unique identifier for the run,\nso we have\\r\\ndo something similar described\nin\\r\\n\\r\\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\\r\\n\\r\\nlog\nafter fix:\\r\\n\\r\\n```\\r\\n[main][~/github/kibana]$ npx playwright test\n--config\nx-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\\r\\n[createPlaywrightConfig]\ncalled with runId: 310a576f32d3b8a5\\r\\n\\r\\nRunning 1 test using 1\nworker\\r\\n\\r\\n[createPlaywrightConfig] called with runId:\n310a576f32d3b8a5\\r\\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps ›\nFull screen mode @svlSecurity @svlOblt @svlSearch @ess\\r\\n```\\r\\n\\r\\nWe\nalso had a chat with @dolaru and agreed that Scout reporters to\nbe\\r\\ndisabled for local test run. Few reasons:\\r\\n- Scout custom\nreporting targets CI execution: events-based reporter was\\r\\nalready\ndisabled\\r\\n- Failed test reporter purpose is to provide html\nboilerplate to be\\r\\nannotated in pipeline build\\r\\n- When you run tests\nwith IDE playwright plugin it provides its own\\r\\nreporter / history,\nshould be enough.\",\"sha\":\"6635fe501c307d567afa71a346fc91a7675e3cc5\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/209507","number":209507,"mergeCommit":{"message":"[scout] unique runId for reporting, disabled failed test reporter locally (#209507)\n\n## Summary\r\n\r\nThis PR makes few changes to scout reporter:\r\n\r\nRecently I found out that Playwright load configuration file _multiple\r\ntimes_:\r\n- first time after you run `npx playwright test -c ...`\r\n- on every worker start\r\n\r\nlog before:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 18f35f735a10155c\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 2633b4e4c20afa15\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWith our current logic unique `runId` will be generated on each\r\nconfiguration load, meaning for parallel run we will report failures in\r\ndifferent directories instead of the same one.\r\n\r\nPlaywright doesn't expose any unique identifier for the run, so we have\r\ndo something similar described in\r\n\r\nhttps://github.com/microsoft/playwright/issues/28941#issuecomment-1888008102\r\n\r\nlog after fix:\r\n\r\n```\r\n[main][~/github/kibana]$ npx playwright test --config x-pack/platform/plugins/shared/maps/ui_tests/playwright.config.ts\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n\r\nRunning 1 test using 1 worker\r\n\r\n[createPlaywrightConfig] called with runId: 310a576f32d3b8a5\r\n[chromium] › full_screen_mode.spec.ts:28:9 › Maps › Full screen mode @svlSecurity @svlOblt @svlSearch @ess\r\n```\r\n\r\nWe also had a chat with @dolaru and agreed that Scout reporters to be\r\ndisabled for local test run. Few reasons:\r\n- Scout custom reporting targets CI execution: events-based reporter was\r\nalready disabled\r\n- Failed test reporter purpose is to provide html boilerplate to be\r\nannotated in pipeline build\r\n- When you run tests with IDE playwright plugin it provides its own\r\nreporter / history, should be enough.","sha":"6635fe501c307d567afa71a346fc91a7675e3cc5"}}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>	2025-02-09 13:14:39 +01:00