mirror of
https://github.com/elastic/kibana.git
synced 2025-04-20 07:48:52 -04:00
84501 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
b1aefb7c84
|
[9.0] Add FTR cases for synonyms (#214476) (#214999)
# Backport This will backport the following commits from `main` to `9.0`: - [Add FTR cases for synonyms (#214476)](https://github.com/elastic/kibana/pull/214476) <!--- 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-18T15:25:48Z","message":"Add FTR cases for synonyms (#214476)\n\n## Summary\n\nAdds more coverage for FTRs to test Synonyms UI in serverless.\n\nAdds test cases for synonyms set listing, synoyms set detail and adding\ndeleting rules.\nCovers some happy paths.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\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- [x] 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":"a73477c7c05ffd748f1fdce58184d837b153798e","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:Search","backport:version","v9.1.0","v9.0.1"],"title":"Add FTR cases for synonyms","number":214476,"url":"https://github.com/elastic/kibana/pull/214476","mergeCommit":{"message":"Add FTR cases for synonyms (#214476)\n\n## Summary\n\nAdds more coverage for FTRs to test Synonyms UI in serverless.\n\nAdds test cases for synonyms set listing, synoyms set detail and adding\ndeleting rules.\nCovers some happy paths.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\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- [x] 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":"a73477c7c05ffd748f1fdce58184d837b153798e"}},"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/214476","number":214476,"mergeCommit":{"message":"Add FTR cases for synonyms (#214476)\n\n## Summary\n\nAdds more coverage for FTRs to test Synonyms UI in serverless.\n\nAdds test cases for synonyms set listing, synoyms set detail and adding\ndeleting rules.\nCovers some happy paths.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\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- [x] 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":"a73477c7c05ffd748f1fdce58184d837b153798e"}}]}] BACKPORT--> Co-authored-by: Efe Gürkan YALAMAN <efeguerkan.yalaman@elastic.co> |
||
Jacek Kolezynski
|
22245cb937
|
[9.0] [Security Solution] Fix flaky test for delete rules bulk legacy and unskip it (#214724) (#214983)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Fix flaky test for delete rules bulk legacy and unskip it (#214724)](https://github.com/elastic/kibana/pull/214724) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jacek Kolezynski","email":"jacek.kolezynski@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T14:01:53Z","message":"[Security Solution] Fix flaky test for delete rules bulk legacy and unskip it (#214724)\n\n**Resolves: #214633**\n\n## Summary\n\nI am fixing a flaky test in the `delete_rules_bulk_legacy.ts` file\nintroduced in the #213244.\n\nAlso, in two other files I am changing using expect from kbn to jest.","sha":"237d4f5c14f787dedf2cb6a346bc1cf8fc835a40","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:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","Team:Detection Rule Management","backport:version","9.1 candidate","v9.1.0"],"title":"[Security Solution] Fix flaky test for delete rules bulk legacy and unskip it","number":214724,"url":"https://github.com/elastic/kibana/pull/214724","mergeCommit":{"message":"[Security Solution] Fix flaky test for delete rules bulk legacy and unskip it (#214724)\n\n**Resolves: #214633**\n\n## Summary\n\nI am fixing a flaky test in the `delete_rules_bulk_legacy.ts` file\nintroduced in the #213244.\n\nAlso, in two other files I am changing using expect from kbn to jest.","sha":"237d4f5c14f787dedf2cb6a346bc1cf8fc835a40"}},"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/214724","number":214724,"mergeCommit":{"message":"[Security Solution] Fix flaky test for delete rules bulk legacy and unskip it (#214724)\n\n**Resolves: #214633**\n\n## Summary\n\nI am fixing a flaky test in the `delete_rules_bulk_legacy.ts` file\nintroduced in the #213244.\n\nAlso, in two other files I am changing using expect from kbn to jest.","sha":"237d4f5c14f787dedf2cb6a346bc1cf8fc835a40"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
7a764bad1d
|
[9.0] [Authz]: added reason for authorization opt out for snapshot_restore routes (#213888) (#214727)
# Backport This will backport the following commits from `main` to `9.0`: - [[Authz]: added reason for authorization opt out for snapshot_restore routes (#213888)](https://github.com/elastic/kibana/pull/213888) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T12:15:45Z","message":"[Authz]: added reason for authorization opt out for snapshot_restore routes (#213888)\n\n## Summary\n\nAdded reason for authorization opt out for `snapshot_restore` routes.\n\n\n### Checklist\n\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\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"59e606cdc49e6500bfd7a9a6e95c4e9d4174e775","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"[Authz]: added reason for authorization opt out for snapshot_restore routes","number":213888,"url":"https://github.com/elastic/kibana/pull/213888","mergeCommit":{"message":"[Authz]: added reason for authorization opt out for snapshot_restore routes (#213888)\n\n## Summary\n\nAdded reason for authorization opt out for `snapshot_restore` routes.\n\n\n### Checklist\n\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\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"59e606cdc49e6500bfd7a9a6e95c4e9d4174e775"}},"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/213888","number":213888,"mergeCommit":{"message":"[Authz]: added reason for authorization opt out for snapshot_restore routes (#213888)\n\n## Summary\n\nAdded reason for authorization opt out for `snapshot_restore` routes.\n\n\n### Checklist\n\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\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"59e606cdc49e6500bfd7a9a6e95c4e9d4174e775"}},{"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> |
||
|
Kibana Machine
|
fd630b317e
|
[9.0] [DOCS] Add minimal short URL APIs (#213860) (#214969)
# Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Add minimal short URL APIs (#213860)](https://github.com/elastic/kibana/pull/213860) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T12:28:23Z","message":"[DOCS] Add minimal short URL APIs (#213860)","sha":"863a42fd31827e592319fcaf3670a7d18cd3e637","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","docs","Team:SharedUX","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[DOCS] Add minimal short URL APIs","number":213860,"url":"https://github.com/elastic/kibana/pull/213860","mergeCommit":{"message":"[DOCS] Add minimal short URL APIs (#213860)","sha":"863a42fd31827e592319fcaf3670a7d18cd3e637"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213860","number":213860,"mergeCommit":{"message":"[DOCS] Add minimal short URL APIs (#213860)","sha":"863a42fd31827e592319fcaf3670a7d18cd3e637"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
426bf5c7e9
|
[9.0] [Uptime] Unskip flaky Overview Page tests (#214807) (#214973)
# Backport This will backport the following commits from `main` to `9.0`: - [[Uptime] Unskip flaky Overview Page tests (#214807)](https://github.com/elastic/kibana/pull/214807) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T12:39:58Z","message":"[Uptime] Unskip flaky Overview Page tests (#214807)\n\n## Summary\n\nResolves #57737.\nResolves [#89072](https://github.com/elastic/kibana/issues/89072).\n\n40/40 ✅\n[run](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051)\non Flaky Test Runner.\n\n- [Example #57737\nsuccess](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051#0195a4d4-f2d0-4be4-a91d-6b0d4b6ba84d/240-1226)\n- [Example #89072\nsuccess](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051#0195a4d4-f2d0-4be4-a91d-6b0d4b6ba84d/240-1231)\n\nUsing the page elements manually on the test server version of Kibana, I\ncan click through and execute all these tests by hand. However, for some\nreason web driver does not click the elements and make the desired\nthings happen.\n\nAll of the behaviors we are testing are configurable via the URL params,\nso I'm relying on the URL to set the app state to the expected\nconditions to verify the app is working. These page elements are also\ntested via unit-level tests, so I don't think we are losing any\npractical coverage for this soon-to-be-deprecated code.\n\nAdditionally, I removed the code in the `beforeEach` hook that utilizes\nthe date picker to set the default start/end range fields. This takes\n_forever_, and our tests don't need to test that `SuperDatePicker` is\ndoing its job (again, our implementation has unit tests to verify the\ncorrect callbacks are provided and that they handle the input criteria).\nInstead we simply `navigateToApp` with the default parameters specified\nin the URL search.","sha":"a412a05ddf233b6115a20460e18e802e4517cba0","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","Team:obs-ux-management","v9.1.0"],"title":"[Uptime] Unskip flaky Overview Page tests","number":214807,"url":"https://github.com/elastic/kibana/pull/214807","mergeCommit":{"message":"[Uptime] Unskip flaky Overview Page tests (#214807)\n\n## Summary\n\nResolves #57737.\nResolves [#89072](https://github.com/elastic/kibana/issues/89072).\n\n40/40 ✅\n[run](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051)\non Flaky Test Runner.\n\n- [Example #57737\nsuccess](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051#0195a4d4-f2d0-4be4-a91d-6b0d4b6ba84d/240-1226)\n- [Example #89072\nsuccess](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051#0195a4d4-f2d0-4be4-a91d-6b0d4b6ba84d/240-1231)\n\nUsing the page elements manually on the test server version of Kibana, I\ncan click through and execute all these tests by hand. However, for some\nreason web driver does not click the elements and make the desired\nthings happen.\n\nAll of the behaviors we are testing are configurable via the URL params,\nso I'm relying on the URL to set the app state to the expected\nconditions to verify the app is working. These page elements are also\ntested via unit-level tests, so I don't think we are losing any\npractical coverage for this soon-to-be-deprecated code.\n\nAdditionally, I removed the code in the `beforeEach` hook that utilizes\nthe date picker to set the default start/end range fields. This takes\n_forever_, and our tests don't need to test that `SuperDatePicker` is\ndoing its job (again, our implementation has unit tests to verify the\ncorrect callbacks are provided and that they handle the input criteria).\nInstead we simply `navigateToApp` with the default parameters specified\nin the URL search.","sha":"a412a05ddf233b6115a20460e18e802e4517cba0"}},"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/214807","number":214807,"mergeCommit":{"message":"[Uptime] Unskip flaky Overview Page tests (#214807)\n\n## Summary\n\nResolves #57737.\nResolves [#89072](https://github.com/elastic/kibana/issues/89072).\n\n40/40 ✅\n[run](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051)\non Flaky Test Runner.\n\n- [Example #57737\nsuccess](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051#0195a4d4-f2d0-4be4-a91d-6b0d4b6ba84d/240-1226)\n- [Example #89072\nsuccess](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8051#0195a4d4-f2d0-4be4-a91d-6b0d4b6ba84d/240-1231)\n\nUsing the page elements manually on the test server version of Kibana, I\ncan click through and execute all these tests by hand. However, for some\nreason web driver does not click the elements and make the desired\nthings happen.\n\nAll of the behaviors we are testing are configurable via the URL params,\nso I'm relying on the URL to set the app state to the expected\nconditions to verify the app is working. These page elements are also\ntested via unit-level tests, so I don't think we are losing any\npractical coverage for this soon-to-be-deprecated code.\n\nAdditionally, I removed the code in the `beforeEach` hook that utilizes\nthe date picker to set the default start/end range fields. This takes\n_forever_, and our tests don't need to test that `SuperDatePicker` is\ndoing its job (again, our implementation has unit tests to verify the\ncorrect callbacks are provided and that they handle the input criteria).\nInstead we simply `navigateToApp` with the default parameters specified\nin the URL search.","sha":"a412a05ddf233b6115a20460e18e802e4517cba0"}}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co> |
||
Dzmitry Lemechko
|
1101afbf99
|
[9.0] [scout] use project deps as global hooks for parallel tests (#211409) (#214645)
# Backport This will backport the following commits from `main` to `9.0`: - [[scout] use project deps as global hooks for parallel tests (#211409)](https://github.com/elastic/kibana/pull/211409) <!--- 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-03-13T09:06:26Z","message":"[scout] use project deps as global hooks for parallel tests (#211409)\n\n## Summary\n\nCurrently we are using `globalSetup` [script in configuration\nfile](https://playwright.dev/docs/test-global-setup-teardown#option-2-configure-globalsetup-and-globalteardown)\nto ingest Elasticsearch data before running the tests in parallel\nagainst the same ES/Kibana instances.\n\nThis approach doesn't work well when you need to adjust `globalSetup`\nlogic based on specific condition, e.g. configuration file defining\nwhere servers are hosted, its credentials, etc.\n\nNot only global hook, but `ScoutConfig` fixture expects an argument to\ndefine where servers configuration is defined:\n\n\n |
||
|
Kibana Machine
|
c5c18bbe5e
|
[9.0] [APM] Filter out upstream orphans in waterfall (#214704) (#214966)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM] Filter out upstream orphans in waterfall (#214704)](https://github.com/elastic/kibana/pull/214704) <!--- Backport version: 9.6.6 --> ### 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-03-18T12:06:36Z","message":"[APM] Filter out upstream orphans in waterfall (#214704)\n\n## Summary\n\nCloses #212797\n\n\nThis PR filters out upstream orphans in the waterfall, which was\nconfusing as we were reparenting to the entry transaction.","sha":"e1f094d1f57037445213e326b6fa01696172d601","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[APM] Filter out upstream orphans in waterfall","number":214704,"url":"https://github.com/elastic/kibana/pull/214704","mergeCommit":{"message":"[APM] Filter out upstream orphans in waterfall (#214704)\n\n## Summary\n\nCloses #212797\n\n\nThis PR filters out upstream orphans in the waterfall, which was\nconfusing as we were reparenting to the entry transaction.","sha":"e1f094d1f57037445213e326b6fa01696172d601"}},"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/214704","number":214704,"mergeCommit":{"message":"[APM] Filter out upstream orphans in waterfall (#214704)\n\n## Summary\n\nCloses #212797\n\n\nThis PR filters out upstream orphans in the waterfall, which was\nconfusing as we were reparenting to the entry transaction.","sha":"e1f094d1f57037445213e326b6fa01696172d601"}},{"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> |
||
|
Kibana Machine
|
bc32304513
|
[9.0] [CI] Only emit .d.ts when running typecheck (#209259) (#214944)
# Backport This will backport the following commits from `main` to `9.0`: - [[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> |
||
|
Kibana Machine
|
a0aebf1859
|
[9.0] [APM] Fix entry item in waterfall shouldn't be orphan (#214700) (#214928)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM] Fix entry item in waterfall shouldn't be orphan (#214700)](https://github.com/elastic/kibana/pull/214700) <!--- Backport version: 9.6.6 --> ### 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-03-18T10:02:30Z","message":"[APM] Fix entry item in waterfall shouldn't be orphan (#214700)\n\n## Summary\n\nCloses #213074\n\nThis PR fixes the scenario where the entry waterfall transaction is\ntreated as an orphan, causing it to reparent itself and be duplicated\nmultiple times.\n\n---------\n\nCo-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>","sha":"dbb2aeda4d422a6a03a74f437cd25f515309654a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[APM] Fix entry item in waterfall shouldn't be orphan","number":214700,"url":"https://github.com/elastic/kibana/pull/214700","mergeCommit":{"message":"[APM] Fix entry item in waterfall shouldn't be orphan (#214700)\n\n## Summary\n\nCloses #213074\n\nThis PR fixes the scenario where the entry waterfall transaction is\ntreated as an orphan, causing it to reparent itself and be duplicated\nmultiple times.\n\n---------\n\nCo-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>","sha":"dbb2aeda4d422a6a03a74f437cd25f515309654a"}},"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/214700","number":214700,"mergeCommit":{"message":"[APM] Fix entry item in waterfall shouldn't be orphan (#214700)\n\n## Summary\n\nCloses #213074\n\nThis PR fixes the scenario where the entry waterfall transaction is\ntreated as an orphan, causing it to reparent itself and be duplicated\nmultiple times.\n\n---------\n\nCo-authored-by: Cauê Marcondes <55978943+cauemarcondes@users.noreply.github.com>","sha":"dbb2aeda4d422a6a03a74f437cd25f515309654a"}},{"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> |
||
|
Kibana Machine
|
ce776eca54
|
[9.0] [Lens][Datatable] Fix color by value for Last value array mode (#213917) (#214919)
# Backport This will backport the following commits from `main` to `9.0`: - [[Lens][Datatable] Fix color by value for Last value array mode (#213917)](https://github.com/elastic/kibana/pull/213917) <!--- Backport version: 9.6.6 --> ### 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-03-18T09:09:03Z","message":"[Lens][Datatable] Fix color by value for Last value array mode (#213917)\n\n## Summary\n\nFixes the table side of #188263 \n\nThe [fix used for\n`Metric`](https://github.com/elastic/kibana/pull/209110) has been\ngeneralized and re-used for the datatable visualization.\n\n\n\n\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","sha":"0b9df094d1770065f79c05272a41175396caa27b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Visualizations","Feature:Lens","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Lens][Datatable] Fix color by value for Last value array mode","number":213917,"url":"https://github.com/elastic/kibana/pull/213917","mergeCommit":{"message":"[Lens][Datatable] Fix color by value for Last value array mode (#213917)\n\n## Summary\n\nFixes the table side of #188263 \n\nThe [fix used for\n`Metric`](https://github.com/elastic/kibana/pull/209110) has been\ngeneralized and re-used for the datatable visualization.\n\n\n\n\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","sha":"0b9df094d1770065f79c05272a41175396caa27b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213917","number":213917,"mergeCommit":{"message":"[Lens][Datatable] Fix color by value for Last value array mode (#213917)\n\n## Summary\n\nFixes the table side of #188263 \n\nThe [fix used for\n`Metric`](https://github.com/elastic/kibana/pull/209110) has been\ngeneralized and re-used for the datatable visualization.\n\n\n\n\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","sha":"0b9df094d1770065f79c05272a41175396caa27b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
Ignacio Rivas
|
ab3050f295
|
[9.0] [UA] Make public APIs internal (#214051) (#214530)
# Backport
This will backport the following commits from `main` to `9.0`:
- [[UA] Make public APIs internal
(#214051)](https://github.com/elastic/kibana/pull/214051)
[This](
|
||
elastic-vault-github-plugin-prod[bot]
|
01c2e061c3
|
[9.0] Sync bundled packages with Package Storage (#214909)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2460 Co-authored-by: elasticmachine <elasticmachine@elastic.co> |
||
|
Kibana Machine
|
efc05f44be
|
[9.0] [Siem Migrations] - Adds eventName property for Siem Migrations telemetry (#214186) (#214852)
# Backport This will backport the following commits from `main` to `9.0`: - [[Siem Migrations] - Adds `eventName` property for Siem Migrations telemetry (#214186)](https://github.com/elastic/kibana/pull/214186) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T17:28:23Z","message":"[Siem Migrations] - Adds `eventName` property for Siem Migrations telemetry (#214186)\n\n## Summary\n\nThis PR adds `eventName` property to the Siem Migrations telemetry. This\nchange is non-destructive to previous format and simply adds a new\nproperty `eventName`.","sha":"bdd0de29b1c681a9f74b359410cac4ea875d0786","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","v8.18.1"],"title":"[Siem Migrations] - Adds `eventName` property for Siem Migrations telemetry","number":214186,"url":"https://github.com/elastic/kibana/pull/214186","mergeCommit":{"message":"[Siem Migrations] - Adds `eventName` property for Siem Migrations telemetry (#214186)\n\n## Summary\n\nThis PR adds `eventName` property to the Siem Migrations telemetry. This\nchange is non-destructive to previous format and simply adds a new\nproperty `eventName`.","sha":"bdd0de29b1c681a9f74b359410cac4ea875d0786"}},"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/214186","number":214186,"mergeCommit":{"message":"[Siem Migrations] - Adds `eventName` property for Siem Migrations telemetry (#214186)\n\n## Summary\n\nThis PR adds `eventName` property to the Siem Migrations telemetry. This\nchange is non-destructive to previous format and simply adds a new\nproperty `eventName`.","sha":"bdd0de29b1c681a9f74b359410cac4ea875d0786"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
Jeramy Soucy
|
cae810523b
|
[9.0] Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792) (#214901)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)](https://github.com/elastic/kibana/pull/214792) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T17:57:41Z","message":"Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)\n\n## Summary\n\nUpgrades `xml-crypto` from v6.0.0 to v6.0.1","sha":"da7e44988d160c55147765959dcc19ff59d1cdb6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport:all-open","v9.1.0","v9.0.1"],"title":"Upgrade xml-crypto 6.0.0 → 6.0.1","number":214792,"url":"https://github.com/elastic/kibana/pull/214792","mergeCommit":{"message":"Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)\n\n## Summary\n\nUpgrades `xml-crypto` from v6.0.0 to v6.0.1","sha":"da7e44988d160c55147765959dcc19ff59d1cdb6"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214792","number":214792,"mergeCommit":{"message":"Upgrade xml-crypto 6.0.0 → 6.0.1 (#214792)\n\n## Summary\n\nUpgrades `xml-crypto` from v6.0.0 to v6.0.1","sha":"da7e44988d160c55147765959dcc19ff59d1cdb6"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
afbc335865
|
[9.0] [Fleet] fix reassign agent with spaces (#214748) (#214812)
# Backport This will backport the following commits from `main` to `9.0`: - [[Fleet] fix reassign agent with spaces (#214748)](https://github.com/elastic/kibana/pull/214748) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T15:30:22Z","message":"[Fleet] fix reassign agent with spaces (#214748)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/214341\n\nUpdating agent spaces when reassigning to agent policy.\n\nTo verify:\n- Enable space awareness\n- Create an agent policy and enroll an agent to it\n- Create another agent policy and assign 2 spaces to it\n- Reassign agent to the second policy\n- Verify that the agent is visible in both spaces\n- Same behaviour with bulk reassign action\n\n<img width=\"1789\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3c7e6f07-c8d1-4a26-9e05-483caea6da1e\"\n/>\n<img width=\"1789\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b84d2f69-8ba7-4a38-9a80-9b9e8ab9b37a\"\n/>\n<img width=\"1782\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/1272c35b-25cc-4a55-af6d-61b442ff3e07\"\n/>\n<img width=\"1489\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/df23f420-63f5-4d4b-bdb2-721a381adb4e\"\n/>\n\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","sha":"68749db9590e8b1dbdd076a91f560e96abf424ae","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","backport:prev-minor","v9.1.0"],"title":"[Fleet] fix reassign agent with spaces","number":214748,"url":"https://github.com/elastic/kibana/pull/214748","mergeCommit":{"message":"[Fleet] fix reassign agent with spaces (#214748)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/214341\n\nUpdating agent spaces when reassigning to agent policy.\n\nTo verify:\n- Enable space awareness\n- Create an agent policy and enroll an agent to it\n- Create another agent policy and assign 2 spaces to it\n- Reassign agent to the second policy\n- Verify that the agent is visible in both spaces\n- Same behaviour with bulk reassign action\n\n<img width=\"1789\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3c7e6f07-c8d1-4a26-9e05-483caea6da1e\"\n/>\n<img width=\"1789\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b84d2f69-8ba7-4a38-9a80-9b9e8ab9b37a\"\n/>\n<img width=\"1782\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/1272c35b-25cc-4a55-af6d-61b442ff3e07\"\n/>\n<img width=\"1489\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/df23f420-63f5-4d4b-bdb2-721a381adb4e\"\n/>\n\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","sha":"68749db9590e8b1dbdd076a91f560e96abf424ae"}},"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/214748","number":214748,"mergeCommit":{"message":"[Fleet] fix reassign agent with spaces (#214748)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/214341\n\nUpdating agent spaces when reassigning to agent policy.\n\nTo verify:\n- Enable space awareness\n- Create an agent policy and enroll an agent to it\n- Create another agent policy and assign 2 spaces to it\n- Reassign agent to the second policy\n- Verify that the agent is visible in both spaces\n- Same behaviour with bulk reassign action\n\n<img width=\"1789\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/3c7e6f07-c8d1-4a26-9e05-483caea6da1e\"\n/>\n<img width=\"1789\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b84d2f69-8ba7-4a38-9a80-9b9e8ab9b37a\"\n/>\n<img width=\"1782\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/1272c35b-25cc-4a55-af6d-61b442ff3e07\"\n/>\n<img width=\"1489\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/df23f420-63f5-4d4b-bdb2-721a381adb4e\"\n/>\n\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","sha":"68749db9590e8b1dbdd076a91f560e96abf424ae"}}]}] BACKPORT--> --------- Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> Co-authored-by: Julia Bardi <julia.bardi@elastic.co> |
||
|
Kibana Machine
|
d39c519c59
|
[9.0] [DOCS] Add minimal uptime APIs (#213867) (#214885)
# Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Add minimal uptime APIs (#213867)](https://github.com/elastic/kibana/pull/213867) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T22:03:33Z","message":"[DOCS] Add minimal uptime APIs (#213867)","sha":"57caf8796cd5633625ccec94b1d77b3b425fec35","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","docs","Team:uptime","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[DOCS] Add minimal uptime APIs","number":213867,"url":"https://github.com/elastic/kibana/pull/213867","mergeCommit":{"message":"[DOCS] Add minimal uptime APIs (#213867)","sha":"57caf8796cd5633625ccec94b1d77b3b425fec35"}},"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/213867","number":213867,"mergeCommit":{"message":"[DOCS] Add minimal uptime APIs (#213867)","sha":"57caf8796cd5633625ccec94b1d77b3b425fec35"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
a6dda32ef7
|
[9.0] [DOCS] Logstash configuration management APIs (#214497) (#214895)
# Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Logstash configuration management APIs (#214497)](https://github.com/elastic/kibana/pull/214497) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T05:54:06Z","message":"[DOCS] Logstash configuration management APIs (#214497)","sha":"ab0776ee1e798daf4b73d34f5c369141c1a71dd7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Logstash","release_note:skip","docs","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[DOCS] Logstash configuration management APIs","number":214497,"url":"https://github.com/elastic/kibana/pull/214497","mergeCommit":{"message":"[DOCS] Logstash configuration management APIs (#214497)","sha":"ab0776ee1e798daf4b73d34f5c369141c1a71dd7"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214497","number":214497,"mergeCommit":{"message":"[DOCS] Logstash configuration management APIs (#214497)","sha":"ab0776ee1e798daf4b73d34f5c369141c1a71dd7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
|
Kibana Machine
|
d1b6b5047a
|
[9.0] [Security Solution] Fix session view error from alerts tab (#214887) (#214892)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Fix session view error from alerts tab (#214887)](https://github.com/elastic/kibana/pull/214887) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-18T03:57:36Z","message":"[Security Solution] Fix session view error from alerts tab (#214887)\n\n## Summary\n\nRelated: https://github.com/elastic/kibana/issues/130641\n\nWhen session view is opened on non-alert pages, if alert index is not\npassed, an error shows up when opening alert flyout.\nhttps://github.com/elastic/kibana/pull/196422 addressed this by passing\nan `alertsIndex` to the index name. However, it only addressed the\nalerts from the canvas area, when clicking view alerts from the alert\npanel, the error still occurs. This PR fixed that by passing alerts\nindex in the panel as well.\n\nThe bug only applies to alerts opened from alerts tab, and when\n`visualizationinFlyout` is enabled. This video shows the alerts flyout\nis showing correctly with the advanced setting on and off.\n\n\nhttps://github.com/user-attachments/assets/8dca4568-4645-4718-9605-17baa0691ed0\n\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":"48df091c719331b46f5d5373ce67547a43c132a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Threat Hunting:Investigations","backport:version","v8.18.0","v9.1.0"],"title":"[Security Solution] Fix session view error from alerts tab","number":214887,"url":"https://github.com/elastic/kibana/pull/214887","mergeCommit":{"message":"[Security Solution] Fix session view error from alerts tab (#214887)\n\n## Summary\n\nRelated: https://github.com/elastic/kibana/issues/130641\n\nWhen session view is opened on non-alert pages, if alert index is not\npassed, an error shows up when opening alert flyout.\nhttps://github.com/elastic/kibana/pull/196422 addressed this by passing\nan `alertsIndex` to the index name. However, it only addressed the\nalerts from the canvas area, when clicking view alerts from the alert\npanel, the error still occurs. This PR fixed that by passing alerts\nindex in the panel as well.\n\nThe bug only applies to alerts opened from alerts tab, and when\n`visualizationinFlyout` is enabled. This video shows the alerts flyout\nis showing correctly with the advanced setting on and off.\n\n\nhttps://github.com/user-attachments/assets/8dca4568-4645-4718-9605-17baa0691ed0\n\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":"48df091c719331b46f5d5373ce67547a43c132a1"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"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/214887","number":214887,"mergeCommit":{"message":"[Security Solution] Fix session view error from alerts tab (#214887)\n\n## Summary\n\nRelated: https://github.com/elastic/kibana/issues/130641\n\nWhen session view is opened on non-alert pages, if alert index is not\npassed, an error shows up when opening alert flyout.\nhttps://github.com/elastic/kibana/pull/196422 addressed this by passing\nan `alertsIndex` to the index name. However, it only addressed the\nalerts from the canvas area, when clicking view alerts from the alert\npanel, the error still occurs. This PR fixed that by passing alerts\nindex in the panel as well.\n\nThe bug only applies to alerts opened from alerts tab, and when\n`visualizationinFlyout` is enabled. This video shows the alerts flyout\nis showing correctly with the advanced setting on and off.\n\n\nhttps://github.com/user-attachments/assets/8dca4568-4645-4718-9605-17baa0691ed0\n\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":"48df091c719331b46f5d5373ce67547a43c132a1"}}]}] BACKPORT--> Co-authored-by: christineweng <18648970+christineweng@users.noreply.github.com> |
||
|
Kibana Machine
|
043c2a73ca
|
[9.0] [Obs AI Assistant] Remove prompts from recall ranking Telemetry event (#214573) (#214874)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Remove prompts from recall ranking Telemetry event (#214573)](https://github.com/elastic/kibana/pull/214573) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T20:10:44Z","message":"[Obs AI Assistant] Remove prompts from recall ranking Telemetry event (#214573)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/224\n\n## Summary\n\nRelates to https://github.com/elastic/obs-ai-assistant-team/issues/186\n\nRemoves the prompts from the recall ranking telemetry event.\n\n### Checklist\n\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":"43079c7603641f47853a370aef29f0512fe5e574","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 AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Remove prompts from recall ranking Telemetry event","number":214573,"url":"https://github.com/elastic/kibana/pull/214573","mergeCommit":{"message":"[Obs AI Assistant] Remove prompts from recall ranking Telemetry event (#214573)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/224\n\n## Summary\n\nRelates to https://github.com/elastic/obs-ai-assistant-team/issues/186\n\nRemoves the prompts from the recall ranking telemetry event.\n\n### Checklist\n\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":"43079c7603641f47853a370aef29f0512fe5e574"}},"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/214573","number":214573,"mergeCommit":{"message":"[Obs AI Assistant] Remove prompts from recall ranking Telemetry event (#214573)\n\nCloses https://github.com/elastic/obs-ai-assistant-team/issues/224\n\n## Summary\n\nRelates to https://github.com/elastic/obs-ai-assistant-team/issues/186\n\nRemoves the prompts from the recall ranking telemetry event.\n\n### Checklist\n\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":"43079c7603641f47853a370aef29f0512fe5e574"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
Candace Park
|
46933aaf1f
|
[9.0] [Defend Workflows][Eui Visual Refresh] Removed transparentize usage in responder (#208457) (#214860)
# Backport This will backport the following commits from `main` to `9.0`: - [[Defend Workflows][Eui Visual Refresh] Removed transparentize usage in responder (#208457)](https://github.com/elastic/kibana/pull/208457) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Candace Park","email":"56409205+parkiino@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-11T22:28:46Z","message":"[Defend Workflows][Eui Visual Refresh] Removed transparentize usage in responder (#208457)\n\n## Summary\r\n\r\n- [x] Removed use of color calculating function `transparentize()` \r\n- [x] Begin removal of JSON tokens when possible in favor of colors\r\ntokens\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"eac85d4d9971e6bc5164a7ff1abc20985af53159","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:Defend Workflows","EUI Visual Refresh","v9.1.0"],"title":"[Defend Workflows][Eui Visual Refresh] Removed transparentize usage in responder","number":208457,"url":"https://github.com/elastic/kibana/pull/208457","mergeCommit":{"message":"[Defend Workflows][Eui Visual Refresh] Removed transparentize usage in responder (#208457)\n\n## Summary\r\n\r\n- [x] Removed use of color calculating function `transparentize()` \r\n- [x] Begin removal of JSON tokens when possible in favor of colors\r\ntokens\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"eac85d4d9971e6bc5164a7ff1abc20985af53159"}},"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/208457","number":208457,"mergeCommit":{"message":"[Defend Workflows][Eui Visual Refresh] Removed transparentize usage in responder (#208457)\n\n## Summary\r\n\r\n- [x] Removed use of color calculating function `transparentize()` \r\n- [x] Begin removal of JSON tokens when possible in favor of colors\r\ntokens\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"eac85d4d9971e6bc5164a7ff1abc20985af53159"}}]}] BACKPORT--> |
||
Khristinin Nikita
|
7fd9a8309b
|
Enable gaps in 9.0 (#214847)
enable gaps in 9.0 Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
1864c03e60
|
[9.0] Unauthorized route migration for routes owned by kibana-presentation (#214783) (#214845)
# Backport This will backport the following commits from `main` to `9.0`: - [Unauthorized route migration for routes owned by kibana-presentation (#214783)](https://github.com/elastic/kibana/pull/214783) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T17:34:43Z","message":"Unauthorized route migration for routes owned by kibana-presentation (#214783)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"e5e42a87ea22d957000fe77a9e09929d9d45b5ff","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","Team:Presentation","release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration for routes owned by kibana-presentation","number":214783,"url":"https://github.com/elastic/kibana/pull/214783","mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-presentation (#214783)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"e5e42a87ea22d957000fe77a9e09929d9d45b5ff"}},"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/214783","number":214783,"mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-presentation (#214783)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"e5e42a87ea22d957000fe77a9e09929d9d45b5ff"}},{"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> |
||
|
Kibana Machine
|
9ea96f353a
|
[9.0] Unauthorized route migration for routes owned by kibana-esql (#214781) (#214836)
# Backport This will backport the following commits from `main` to `9.0`: - [Unauthorized route migration for routes owned by kibana-esql (#214781)](https://github.com/elastic/kibana/pull/214781) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T17:05:36Z","message":"Unauthorized route migration for routes owned by kibana-esql (#214781)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"a46e7cbfa398f8bcd4b74680bcd2799019902537","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Feature:Security/Authorization","backport:prev-minor","Team:ESQL","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration for routes owned by kibana-esql","number":214781,"url":"https://github.com/elastic/kibana/pull/214781","mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-esql (#214781)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"a46e7cbfa398f8bcd4b74680bcd2799019902537"}},"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/214781","number":214781,"mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-esql (#214781)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"a46e7cbfa398f8bcd4b74680bcd2799019902537"}},{"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> |
||
|
Kibana Machine
|
1b42e77e99
|
[9.0] Unauthorized route migration for routes owned by response-ops (#214785) (#214830)
# Backport This will backport the following commits from `main` to `9.0`: - [Unauthorized route migration for routes owned by response-ops (#214785)](https://github.com/elastic/kibana/pull/214785) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T16:08:59Z","message":"Unauthorized route migration for routes owned by response-ops (#214785)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"229dca52a613fbe88988f8afef154cd2fcc6d54e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Feature:Security/Authorization","Team:ResponseOps","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration for routes owned by response-ops","number":214785,"url":"https://github.com/elastic/kibana/pull/214785","mergeCommit":{"message":"Unauthorized route migration for routes owned by response-ops (#214785)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"229dca52a613fbe88988f8afef154cd2fcc6d54e"}},"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/214785","number":214785,"mergeCommit":{"message":"Unauthorized route migration for routes owned by response-ops (#214785)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"229dca52a613fbe88988f8afef154cd2fcc6d54e"}},{"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> |
||
wajihaparvez
|
3cbf60a903
|
[Docs] Add link to dependencies page - 9.0 (#214668)
## Summary This PR adds a page to the 9.0 Kibana docs linking to the list of third-party dependencies. Closes: [#212706](https://github.com/elastic/kibana/issues/212706) Rel: https://github.com/elastic/kibana/pull/214667, [#797](https://github.com/elastic/docs-content/pull/797) --------- Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
|
Kibana Machine
|
cd9388519a
|
[9.0] Unauthorized route migration for routes owned by stack-monitoring (#214787) (#214820)
# Backport This will backport the following commits from `main` to `9.0`: - [Unauthorized route migration for routes owned by stack-monitoring (#214787)](https://github.com/elastic/kibana/pull/214787) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T16:04:40Z","message":"Unauthorized route migration for routes owned by stack-monitoring (#214787)\n\n## Summary\n\nPassed security config to the core router, so it is correctly captured.\n\n\n### Checklist\n\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":"e93a63331a8ea7c18d23b989418d54cf64adec7b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","Team:Monitoring","release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration for routes owned by stack-monitoring","number":214787,"url":"https://github.com/elastic/kibana/pull/214787","mergeCommit":{"message":"Unauthorized route migration for routes owned by stack-monitoring (#214787)\n\n## Summary\n\nPassed security config to the core router, so it is correctly captured.\n\n\n### Checklist\n\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":"e93a63331a8ea7c18d23b989418d54cf64adec7b"}},"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/214787","number":214787,"mergeCommit":{"message":"Unauthorized route migration for routes owned by stack-monitoring (#214787)\n\n## Summary\n\nPassed security config to the core router, so it is correctly captured.\n\n\n### Checklist\n\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":"e93a63331a8ea7c18d23b989418d54cf64adec7b"}},{"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> |
||
Tiago Costa
|
41cf8f8780
|
skip flaky suite (#203607) | ||
|
Kibana Machine
|
eed49247ed | skip failing test suite (#214633) | ||
|
Kibana Machine
|
31e1cdcb68
|
[9.0] [Obs Overview] Replace clickable tooltip with external link (#213741) (#214800)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs Overview] Replace clickable tooltip with external link (#213741)](https://github.com/elastic/kibana/pull/213741) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bailey Cash","email":"bailey.cash@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T15:09:13Z","message":"[Obs Overview] Replace clickable tooltip with external link (#213741)\n\n## Summary\n\nResolves [this issue](https://github.com/elastic/kibana/issues/210168)\n\nVital links / clickable items should not be hidden behind tooltips that\nrequire an additional click, as they do not include necessary indicators\nfor screen readers. Converting the clickable tooltip with the core web\nvitals docs to a standard link.\n\n<img width=\"1727\" alt=\"Screenshot 2025-03-10 at 9 33 30 AM\"\nsrc=\"https://github.com/user-attachments/assets/ab611238-1fa1-455b-b0c4-563ae875e51d\"\n/>\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"26d84c4e1375362ef3a494fb9c9961c17e3ea1f8","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:current-major","obs-accessibilty","v9.1.0","v8.19.0"],"title":"[Obs Overview] Replace clickable tooltip with external link","number":213741,"url":"https://github.com/elastic/kibana/pull/213741","mergeCommit":{"message":"[Obs Overview] Replace clickable tooltip with external link (#213741)\n\n## Summary\n\nResolves [this issue](https://github.com/elastic/kibana/issues/210168)\n\nVital links / clickable items should not be hidden behind tooltips that\nrequire an additional click, as they do not include necessary indicators\nfor screen readers. Converting the clickable tooltip with the core web\nvitals docs to a standard link.\n\n<img width=\"1727\" alt=\"Screenshot 2025-03-10 at 9 33 30 AM\"\nsrc=\"https://github.com/user-attachments/assets/ab611238-1fa1-455b-b0c4-563ae875e51d\"\n/>\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"26d84c4e1375362ef3a494fb9c9961c17e3ea1f8"}},"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/213741","number":213741,"mergeCommit":{"message":"[Obs Overview] Replace clickable tooltip with external link (#213741)\n\n## Summary\n\nResolves [this issue](https://github.com/elastic/kibana/issues/210168)\n\nVital links / clickable items should not be hidden behind tooltips that\nrequire an additional click, as they do not include necessary indicators\nfor screen readers. Converting the clickable tooltip with the core web\nvitals docs to a standard link.\n\n<img width=\"1727\" alt=\"Screenshot 2025-03-10 at 9 33 30 AM\"\nsrc=\"https://github.com/user-attachments/assets/ab611238-1fa1-455b-b0c4-563ae875e51d\"\n/>\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"26d84c4e1375362ef3a494fb9c9961c17e3ea1f8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Bailey Cash <bailey.cash@elastic.co> |
||
|
Kibana Machine
|
51e0ea0070 | skip failing test suite (#209228) | ||
|
Kibana Machine
|
beec8a08cc
|
[9.0] [Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552) (#214790)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)](https://github.com/elastic/kibana/pull/214552) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mykola Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2025-03-17T14:27:33Z","message":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)\n\nCloses https://github.com/elastic/kibana/issues/212075\n\nThis change replaces the `--no-progress-meter` curl parameter with a\ncombination of `--silent` and `--show-error` to suppress verbose\nprogress output. `--no-progress-meter` was introduced in curl `v7.67.0`\nwhich is not available on some popular OSs like RHEL 8.\n\n## How to test\n\n1. Create an RHEL 8 instance in GCP and login via SSH\n2. Open auto detect flow on the Kibana instance deployed from this PR\n3. Go through the flow and make sure the auto detect script goes through\nall steps successfully","sha":"fabb1c9ffdb0870626d3031d454ae6229d1bb289","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","Feature: Observability Onboarding","backport:version","v8.18.0","v9.1.0","v8.17.4"],"title":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions","number":214552,"url":"https://github.com/elastic/kibana/pull/214552","mergeCommit":{"message":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)\n\nCloses https://github.com/elastic/kibana/issues/212075\n\nThis change replaces the `--no-progress-meter` curl parameter with a\ncombination of `--silent` and `--show-error` to suppress verbose\nprogress output. `--no-progress-meter` was introduced in curl `v7.67.0`\nwhich is not available on some popular OSs like RHEL 8.\n\n## How to test\n\n1. Create an RHEL 8 instance in GCP and login via SSH\n2. Open auto detect flow on the Kibana instance deployed from this PR\n3. Go through the flow and make sure the auto detect script goes through\nall steps successfully","sha":"fabb1c9ffdb0870626d3031d454ae6229d1bb289"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"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/214552","number":214552,"mergeCommit":{"message":"[Obs Onboarding][Auto Detect] Fix auto detect script failing on systems with older curl versions (#214552)\n\nCloses https://github.com/elastic/kibana/issues/212075\n\nThis change replaces the `--no-progress-meter` curl parameter with a\ncombination of `--silent` and `--show-error` to suppress verbose\nprogress output. `--no-progress-meter` was introduced in curl `v7.67.0`\nwhich is not available on some popular OSs like RHEL 8.\n\n## How to test\n\n1. Create an RHEL 8 instance in GCP and login via SSH\n2. Open auto detect flow on the Kibana instance deployed from this PR\n3. Go through the flow and make sure the auto detect script goes through\nall steps successfully","sha":"fabb1c9ffdb0870626d3031d454ae6229d1bb289"}},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Mykola Harmash <mykola.harmash@gmail.com> |
||
Ryland Herrick
|
f21cfa8825
|
[9.0] [Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510) (#214664)
# Backport This will backport the following commits from `main` to `9.0`: - [[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)](https://github.com/elastic/kibana/pull/213510) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-03-14T16:10:27Z","message":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)\n\nThis addresses some recent cypress failures: \n\n* https://github.com/elastic/kibana/issues/212743 (Rule Creation with a\nDataView)\n* https://github.com/elastic/kibana/issues/212742 (Rule Creation + Edit\nwith a DataView)\n* https://github.com/elastic/kibana/issues/213752 (Rule Creation +\nFilter with a DataView)\n\nThis appears (as much as a cypress failure can 😓) to be caused by an\nincorrect/false-positive assertion, leading to us (very occasionally)\ninteracting with the combobox before it's ready. We were calling\n`.should('not.be.disabled')` on an element that could never be disabled.\nBy calling that instead on the inner `input` that actually is\nenabled/disabled, we have the sanity check that was originally intended.\n\nThis PR also adds a post-action check (`.should('contains',\nthingThatWasTyped)`) so that if the action fails, the test doesn't fail\ninscrutably at a later step.\n\n### Evidence\n\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8003\n(50x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8004\n(200x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8033\n(200x)\n\n### Significance\n\n**Note also** that some initial investigation found this pattern in\nseveral places in our test suite. I'm going to follow up on this focused\nPR with a more comprehensive one (once this is proven out in the flaky\nrunner).\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- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"02409dbd65c0262022cdee918e6651d8afc7b330","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-major","Team:Detection Engine","v8.18.0","v9.1.0","v8.19.0"],"title":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component","number":213510,"url":"https://github.com/elastic/kibana/pull/213510","mergeCommit":{"message":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)\n\nThis addresses some recent cypress failures: \n\n* https://github.com/elastic/kibana/issues/212743 (Rule Creation with a\nDataView)\n* https://github.com/elastic/kibana/issues/212742 (Rule Creation + Edit\nwith a DataView)\n* https://github.com/elastic/kibana/issues/213752 (Rule Creation +\nFilter with a DataView)\n\nThis appears (as much as a cypress failure can 😓) to be caused by an\nincorrect/false-positive assertion, leading to us (very occasionally)\ninteracting with the combobox before it's ready. We were calling\n`.should('not.be.disabled')` on an element that could never be disabled.\nBy calling that instead on the inner `input` that actually is\nenabled/disabled, we have the sanity check that was originally intended.\n\nThis PR also adds a post-action check (`.should('contains',\nthingThatWasTyped)`) so that if the action fails, the test doesn't fail\ninscrutably at a later step.\n\n### Evidence\n\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8003\n(50x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8004\n(200x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8033\n(200x)\n\n### Significance\n\n**Note also** that some initial investigation found this pattern in\nseveral places in our test suite. I'm going to follow up on this focused\nPR with a more comprehensive one (once this is proven out in the flaky\nrunner).\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- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"02409dbd65c0262022cdee918e6651d8afc7b330"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214605","number":214605,"state":"MERGED","mergeCommit":{"sha":"9ecdbde42dd917593ad40da9bd53e45d4ea66112","message":"[8.18] [Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510) (#214605)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[Detection Engine] Cypress - Add more robust selection from our\nDataView dropdown component\n(#213510)](https://github.com/elastic/kibana/pull/213510)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Ryland Herrick <ryalnd@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213510","number":213510,"mergeCommit":{"message":"[Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510)\n\nThis addresses some recent cypress failures: \n\n* https://github.com/elastic/kibana/issues/212743 (Rule Creation with a\nDataView)\n* https://github.com/elastic/kibana/issues/212742 (Rule Creation + Edit\nwith a DataView)\n* https://github.com/elastic/kibana/issues/213752 (Rule Creation +\nFilter with a DataView)\n\nThis appears (as much as a cypress failure can 😓) to be caused by an\nincorrect/false-positive assertion, leading to us (very occasionally)\ninteracting with the combobox before it's ready. We were calling\n`.should('not.be.disabled')` on an element that could never be disabled.\nBy calling that instead on the inner `input` that actually is\nenabled/disabled, we have the sanity check that was originally intended.\n\nThis PR also adds a post-action check (`.should('contains',\nthingThatWasTyped)`) so that if the action fails, the test doesn't fail\ninscrutably at a later step.\n\n### Evidence\n\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8003\n(50x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8004\n(200x)\n*\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/8033\n(200x)\n\n### Significance\n\n**Note also** that some initial investigation found this pattern in\nseveral places in our test suite. I'm going to follow up on this focused\nPR with a more comprehensive one (once this is proven out in the flaky\nrunner).\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- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"02409dbd65c0262022cdee918e6651d8afc7b330"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214606","number":214606,"state":"MERGED","mergeCommit":{"sha":"43da70a9c508e760f4cc648d9f28824c0b46c45e","message":"[8.x] [Detection Engine] Cypress - Add more robust selection from our DataView dropdown component (#213510) (#214606)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Detection Engine] Cypress - Add more robust selection from our\nDataView dropdown component\n(#213510)](https://github.com/elastic/kibana/pull/213510)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Ryland Herrick <ryalnd@gmail.com>"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
5c8e1a4726
|
[9.0] Convert Alert and Action Settings yaml strings to Markdown (#214642) (#214806)
# Backport This will backport the following commits from `main` to `9.0`: - [Convert Alert and Action Settings yaml strings to Markdown (#214642)](https://github.com/elastic/kibana/pull/214642) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Kilfoyle","email":"41695641+kilfoyle@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T15:39:26Z","message":"Convert Alert and Action Settings yaml strings to Markdown (#214642)\n\nThis PR:\n- Makes a backup copy of the `kibana-alert-action-settings.yml` file\njust in case I mess things up badly.\n- Converts all of the descriptions and examples in the original file to\nMarkdown format.\n - Adds the versioning info as follows:\n - supported on ESS/ECH:\n ```\n applies_to:\n stack: ga\n deployment:\n self: ga\n ess: ga\n ``` \n - not supported on ESS/ECH:\n ```\n applies_to:\n stack: ga\n deployment:\n self: ga\n ``` \n\nIn the current Kibana settings docs we indicate settings available on\nESS/ECH. We don't indicate anything for other deployment types such as\nECK or ECE. I assume that no settings are available on Serverless. So,\nthe above versioning basically just copies what we document currently.\n\nOnce merged, I expect that we can test rendering the docs HTML pages\n(like [this\none](https://www.elastic.co/guide/en/kibana/8.x/alert-action-settings-kb.html))\ndirectly from this [YAML\nsource](https://github.com/elastic/kibana/blob/main/docs/settings-gen/source/kibana-alert-action-settings.yml).\n\n@florent-leborgne and @wajihaparvez Sorry, I know this is kind of big.\nI'd appreciate any input, especially on the versioning / `applies_to`\npart since that's still a bit new.\n\nJust for my own reference, I cut and pasted all of the Markdown from\n[here](https://github.com/elastic/asciidocalypse/blob/main/docs/kibana/docs/reference/configuration-reference/alerting-settings.md?plain=1).\n\nCloses: https://github.com/elastic/ingest-docs/issues/1659","sha":"be351d3c973978f56d8b527d4878911e0ade68eb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","backport:version","v9.1.0"],"title":"Convert Alert and Action Settings yaml strings to Markdown","number":214642,"url":"https://github.com/elastic/kibana/pull/214642","mergeCommit":{"message":"Convert Alert and Action Settings yaml strings to Markdown (#214642)\n\nThis PR:\n- Makes a backup copy of the `kibana-alert-action-settings.yml` file\njust in case I mess things up badly.\n- Converts all of the descriptions and examples in the original file to\nMarkdown format.\n - Adds the versioning info as follows:\n - supported on ESS/ECH:\n ```\n applies_to:\n stack: ga\n deployment:\n self: ga\n ess: ga\n ``` \n - not supported on ESS/ECH:\n ```\n applies_to:\n stack: ga\n deployment:\n self: ga\n ``` \n\nIn the current Kibana settings docs we indicate settings available on\nESS/ECH. We don't indicate anything for other deployment types such as\nECK or ECE. I assume that no settings are available on Serverless. So,\nthe above versioning basically just copies what we document currently.\n\nOnce merged, I expect that we can test rendering the docs HTML pages\n(like [this\none](https://www.elastic.co/guide/en/kibana/8.x/alert-action-settings-kb.html))\ndirectly from this [YAML\nsource](https://github.com/elastic/kibana/blob/main/docs/settings-gen/source/kibana-alert-action-settings.yml).\n\n@florent-leborgne and @wajihaparvez Sorry, I know this is kind of big.\nI'd appreciate any input, especially on the versioning / `applies_to`\npart since that's still a bit new.\n\nJust for my own reference, I cut and pasted all of the Markdown from\n[here](https://github.com/elastic/asciidocalypse/blob/main/docs/kibana/docs/reference/configuration-reference/alerting-settings.md?plain=1).\n\nCloses: https://github.com/elastic/ingest-docs/issues/1659","sha":"be351d3c973978f56d8b527d4878911e0ade68eb"}},"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/214642","number":214642,"mergeCommit":{"message":"Convert Alert and Action Settings yaml strings to Markdown (#214642)\n\nThis PR:\n- Makes a backup copy of the `kibana-alert-action-settings.yml` file\njust in case I mess things up badly.\n- Converts all of the descriptions and examples in the original file to\nMarkdown format.\n - Adds the versioning info as follows:\n - supported on ESS/ECH:\n ```\n applies_to:\n stack: ga\n deployment:\n self: ga\n ess: ga\n ``` \n - not supported on ESS/ECH:\n ```\n applies_to:\n stack: ga\n deployment:\n self: ga\n ``` \n\nIn the current Kibana settings docs we indicate settings available on\nESS/ECH. We don't indicate anything for other deployment types such as\nECK or ECE. I assume that no settings are available on Serverless. So,\nthe above versioning basically just copies what we document currently.\n\nOnce merged, I expect that we can test rendering the docs HTML pages\n(like [this\none](https://www.elastic.co/guide/en/kibana/8.x/alert-action-settings-kb.html))\ndirectly from this [YAML\nsource](https://github.com/elastic/kibana/blob/main/docs/settings-gen/source/kibana-alert-action-settings.yml).\n\n@florent-leborgne and @wajihaparvez Sorry, I know this is kind of big.\nI'd appreciate any input, especially on the versioning / `applies_to`\npart since that's still a bit new.\n\nJust for my own reference, I cut and pasted all of the Markdown from\n[here](https://github.com/elastic/asciidocalypse/blob/main/docs/kibana/docs/reference/configuration-reference/alerting-settings.md?plain=1).\n\nCloses: https://github.com/elastic/ingest-docs/issues/1659","sha":"be351d3c973978f56d8b527d4878911e0ade68eb"}}]}] BACKPORT--> Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> |
||
|
Kibana Machine
|
88b05d2315
|
[9.0] [Inference Endpoints] Fix non-required secret fields getting mangled (#214159) (#214753)
# Backport This will backport the following commits from `main` to `9.0`: - [[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)](https://github.com/elastic/kibana/pull/214159) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T13:12:17Z","message":"[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)\n\nThis fixes an issue with the inference flyout where a 'secret' field\nthat wasn't required would defocus after every keypress. This happened\nbecause the validation accidentally removed those secrets from the\nschema, which forced a destruction of the components, and then on the\nnext render they got added back in.\n\nThis fixes that by no longer filtering out documents in the validation,\nbut only mapping them.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cb6f8bbd3a0545eba76ef6cb3969a33377a4fa25","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:Search","backport:all-open","v9.1.0","v8.19.0","v8.18.1"],"title":"[Inference Endpoints] Fix non-required secret fields getting mangled","number":214159,"url":"https://github.com/elastic/kibana/pull/214159","mergeCommit":{"message":"[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)\n\nThis fixes an issue with the inference flyout where a 'secret' field\nthat wasn't required would defocus after every keypress. This happened\nbecause the validation accidentally removed those secrets from the\nschema, which forced a destruction of the components, and then on the\nnext render they got added back in.\n\nThis fixes that by no longer filtering out documents in the validation,\nbut only mapping them.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cb6f8bbd3a0545eba76ef6cb3969a33377a4fa25"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x","8.18"],"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/214159","number":214159,"mergeCommit":{"message":"[Inference Endpoints] Fix non-required secret fields getting mangled (#214159)\n\nThis fixes an issue with the inference flyout where a 'secret' field\nthat wasn't required would defocus after every keypress. This happened\nbecause the validation accidentally removed those secrets from the\nschema, which forced a destruction of the components, and then on the\nnext render they got added back in.\n\nThis fixes that by no longer filtering out documents in the validation,\nbut only mapping them.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cb6f8bbd3a0545eba76ef6cb3969a33377a4fa25"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
c129ade30c
|
[9.0] [ES|QL] Fixes the comment autocomplete when there is a space (#214696) (#214757)
# Backport This will backport the following commits from `main` to `9.0`: - [[ES|QL] Fixes the comment autocomplete when there is a space (#214696)](https://github.com/elastic/kibana/pull/214696) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T13:07:09Z","message":"[ES|QL] Fixes the comment autocomplete when there is a space (#214696)\n\n## Summary\n\nFixes the problem with autocomplete been triggered in comments\n\n**Before**\n\n (#213801) (#214744)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)](https://github.com/elastic/kibana/pull/213801) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Edgar Santos","email":"edgar.santos@elastic.co"},"sourceCommit":{"committedDate":"2025-03-17T12:56:13Z","message":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)\n\n# Summary\nThis PR changes the behavior of the Preview rule button in the create\nrule form. Now the button will always be enabled, but upon clicking it\nthe validation of the define rule form will be triggered. If the form is\ninvalid, it will show a warning redirecting the user to the form in\norder to fix the errors.\n\nThis PR removes the helper function `getIsRulePreviewDisabled` after\nverifying that all the validations that it was doing are already covered\nby the validation rules of the define rule form.\n\n\nThis solves issue #173930\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"07baf3a79f5d2e37ba2a4823c3c4ef339684959d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Feature:Detection Rules","Feature:Detection Rule Preview","Team:Detection Engine","backport:version","v8.18.0","v9.1.0","v8.17.4"],"title":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930)","number":213801,"url":"https://github.com/elastic/kibana/pull/213801","mergeCommit":{"message":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)\n\n# Summary\nThis PR changes the behavior of the Preview rule button in the create\nrule form. Now the button will always be enabled, but upon clicking it\nthe validation of the define rule form will be triggered. If the form is\ninvalid, it will show a warning redirecting the user to the form in\norder to fix the errors.\n\nThis PR removes the helper function `getIsRulePreviewDisabled` after\nverifying that all the validations that it was doing are already covered\nby the validation rules of the define rule form.\n\n\nThis solves issue #173930\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"07baf3a79f5d2e37ba2a4823c3c4ef339684959d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.17"],"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/213801","number":213801,"mergeCommit":{"message":"[Security Solution][Detection Engine] fixes rule preview works for form's invalid state (#173930) (#213801)\n\n# Summary\nThis PR changes the behavior of the Preview rule button in the create\nrule form. Now the button will always be enabled, but upon clicking it\nthe validation of the define rule form will be triggered. If the form is\ninvalid, it will show a warning redirecting the user to the form in\norder to fix the errors.\n\nThis PR removes the helper function `getIsRulePreviewDisabled` after\nverifying that all the validations that it was doing are already covered\nby the validation rules of the define rule form.\n\n\nThis solves issue #173930\n\n---------\n\nCo-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>","sha":"07baf3a79f5d2e37ba2a4823c3c4ef339684959d"}},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Edgar Santos <edgar.santos@elastic.co> |
||
|
Kibana Machine
|
c8e9793ab3
|
[9.0] [Search] Fix top padding on create index to be consistent (#214188) (#214735)
# Backport This will backport the following commits from `main` to `9.0`: - [[Search] Fix top padding on create index to be consistent (#214188)](https://github.com/elastic/kibana/pull/214188) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T12:52:58Z","message":"[Search] Fix top padding on create index to be consistent (#214188)\n\n## Summary\n\nThis fixes the top padding on the create index page jumping around. \n\nBefore:\n\n\n |
||
|
Kibana Machine
|
5de3b67a96
|
[9.0] [Automatic Import] Fix chunking of samples in ecs mapping (#214702) (#214739)
# Backport This will backport the following commits from `main` to `9.0`: - [[Automatic Import] Fix chunking of samples in ecs mapping (#214702)](https://github.com/elastic/kibana/pull/214702) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bharat Pasupula","email":"123897612+bhapas@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T12:52:37Z","message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix chunking of samples in ecs mapping","number":214702,"url":"https://github.com/elastic/kibana/pull/214702","mergeCommit":{"message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309"}},"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/214702","number":214702,"mergeCommit":{"message":"[Automatic Import] Fix chunking of samples in ecs mapping (#214702)","sha":"059e7e7c52076298537a4faf351ae77eb0563309"}}]}] BACKPORT--> Co-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com> |
||
Christos Nasikas
|
542d800c42
|
[9.0] [Cases] Improve unit test flakiness (#212489) (#214686)
# Backport This will backport the following commits from `main` to `9.0`: - [[Cases] Improve unit test flakiness (#212489)](https://github.com/elastic/kibana/pull/212489) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Christos Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T17:17:13Z","message":"[Cases] Improve unit test flakiness (#212489)\n\n## Summary\n\nThis PR attempts (I have lost count of how many there have been so far)\nto stabilize the flakiness of cases tests.\n\n## Approach\n\nBased on our investigations, I believe a common factor that causes all\ntests to time out is how we wrap the tests with the needed providers.\nInstead of figuring out why they time out (which is very difficult), I\ntried a different approach. I rewrote how we initialize the testing\ndependencies, mocks, and providers on tests. To test my theory, I\ncreated a VM instance in GCloud with the same configuration as the one\nrunning in the CI, specifically the n2-standard-4 (4 vCPUs, 16 GB\nMemory) machine type. I ran the tests 100 times, which took almost two\ndays. In 10 of the runs, a random test was timeouted. I noticed that the\nmachine was stressed while running the tests, and the CPU frequently\nspiked to 100%, especially at the beginning of each test. Then, I\nincreased the timeout for all cases tests to 10 seconds and ran the\ntests again 100 times. No timeouts occurred. Lastly, I created a VM\ninstance in GCloud with the same configuration as the one running in the\nCI, specifically the n2-standard-8 (8 vCPUs, 32 GB Memory) machine type.\nI ran the tests again 100 times. In 1 of the runs, a random test was\ntimeouted. The machine on the CI cannot handle the cases tests. I\nbelieve the work in this PR is a step in the right direction either way,\nand we will benefit from it. I also believe increasing the timeout is a\ngood decision as we need it based on the experiments and the research we\nhave done in the last months.\n\nCPU usage on n2-standard-4\n\n\nhttps://github.com/user-attachments/assets/36b035df-310f-4906-98ba-688d57b97c7e\n\nCPU usage on n2-standard-8\n\n\nhttps://github.com/user-attachments/assets/3b1b6351-d48e-41da-a413-a56e52b54b82\n\n## RLT eslint rules\nI enabled the [RLT eslint\nrules](https://testing-library.com/docs/ecosystem-eslint-plugin-testing-library/)\nfor Cases and resolved any eslint errors. The process revealed small\nbugs in the tests, which I fixed them.\n\n## Testing utils\n\nI removed the `appMockRender` and any usage in favor of the new\n`renderWithTestingProviders` utility function and the improved\n`TestProviders` component. The `renderWithTestingProviders` follows the\nprincipals\n[suggested](https://github.com/testing-library/react-testing-library/issues/780#issuecomment-689053441)\nby the RLT team. Specifically:\n- The `renderWithTestingProviders` is a wrapper of the `render` function\nof the RTL library.\n- The `renderWithTestingProviders` does not create the services or any\ncomponent inside it.\n- The `renderWithTestingProviders` cannot be used in `beforeEach`\nfunctions. It should be called separately on each test.\n- The `renderWithTestingProviders` accepts props to override the default\nmocks.\n- The `renderWithTestingProviders` passes the `TestProviders` in the\n`wrapper` argument of the RLT `render` function.\n- The `TestProviders` component initializes and memoizes all services\nand dependencies. It accepts props to override the default mocks.\n- Mock overrides (like core services) should be created and passed to\n`renderWithTestingProviders` on each test, even if it means duplication.\nWe favor test isolation.\n\n### Checklist\n\nCheck the PR satisfies the following conditions. \n\nReviewers should verify this PR satisfies this list as well.\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## Issues\n<details>\n<summary>List</summary>\n\nFixes: https://github.com/elastic/kibana/issues/207712\nFixes: https://github.com/elastic/kibana/issues/192739\nFixes: https://github.com/elastic/kibana/issues/174682\nFixes: https://github.com/elastic/kibana/issues/206366\nFixes: https://github.com/elastic/kibana/issues/207427\nFixes: https://github.com/elastic/kibana/issues/175239\nFixes: https://github.com/elastic/kibana/issues/177334\nFixes: https://github.com/elastic/kibana/issues/208443\nFixes: https://github.com/elastic/kibana/issues/187526\nFixes: https://github.com/elastic/kibana/issues/208310\nFixes: https://github.com/elastic/kibana/issues/192640\nFixes: https://github.com/elastic/kibana/issues/207077\nFixes: https://github.com/elastic/kibana/issues/197304\nFixes: https://github.com/elastic/kibana/issues/207249\nFixes: https://github.com/elastic/kibana/issues/202761\nFixes: https://github.com/elastic/kibana/issues/202115\nFixes: https://github.com/elastic/kibana/issues/193026\nFixes: https://github.com/elastic/kibana/issues/177304\nFixes: https://github.com/elastic/kibana/issues/208415\nFixes: https://github.com/elastic/kibana/issues/174661\nFixes: https://github.com/elastic/kibana/issues/201611\nFixes: https://github.com/elastic/kibana/issues/182364\nFixes: https://github.com/elastic/kibana/issues/175841\nFixes: https://github.com/elastic/kibana/issues/207907\nFixes: https://github.com/elastic/kibana/issues/171177\nFixes: https://github.com/elastic/kibana/issues/196628\nFixes: https://github.com/elastic/kibana/issues/194703\nFixes: https://github.com/elastic/kibana/issues/207241\nFixes: https://github.com/elastic/kibana/issues/206056\nFixes: https://github.com/elastic/kibana/issues/207328\nFixes: https://github.com/elastic/kibana/issues/205953\nFixes: https://github.com/elastic/kibana/issues/176524\nFixes: https://github.com/elastic/kibana/issues/176335\nFixes: https://github.com/elastic/kibana/issues/207404\nFixes: https://github.com/elastic/kibana/issues/207384\nFixes: https://github.com/elastic/kibana/issues/208380\nFixes: https://github.com/elastic/kibana/issues/207248\nFixes: https://github.com/elastic/kibana/issues/207444\nFixes: https://github.com/elastic/kibana/issues/175240\nFixes: https://github.com/elastic/kibana/issues/178001\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1054799f9c1139c52d74c9c588f60177182919c7","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","Feature:Cases","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Cases] Improve unit test flakiness","number":212489,"url":"https://github.com/elastic/kibana/pull/212489","mergeCommit":{"message":"[Cases] Improve unit test flakiness (#212489)\n\n## Summary\n\nThis PR attempts (I have lost count of how many there have been so far)\nto stabilize the flakiness of cases tests.\n\n## Approach\n\nBased on our investigations, I believe a common factor that causes all\ntests to time out is how we wrap the tests with the needed providers.\nInstead of figuring out why they time out (which is very difficult), I\ntried a different approach. I rewrote how we initialize the testing\ndependencies, mocks, and providers on tests. To test my theory, I\ncreated a VM instance in GCloud with the same configuration as the one\nrunning in the CI, specifically the n2-standard-4 (4 vCPUs, 16 GB\nMemory) machine type. I ran the tests 100 times, which took almost two\ndays. In 10 of the runs, a random test was timeouted. I noticed that the\nmachine was stressed while running the tests, and the CPU frequently\nspiked to 100%, especially at the beginning of each test. Then, I\nincreased the timeout for all cases tests to 10 seconds and ran the\ntests again 100 times. No timeouts occurred. Lastly, I created a VM\ninstance in GCloud with the same configuration as the one running in the\nCI, specifically the n2-standard-8 (8 vCPUs, 32 GB Memory) machine type.\nI ran the tests again 100 times. In 1 of the runs, a random test was\ntimeouted. The machine on the CI cannot handle the cases tests. I\nbelieve the work in this PR is a step in the right direction either way,\nand we will benefit from it. I also believe increasing the timeout is a\ngood decision as we need it based on the experiments and the research we\nhave done in the last months.\n\nCPU usage on n2-standard-4\n\n\nhttps://github.com/user-attachments/assets/36b035df-310f-4906-98ba-688d57b97c7e\n\nCPU usage on n2-standard-8\n\n\nhttps://github.com/user-attachments/assets/3b1b6351-d48e-41da-a413-a56e52b54b82\n\n## RLT eslint rules\nI enabled the [RLT eslint\nrules](https://testing-library.com/docs/ecosystem-eslint-plugin-testing-library/)\nfor Cases and resolved any eslint errors. The process revealed small\nbugs in the tests, which I fixed them.\n\n## Testing utils\n\nI removed the `appMockRender` and any usage in favor of the new\n`renderWithTestingProviders` utility function and the improved\n`TestProviders` component. The `renderWithTestingProviders` follows the\nprincipals\n[suggested](https://github.com/testing-library/react-testing-library/issues/780#issuecomment-689053441)\nby the RLT team. Specifically:\n- The `renderWithTestingProviders` is a wrapper of the `render` function\nof the RTL library.\n- The `renderWithTestingProviders` does not create the services or any\ncomponent inside it.\n- The `renderWithTestingProviders` cannot be used in `beforeEach`\nfunctions. It should be called separately on each test.\n- The `renderWithTestingProviders` accepts props to override the default\nmocks.\n- The `renderWithTestingProviders` passes the `TestProviders` in the\n`wrapper` argument of the RLT `render` function.\n- The `TestProviders` component initializes and memoizes all services\nand dependencies. It accepts props to override the default mocks.\n- Mock overrides (like core services) should be created and passed to\n`renderWithTestingProviders` on each test, even if it means duplication.\nWe favor test isolation.\n\n### Checklist\n\nCheck the PR satisfies the following conditions. \n\nReviewers should verify this PR satisfies this list as well.\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## Issues\n<details>\n<summary>List</summary>\n\nFixes: https://github.com/elastic/kibana/issues/207712\nFixes: https://github.com/elastic/kibana/issues/192739\nFixes: https://github.com/elastic/kibana/issues/174682\nFixes: https://github.com/elastic/kibana/issues/206366\nFixes: https://github.com/elastic/kibana/issues/207427\nFixes: https://github.com/elastic/kibana/issues/175239\nFixes: https://github.com/elastic/kibana/issues/177334\nFixes: https://github.com/elastic/kibana/issues/208443\nFixes: https://github.com/elastic/kibana/issues/187526\nFixes: https://github.com/elastic/kibana/issues/208310\nFixes: https://github.com/elastic/kibana/issues/192640\nFixes: https://github.com/elastic/kibana/issues/207077\nFixes: https://github.com/elastic/kibana/issues/197304\nFixes: https://github.com/elastic/kibana/issues/207249\nFixes: https://github.com/elastic/kibana/issues/202761\nFixes: https://github.com/elastic/kibana/issues/202115\nFixes: https://github.com/elastic/kibana/issues/193026\nFixes: https://github.com/elastic/kibana/issues/177304\nFixes: https://github.com/elastic/kibana/issues/208415\nFixes: https://github.com/elastic/kibana/issues/174661\nFixes: https://github.com/elastic/kibana/issues/201611\nFixes: https://github.com/elastic/kibana/issues/182364\nFixes: https://github.com/elastic/kibana/issues/175841\nFixes: https://github.com/elastic/kibana/issues/207907\nFixes: https://github.com/elastic/kibana/issues/171177\nFixes: https://github.com/elastic/kibana/issues/196628\nFixes: https://github.com/elastic/kibana/issues/194703\nFixes: https://github.com/elastic/kibana/issues/207241\nFixes: https://github.com/elastic/kibana/issues/206056\nFixes: https://github.com/elastic/kibana/issues/207328\nFixes: https://github.com/elastic/kibana/issues/205953\nFixes: https://github.com/elastic/kibana/issues/176524\nFixes: https://github.com/elastic/kibana/issues/176335\nFixes: https://github.com/elastic/kibana/issues/207404\nFixes: https://github.com/elastic/kibana/issues/207384\nFixes: https://github.com/elastic/kibana/issues/208380\nFixes: https://github.com/elastic/kibana/issues/207248\nFixes: https://github.com/elastic/kibana/issues/207444\nFixes: https://github.com/elastic/kibana/issues/175240\nFixes: https://github.com/elastic/kibana/issues/178001\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1054799f9c1139c52d74c9c588f60177182919c7"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"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,"url":"https://github.com/elastic/kibana/pull/214676","number":214676,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212489","number":212489,"mergeCommit":{"message":"[Cases] Improve unit test flakiness (#212489)\n\n## Summary\n\nThis PR attempts (I have lost count of how many there have been so far)\nto stabilize the flakiness of cases tests.\n\n## Approach\n\nBased on our investigations, I believe a common factor that causes all\ntests to time out is how we wrap the tests with the needed providers.\nInstead of figuring out why they time out (which is very difficult), I\ntried a different approach. I rewrote how we initialize the testing\ndependencies, mocks, and providers on tests. To test my theory, I\ncreated a VM instance in GCloud with the same configuration as the one\nrunning in the CI, specifically the n2-standard-4 (4 vCPUs, 16 GB\nMemory) machine type. I ran the tests 100 times, which took almost two\ndays. In 10 of the runs, a random test was timeouted. I noticed that the\nmachine was stressed while running the tests, and the CPU frequently\nspiked to 100%, especially at the beginning of each test. Then, I\nincreased the timeout for all cases tests to 10 seconds and ran the\ntests again 100 times. No timeouts occurred. Lastly, I created a VM\ninstance in GCloud with the same configuration as the one running in the\nCI, specifically the n2-standard-8 (8 vCPUs, 32 GB Memory) machine type.\nI ran the tests again 100 times. In 1 of the runs, a random test was\ntimeouted. The machine on the CI cannot handle the cases tests. I\nbelieve the work in this PR is a step in the right direction either way,\nand we will benefit from it. I also believe increasing the timeout is a\ngood decision as we need it based on the experiments and the research we\nhave done in the last months.\n\nCPU usage on n2-standard-4\n\n\nhttps://github.com/user-attachments/assets/36b035df-310f-4906-98ba-688d57b97c7e\n\nCPU usage on n2-standard-8\n\n\nhttps://github.com/user-attachments/assets/3b1b6351-d48e-41da-a413-a56e52b54b82\n\n## RLT eslint rules\nI enabled the [RLT eslint\nrules](https://testing-library.com/docs/ecosystem-eslint-plugin-testing-library/)\nfor Cases and resolved any eslint errors. The process revealed small\nbugs in the tests, which I fixed them.\n\n## Testing utils\n\nI removed the `appMockRender` and any usage in favor of the new\n`renderWithTestingProviders` utility function and the improved\n`TestProviders` component. The `renderWithTestingProviders` follows the\nprincipals\n[suggested](https://github.com/testing-library/react-testing-library/issues/780#issuecomment-689053441)\nby the RLT team. Specifically:\n- The `renderWithTestingProviders` is a wrapper of the `render` function\nof the RTL library.\n- The `renderWithTestingProviders` does not create the services or any\ncomponent inside it.\n- The `renderWithTestingProviders` cannot be used in `beforeEach`\nfunctions. It should be called separately on each test.\n- The `renderWithTestingProviders` accepts props to override the default\nmocks.\n- The `renderWithTestingProviders` passes the `TestProviders` in the\n`wrapper` argument of the RLT `render` function.\n- The `TestProviders` component initializes and memoizes all services\nand dependencies. It accepts props to override the default mocks.\n- Mock overrides (like core services) should be created and passed to\n`renderWithTestingProviders` on each test, even if it means duplication.\nWe favor test isolation.\n\n### Checklist\n\nCheck the PR satisfies the following conditions. \n\nReviewers should verify this PR satisfies this list as well.\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## Issues\n<details>\n<summary>List</summary>\n\nFixes: https://github.com/elastic/kibana/issues/207712\nFixes: https://github.com/elastic/kibana/issues/192739\nFixes: https://github.com/elastic/kibana/issues/174682\nFixes: https://github.com/elastic/kibana/issues/206366\nFixes: https://github.com/elastic/kibana/issues/207427\nFixes: https://github.com/elastic/kibana/issues/175239\nFixes: https://github.com/elastic/kibana/issues/177334\nFixes: https://github.com/elastic/kibana/issues/208443\nFixes: https://github.com/elastic/kibana/issues/187526\nFixes: https://github.com/elastic/kibana/issues/208310\nFixes: https://github.com/elastic/kibana/issues/192640\nFixes: https://github.com/elastic/kibana/issues/207077\nFixes: https://github.com/elastic/kibana/issues/197304\nFixes: https://github.com/elastic/kibana/issues/207249\nFixes: https://github.com/elastic/kibana/issues/202761\nFixes: https://github.com/elastic/kibana/issues/202115\nFixes: https://github.com/elastic/kibana/issues/193026\nFixes: https://github.com/elastic/kibana/issues/177304\nFixes: https://github.com/elastic/kibana/issues/208415\nFixes: https://github.com/elastic/kibana/issues/174661\nFixes: https://github.com/elastic/kibana/issues/201611\nFixes: https://github.com/elastic/kibana/issues/182364\nFixes: https://github.com/elastic/kibana/issues/175841\nFixes: https://github.com/elastic/kibana/issues/207907\nFixes: https://github.com/elastic/kibana/issues/171177\nFixes: https://github.com/elastic/kibana/issues/196628\nFixes: https://github.com/elastic/kibana/issues/194703\nFixes: https://github.com/elastic/kibana/issues/207241\nFixes: https://github.com/elastic/kibana/issues/206056\nFixes: https://github.com/elastic/kibana/issues/207328\nFixes: https://github.com/elastic/kibana/issues/205953\nFixes: https://github.com/elastic/kibana/issues/176524\nFixes: https://github.com/elastic/kibana/issues/176335\nFixes: https://github.com/elastic/kibana/issues/207404\nFixes: https://github.com/elastic/kibana/issues/207384\nFixes: https://github.com/elastic/kibana/issues/208380\nFixes: https://github.com/elastic/kibana/issues/207248\nFixes: https://github.com/elastic/kibana/issues/207444\nFixes: https://github.com/elastic/kibana/issues/175240\nFixes: https://github.com/elastic/kibana/issues/178001\n\n</details>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1054799f9c1139c52d74c9c588f60177182919c7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214675","number":214675,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
Kibana Machine
|
0ce508ea46
|
[9.0] [Core] Added reason for opting out of authz (#213878) (#214723)
# Backport This will backport the following commits from `main` to `9.0`: - [[Core] Added reason for opting out of authz (#213878)](https://github.com/elastic/kibana/pull/213878) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T11:42:05Z","message":"[Core] Added reason for opting out of authz (#213878)\n\n## Summary\n\nAdded reason for opting out of authz for routes.\n\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- [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":"4008c1f24e68bb3837f12c60e3d472926aa80ac4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"[Core] Added reason for opting out of authz","number":213878,"url":"https://github.com/elastic/kibana/pull/213878","mergeCommit":{"message":"[Core] Added reason for opting out of authz (#213878)\n\n## Summary\n\nAdded reason for opting out of authz for routes.\n\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- [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":"4008c1f24e68bb3837f12c60e3d472926aa80ac4"}},"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/213878","number":213878,"mergeCommit":{"message":"[Core] Added reason for opting out of authz (#213878)\n\n## Summary\n\nAdded reason for opting out of authz for routes.\n\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- [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":"4008c1f24e68bb3837f12c60e3d472926aa80ac4"}},{"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> |
||
Dmitrii Shevchenko
|
8e87c2f673
|
[9.0] [Security Solution] Remove the customization check when importing rules (#214577) (#214648)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Remove the customization check when importing rules (#214577)](https://github.com/elastic/kibana/pull/214577) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dmitrii Shevchenko","email":"dmitrii.shevchenko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T19:14:32Z","message":"[Security Solution] Remove the customization check when importing rules (#214577)","sha":"67d6707715b5508d44666a068ffd5a00cfa92e08","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:Detections and Resp","Team: SecuritySolution","Team:Detection Rule Management","Feature:Prebuilt Detection Rules","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Remove the customization check when importing rules","number":214577,"url":"https://github.com/elastic/kibana/pull/214577","mergeCommit":{"message":"[Security Solution] Remove the customization check when importing rules (#214577)","sha":"67d6707715b5508d44666a068ffd5a00cfa92e08"}},"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/214577","number":214577,"mergeCommit":{"message":"[Security Solution] Remove the customization check when importing rules (#214577)","sha":"67d6707715b5508d44666a068ffd5a00cfa92e08"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co> |
||
|
Kibana Machine
|
8851b348ae
|
[9.0] [SecuritySolution] Fix Risk score Insufficient privileges warning missing cluster privileges (#212405) (#213344)
# Backport This will backport the following commits from `main` to `9.0`: - [[SecuritySolution] Fix Risk score Insufficient privileges warning missing cluster privileges (#212405)](https://github.com/elastic/kibana/pull/212405) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-03-06T09:51:08Z","message":"[SecuritySolution] Fix Risk score Insufficient privileges warning missing cluster privileges (#212405)\n\n## Summary\n\n### \n* Fixes Bug: User with no cluster privileges should not be able to\nenable the risk score\nWhen users with no cluster privileges open the risk score page, they\ndon't see any errors and are able to click the install button.\n\nThis happened because we were only checking for index privileges in the\nUI, but for the enablement flow we also need to check cluster\nprivileges. I also introduced a new parameter to the missing privileges\nhook so pages that only need to check for `read` privileges can work as\nbefore.\n\n\nhttps://github.com/user-attachments/assets/fe162005-ee2b-497d-8744-6262e4511d2d\n\n\n* Fixed Bug: The install button was enabled when all toggles were\ndisabled\nThere were too many booleans in the panel, which was confusing and led\nme to introduce more bugs while trying to fix this one, so I refactored\nthe code to understand it before fixing it.\nI also simplified the logic to display the modal. Now, it only shows\nwhen one of the engines' status is \"not_installed\"\n\n<img width=\"300\"\nsrc=\"https://github.com/user-attachments/assets/a2e8fbba-ac64-4c97-9ef0-ef6fe61e60cd\"\n/>\n\n\n\n\n\n\n\n### To Reproduce\n\n1. Create a user with security privileges and index privileges but no\ncluster privileges\n2. Go to the risk score page and enable the toggle\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or","sha":"b69b696e7fddf4bb26d038f1deaa6388051c428d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team: SecuritySolution","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[SecuritySolution] Fix Risk score Insufficient privileges warning missing cluster privileges","number":212405,"url":"https://github.com/elastic/kibana/pull/212405","mergeCommit":{"message":"[SecuritySolution] Fix Risk score Insufficient privileges warning missing cluster privileges (#212405)\n\n## Summary\n\n### \n* Fixes Bug: User with no cluster privileges should not be able to\nenable the risk score\nWhen users with no cluster privileges open the risk score page, they\ndon't see any errors and are able to click the install button.\n\nThis happened because we were only checking for index privileges in the\nUI, but for the enablement flow we also need to check cluster\nprivileges. I also introduced a new parameter to the missing privileges\nhook so pages that only need to check for `read` privileges can work as\nbefore.\n\n\nhttps://github.com/user-attachments/assets/fe162005-ee2b-497d-8744-6262e4511d2d\n\n\n* Fixed Bug: The install button was enabled when all toggles were\ndisabled\nThere were too many booleans in the panel, which was confusing and led\nme to introduce more bugs while trying to fix this one, so I refactored\nthe code to understand it before fixing it.\nI also simplified the logic to display the modal. Now, it only shows\nwhen one of the engines' status is \"not_installed\"\n\n<img width=\"300\"\nsrc=\"https://github.com/user-attachments/assets/a2e8fbba-ac64-4c97-9ef0-ef6fe61e60cd\"\n/>\n\n\n\n\n\n\n\n### To Reproduce\n\n1. Create a user with security privileges and index privileges but no\ncluster privileges\n2. Go to the risk score page and enable the toggle\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or","sha":"b69b696e7fddf4bb26d038f1deaa6388051c428d"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.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/212405","number":212405,"mergeCommit":{"message":"[SecuritySolution] Fix Risk score Insufficient privileges warning missing cluster privileges (#212405)\n\n## Summary\n\n### \n* Fixes Bug: User with no cluster privileges should not be able to\nenable the risk score\nWhen users with no cluster privileges open the risk score page, they\ndon't see any errors and are able to click the install button.\n\nThis happened because we were only checking for index privileges in the\nUI, but for the enablement flow we also need to check cluster\nprivileges. I also introduced a new parameter to the missing privileges\nhook so pages that only need to check for `read` privileges can work as\nbefore.\n\n\nhttps://github.com/user-attachments/assets/fe162005-ee2b-497d-8744-6262e4511d2d\n\n\n* Fixed Bug: The install button was enabled when all toggles were\ndisabled\nThere were too many booleans in the panel, which was confusing and led\nme to introduce more bugs while trying to fix this one, so I refactored\nthe code to understand it before fixing it.\nI also simplified the logic to display the modal. Now, it only shows\nwhen one of the engines' status is \"not_installed\"\n\n<img width=\"300\"\nsrc=\"https://github.com/user-attachments/assets/a2e8fbba-ac64-4c97-9ef0-ef6fe61e60cd\"\n/>\n\n\n\n\n\n\n\n### To Reproduce\n\n1. Create a user with security privileges and index privileges but no\ncluster privileges\n2. Go to the risk score page and enable the toggle\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or","sha":"b69b696e7fddf4bb26d038f1deaa6388051c428d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
|
Kibana Machine
|
1822ab2a4b
|
[9.0] [Security Solution] Flyout navigation in alert/events: update tooltip copy (#214264) (#214679)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Flyout navigation in alert/events: update tooltip copy (#214264)](https://github.com/elastic/kibana/pull/214264) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"christineweng","email":"18648970+christineweng@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T23:35:27Z","message":"[Security Solution] Flyout navigation in alert/events: update tooltip copy (#214264)\n\n## Summary\n\nUpdated tooltips per copy review\n |
||
|
Kibana Machine
|
418d9eaed2
|
[9.0] Update dependency elastic-apm-node to ^4.11.1 (main) (#214504) (#214674)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency elastic-apm-node to ^4.11.1 (main) (#214504)](https://github.com/elastic/kibana/pull/214504) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T23:26:57Z","message":"Update dependency elastic-apm-node to ^4.11.1 (main) (#214504)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[elastic-apm-node](https://redirect.github.com/elastic/apm-agent-nodejs)\n| dependencies | patch | [`^4.11.0` ->\n`^4.11.1`](https://renovatebot.com/diffs/npm/elastic-apm-node/4.11.0/4.11.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>elastic/apm-agent-nodejs (elastic-apm-node)</summary>\n\n###\n[`v4.11.1`](https://redirect.github.com/elastic/apm-agent-nodejs/releases/tag/v4.11.1)\n\n[Compare\nSource](https://redirect.github.com/elastic/apm-agent-nodejs/compare/v4.11.0...v4.11.1)\n\nFor more information, please see the\n[changelog](https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.11.1).\n\n##### Elastic APM Node.js agent layer ARNs\n\n|Region|ARN|\n|------|---|\n\n|af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"b3010930f92df55dc39aaee6fb310f32f51215de","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-minor","v9.1.0"],"title":"Update dependency elastic-apm-node to ^4.11.1 (main)","number":214504,"url":"https://github.com/elastic/kibana/pull/214504","mergeCommit":{"message":"Update dependency elastic-apm-node to ^4.11.1 (main) (#214504)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[elastic-apm-node](https://redirect.github.com/elastic/apm-agent-nodejs)\n| dependencies | patch | [`^4.11.0` ->\n`^4.11.1`](https://renovatebot.com/diffs/npm/elastic-apm-node/4.11.0/4.11.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>elastic/apm-agent-nodejs (elastic-apm-node)</summary>\n\n###\n[`v4.11.1`](https://redirect.github.com/elastic/apm-agent-nodejs/releases/tag/v4.11.1)\n\n[Compare\nSource](https://redirect.github.com/elastic/apm-agent-nodejs/compare/v4.11.0...v4.11.1)\n\nFor more information, please see the\n[changelog](https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.11.1).\n\n##### Elastic APM Node.js agent layer ARNs\n\n|Region|ARN|\n|------|---|\n\n|af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"b3010930f92df55dc39aaee6fb310f32f51215de"}},"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/214504","number":214504,"mergeCommit":{"message":"Update dependency elastic-apm-node to ^4.11.1 (main) (#214504)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n|\n[elastic-apm-node](https://redirect.github.com/elastic/apm-agent-nodejs)\n| dependencies | patch | [`^4.11.0` ->\n`^4.11.1`](https://renovatebot.com/diffs/npm/elastic-apm-node/4.11.0/4.11.1)\n|\n\n---\n\n### Release Notes\n\n<details>\n<summary>elastic/apm-agent-nodejs (elastic-apm-node)</summary>\n\n###\n[`v4.11.1`](https://redirect.github.com/elastic/apm-agent-nodejs/releases/tag/v4.11.1)\n\n[Compare\nSource](https://redirect.github.com/elastic/apm-agent-nodejs/compare/v4.11.0...v4.11.1)\n\nFor more information, please see the\n[changelog](https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-4.x.html#release-notes-4.11.1).\n\n##### Elastic APM Node.js agent layer ARNs\n\n|Region|ARN|\n|------|---|\n\n|af-south-1|arn:aws:lambda:af-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-east-1|arn:aws:lambda:ap-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-1|arn:aws:lambda:ap-northeast-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-2|arn:aws:lambda:ap-northeast-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-northeast-3|arn:aws:lambda:ap-northeast-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-south-1|arn:aws:lambda:ap-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-1|arn:aws:lambda:ap-southeast-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-2|arn:aws:lambda:ap-southeast-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ap-southeast-3|arn:aws:lambda:ap-southeast-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|ca-central-1|arn:aws:lambda:ca-central-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-central-1|arn:aws:lambda:eu-central-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-north-1|arn:aws:lambda:eu-north-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-south-1|arn:aws:lambda:eu-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-1|arn:aws:lambda:eu-west-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-2|arn:aws:lambda:eu-west-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|eu-west-3|arn:aws:lambda:eu-west-3:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|me-south-1|arn:aws:lambda:me-south-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|sa-east-1|arn:aws:lambda:sa-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-east-1|arn:aws:lambda:us-east-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-east-2|arn:aws:lambda:us-east-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-west-1|arn:aws:lambda:us-west-1:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n|us-west-2|arn:aws:lambda:us-west-2:267093732750:layer:elastic-apm-node-ver-4-11-1:1|\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"b3010930f92df55dc39aaee6fb310f32f51215de"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
56e0db9b29
|
[9.0] [Security solution] Destructure telemetryMetadata from subActionParams in order not to pass to OpenAI (#214640) (#214659)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)](https://github.com/elastic/kibana/pull/214640) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Steph Milovic","email":"stephanie.milovic@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T20:26:49Z","message":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)","sha":"36703da774e3a4dbcc6bd03cd66b9eade289a758","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: SecuritySolution","Team:Security Generative AI","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI","number":214640,"url":"https://github.com/elastic/kibana/pull/214640","mergeCommit":{"message":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)","sha":"36703da774e3a4dbcc6bd03cd66b9eade289a758"}},"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/214640","number":214640,"mergeCommit":{"message":"[Security solution] Destructure `telemetryMetadata` from `subActionParams` in order not to pass to OpenAI (#214640)","sha":"36703da774e3a4dbcc6bd03cd66b9eade289a758"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Steph Milovic <stephanie.milovic@elastic.co> |
||
elastic-renovate-prod[bot]
|
0eddfc7dcc
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 66d427a (9.0) (#214628)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `3f6bcf4` -> `66d427a` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
f61f65f88f
|
[9.0] [Synthetics] Unskip jest test (#214411) (#214646)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Unskip jest test (#214411)](https://github.com/elastic/kibana/pull/214411) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Justin Kambic","email":"jk@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T18:52:42Z","message":"[Synthetics] Unskip jest test (#214411)\n\n## Summary\n\nResolves #204152.\n\nUnskips a test.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d39d4fc5c58a193c3ed81ff6aed36f8c72b52316","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","Team:obs-ux-management","v9.1.0"],"title":"[Synthetics] Unskip jest test","number":214411,"url":"https://github.com/elastic/kibana/pull/214411","mergeCommit":{"message":"[Synthetics] Unskip jest test (#214411)\n\n## Summary\n\nResolves #204152.\n\nUnskips a test.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d39d4fc5c58a193c3ed81ff6aed36f8c72b52316"}},"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/214411","number":214411,"mergeCommit":{"message":"[Synthetics] Unskip jest test (#214411)\n\n## Summary\n\nResolves #204152.\n\nUnskips a test.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"d39d4fc5c58a193c3ed81ff6aed36f8c72b52316"}}]}] BACKPORT--> Co-authored-by: Justin Kambic <jk@elastic.co> |
||
|
Kibana Machine
|
a3ded6e9c8
|
[9.0] [Obs AI Assistant] Decrease log level to debug (#214598) (#214626)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Decrease log level to debug (#214598)](https://github.com/elastic/kibana/pull/214598) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T17:14:29Z","message":"[Obs AI Assistant] Decrease log level to debug (#214598)\n\nMinor logging change","sha":"5f04c35740823d10570dd4f0ccab262421a1ec21","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:Obs AI Assistant","v9.1.0"],"title":"[Obs AI Assistant] Decrease log level to debug","number":214598,"url":"https://github.com/elastic/kibana/pull/214598","mergeCommit":{"message":"[Obs AI Assistant] Decrease log level to debug (#214598)\n\nMinor logging change","sha":"5f04c35740823d10570dd4f0ccab262421a1ec21"}},"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/214598","number":214598,"mergeCommit":{"message":"[Obs AI Assistant] Decrease log level to debug (#214598)\n\nMinor logging change","sha":"5f04c35740823d10570dd4f0ccab262421a1ec21"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
Sergi Massaneda
|
adafa250f0
|
[9.0] [Security Solution] Siem migrations/copy changes rule translations (#214437) (#214623)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Siem migrations/copy changes rule translations (#214437)](https://github.com/elastic/kibana/pull/214437) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T16:15:09Z","message":"[Security Solution] Siem migrations/copy changes rule translations (#214437)\n\n## Summary\n\n3/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\nInstalled ML prebuilt rule\n\n\nKQL prebuilt rule\n\n\nCustom translated rule\n\n\nCustom partially translated rule\n\n\nCustom not translated rule\n\n\n#### Other\n\nInstalled badge updated\n\n\nStatus tooltip updated\n\n\nTour step 2 updated\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9e13b5594a628b79b711af6e2b05819c3f07b8a0","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":"[Security Solution] Siem migrations/copy changes rule translations","number":214437,"url":"https://github.com/elastic/kibana/pull/214437","mergeCommit":{"message":"[Security Solution] Siem migrations/copy changes rule translations (#214437)\n\n## Summary\n\n3/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\nInstalled ML prebuilt rule\n\n\nKQL prebuilt rule\n\n\nCustom translated rule\n\n\nCustom partially translated rule\n\n\nCustom not translated rule\n\n\n#### Other\n\nInstalled badge updated\n\n\nStatus tooltip updated\n\n\nTour step 2 updated\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9e13b5594a628b79b711af6e2b05819c3f07b8a0"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"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,"url":"https://github.com/elastic/kibana/pull/214607","number":214607,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214437","number":214437,"mergeCommit":{"message":"[Security Solution] Siem migrations/copy changes rule translations (#214437)\n\n## Summary\n\n3/3 of https://github.com/elastic/security-team/issues/11696\n\n**Done**\n- UI changes in the onboarding cards\n- UI changes in the upload form\n- UI changes in the translated rules page\n\n### Screenshots\n\nInstalled ML prebuilt rule\n\n\nKQL prebuilt rule\n\n\nCustom translated rule\n\n\nCustom partially translated rule\n\n\nCustom not translated rule\n\n\n#### Other\n\nInstalled badge updated\n\n\nStatus tooltip updated\n\n\nTour step 2 updated\n\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"9e13b5594a628b79b711af6e2b05819c3f07b8a0"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214609","number":214609,"state":"OPEN"}]}] BACKPORT--> |
||
Efe Gürkan YALAMAN
|
9440a3cf05
|
[9.0] [Search] [Synonyms] Synonym Rule flyout update (#213433) (#214414)
# Backport This will backport the following commits from `main` to `9.0`: - [[Search] [Synonyms] Synonym Rule flyout update (#213433)](https://github.com/elastic/kibana/pull/213433) <!--- 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-13T14:35:11Z","message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \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- [ ] [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: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Search","ci:project-deploy-elasticsearch","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[Search] [Synonyms] Synonym Rule flyout update","number":213433,"url":"https://github.com/elastic/kibana/pull/213433","mergeCommit":{"message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \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- [ ] [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: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213433","number":213433,"mergeCommit":{"message":"[Search] [Synonyms] Synonym Rule flyout update (#213433)\n\n## Summary\n\nUpdates Synonym Rule Flyout to match the designs. \n\n\nhttps://github.com/user-attachments/assets/8c034c2a-0b12-4a98-a627-fbef3a2542c7\n\nFlyout tries to handle invalid cases which would throw from the endpoint\ncall\n\n<img width=\"497\" alt=\"Screenshot 2025-03-07 at 17 11 51\"\nsrc=\"https://github.com/user-attachments/assets/6e610177-ec56-4420-bcee-4c72935cdbb9\"\n/>\n<img width=\"495\" alt=\"Screenshot 2025-03-07 at 17 12 07\"\nsrc=\"https://github.com/user-attachments/assets/3fed1ed1-4be4-449e-a30c-c8c13e7d7968\"\n/>\n<img width=\"509\" alt=\"Screenshot 2025-03-07 at 17 12 33\"\nsrc=\"https://github.com/user-attachments/assets/117dbac5-dfbe-4160-a9d4-a92bcb3bcf89\"\n/>\n<img width=\"472\" alt=\"Screenshot 2025-03-07 at 17 12 44\"\nsrc=\"https://github.com/user-attachments/assets/70d50693-b2bf-4af4-b363-65f92d6812fd\"\n/>\n<img width=\"484\" alt=\"Screenshot 2025-03-07 at 17 12 53\"\nsrc=\"https://github.com/user-attachments/assets/ebb8f401-4dd6-4180-9028-396680091a4c\"\n/>\n<img width=\"458\" alt=\"Screenshot 2025-03-07 at 17 13 27\"\nsrc=\"https://github.com/user-attachments/assets/a7c1244b-3334-44d3-bd4c-e26b463e1b68\"\n/>\n\nThe text added needs a quick check as well cc: @leemthompo \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- [ ] [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: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"c42d763ce48284c2cef855a99cf3008b8ccb96e3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214398","number":214398,"state":"OPEN"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/214397","number":214397,"state":"OPEN"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |