mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
82476 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
bac6d90d65
|
[8.18] [Obs AI Assistant] Add KB re-indexing when encountering semantic_text bug (#210386) (#211497)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Add KB re-indexing when encountering `semantic_text` bug (#210386)](https://github.com/elastic/kibana/pull/210386) <!--- Backport version: 9.6.5 --> ### 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-02-17T17:20:50Z","message":"[Obs AI Assistant] Add KB re-indexing when encountering `semantic_text` bug (#210386)\n\nCloses https://github.com/elastic/kibana/issues/210204\n\nThis will automatically re-index the knowledge base if upon adding a KB\nentry there is this error:\n\n> The [sparse_vector] field type is not supported on indices created on\nversions 8.0 to 8.10\n\nThat error means that semantic_text is not supported in the given index,\nand it should therefore be re-indexed.\n\n**How to test this PR:**\n\n**8.10**\n- `git checkout -B 8.10 origin/8.10`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n\n**8.19**\n- `git checkout -B 8.19 origin/8.x`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n- Install Knowledge base\n- Try adding an item to KB (it should fail ❌️)\n\n**9.1.0**\n- `gh pr checkout 210386`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n- Try adding an item to KB (it should succeed ✅️)\n\n**TODO:**\n\n- Add an upgrade test that covers this flow\n\n---------\n\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"df67a09afab22521dfa9ff3ec3a4f624a039c462","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-major","Team:Obs AI Assistant","v9.1.0"],"title":"[Obs AI Assistant] Add KB re-indexing when encountering `semantic_text` bug","number":210386,"url":"https://github.com/elastic/kibana/pull/210386","mergeCommit":{"message":"[Obs AI Assistant] Add KB re-indexing when encountering `semantic_text` bug (#210386)\n\nCloses https://github.com/elastic/kibana/issues/210204\n\nThis will automatically re-index the knowledge base if upon adding a KB\nentry there is this error:\n\n> The [sparse_vector] field type is not supported on indices created on\nversions 8.0 to 8.10\n\nThat error means that semantic_text is not supported in the given index,\nand it should therefore be re-indexed.\n\n**How to test this PR:**\n\n**8.10**\n- `git checkout -B 8.10 origin/8.10`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n\n**8.19**\n- `git checkout -B 8.19 origin/8.x`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n- Install Knowledge base\n- Try adding an item to KB (it should fail ❌️)\n\n**9.1.0**\n- `gh pr checkout 210386`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n- Try adding an item to KB (it should succeed ✅️)\n\n**TODO:**\n\n- Add an upgrade test that covers this flow\n\n---------\n\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"df67a09afab22521dfa9ff3ec3a4f624a039c462"}},"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/210386","number":210386,"mergeCommit":{"message":"[Obs AI Assistant] Add KB re-indexing when encountering `semantic_text` bug (#210386)\n\nCloses https://github.com/elastic/kibana/issues/210204\n\nThis will automatically re-index the knowledge base if upon adding a KB\nentry there is this error:\n\n> The [sparse_vector] field type is not supported on indices created on\nversions 8.0 to 8.10\n\nThat error means that semantic_text is not supported in the given index,\nand it should therefore be re-indexed.\n\n**How to test this PR:**\n\n**8.10**\n- `git checkout -B 8.10 origin/8.10`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n\n**8.19**\n- `git checkout -B 8.19 origin/8.x`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n- Install Knowledge base\n- Try adding an item to KB (it should fail ❌️)\n\n**9.1.0**\n- `gh pr checkout 210386`\n- Start Kibana:\n - `nvm use && yarn kbn bootstrap && yarn start`\n- Start ES\n- `nvm use && yarn es snapshot --license trial --E\npath.data=\"/Users/sorenlouv/elastic/kbn_es_data/upgrade_testing\"`\n- Try adding an item to KB (it should succeed ✅️)\n\n**TODO:**\n\n- Add an upgrade test that covers this flow\n\n---------\n\nCo-authored-by: Viduni Wickramarachchi <viduni.ushanka@gmail.com>","sha":"df67a09afab22521dfa9ff3ec3a4f624a039c462"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
|
Kibana Machine
|
b408e8c585
|
[8.18] [ML] File upload: Adding link to full file upload tool (#211443) (#211491)
# Backport This will backport the following commits from `main` to `8.18`: - [[ML] File upload: Adding link to full file upload tool (#211443)](https://github.com/elastic/kibana/pull/211443) <!--- Backport version: 9.6.5 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"James Gowdy","email":"jgowdy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-17T16:38:05Z","message":"[ML] File upload: Adding link to full file upload tool (#211443)\n\nAdds a link to the original file upload page from file upload lite help\r\ntext.\r\n\r\n\r\n","sha":"24dbf7ecfd6e5aaa9e34e514f2afd801ef566808","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["non-issue",":ml","release_note:skip","Feature:File and Index Data Viz","Feature:File Upload","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ML] File upload: Adding link to full file upload tool","number":211443,"url":"https://github.com/elastic/kibana/pull/211443","mergeCommit":{"message":"[ML] File upload: Adding link to full file upload tool (#211443)\n\nAdds a link to the original file upload page from file upload lite help\r\ntext.\r\n\r\n\r\n","sha":"24dbf7ecfd6e5aaa9e34e514f2afd801ef566808"}},"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/211443","number":211443,"mergeCommit":{"message":"[ML] File upload: Adding link to full file upload tool (#211443)\n\nAdds a link to the original file upload page from file upload lite help\r\ntext.\r\n\r\n\r\n","sha":"24dbf7ecfd6e5aaa9e34e514f2afd801ef566808"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: James Gowdy <jgowdy@elastic.co> |
||
|
Kibana Machine
|
035b784bd7
|
[8.18] Bump backport to v9.6.6 (#211424) (#211482)
# Backport This will backport the following commits from `main` to `8.18`: - [Bump backport to v9.6.6 (#211424)](https://github.com/elastic/kibana/pull/211424) <!--- Backport version: 9.6.5 --> ### 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-02-17T16:08:53Z","message":"Bump backport to v9.6.6 (#211424)\n\nThis bumps backport to 9.6.6. Most notably fixes an issue with\nHandlebars templates and stripping markdown comments:\nhttps://github.com/sorenlouv/backport/compare/v9.6.4...v9.6.6\n\nAlso bumped here:\nhttps://github.com/elastic/kibana-github-actions/pull/55","sha":"a91e4fcd088dcdf93775bc9d9d9d77e3eec8ea59","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v9.1.0"],"title":"Bump backport to v9.6.6","number":211424,"url":"https://github.com/elastic/kibana/pull/211424","mergeCommit":{"message":"Bump backport to v9.6.6 (#211424)\n\nThis bumps backport to 9.6.6. Most notably fixes an issue with\nHandlebars templates and stripping markdown comments:\nhttps://github.com/sorenlouv/backport/compare/v9.6.4...v9.6.6\n\nAlso bumped here:\nhttps://github.com/elastic/kibana-github-actions/pull/55","sha":"a91e4fcd088dcdf93775bc9d9d9d77e3eec8ea59"}},"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/211424","number":211424,"mergeCommit":{"message":"Bump backport to v9.6.6 (#211424)\n\nThis bumps backport to 9.6.6. Most notably fixes an issue with\nHandlebars templates and stripping markdown comments:\nhttps://github.com/sorenlouv/backport/compare/v9.6.4...v9.6.6\n\nAlso bumped here:\nhttps://github.com/elastic/kibana-github-actions/pull/55","sha":"a91e4fcd088dcdf93775bc9d9d9d77e3eec8ea59"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
|
Kibana Machine
|
1a6691c6f2
|
[8.18] Delete 'ServiceEntityStoreEnabled' Flag usages (#211066) (#211454)
# Backport This will backport the following commits from `main` to `8.18`: - [Delete 'ServiceEntityStoreEnabled' Flag usages (#211066)](https://github.com/elastic/kibana/pull/211066) <!--- Backport version: 9.6.5 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Charlotte Alexandra Wilson","email":"CAWilson94@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-17T14:19:09Z","message":"Delete 'ServiceEntityStoreEnabled' Flag usages (#211066)\n\n## Summary\r\n\r\nThis PR deletes all usages of ServiceEntityStoreEnabled feature flag.\r\nThe feature flag itself has been left in `experimental_features.ts`\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"745784f32a528705c04343f3c8a619b3caf939f2","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","ci:project-deploy-security","ci:project-persist-deployment","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Delete 'ServiceEntityStoreEnabled' Flag usages","number":211066,"url":"https://github.com/elastic/kibana/pull/211066","mergeCommit":{"message":"Delete 'ServiceEntityStoreEnabled' Flag usages (#211066)\n\n## Summary\r\n\r\nThis PR deletes all usages of ServiceEntityStoreEnabled feature flag.\r\nThe feature flag itself has been left in `experimental_features.ts`\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"745784f32a528705c04343f3c8a619b3caf939f2"}},"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/211066","number":211066,"mergeCommit":{"message":"Delete 'ServiceEntityStoreEnabled' Flag usages (#211066)\n\n## Summary\r\n\r\nThis PR deletes all usages of ServiceEntityStoreEnabled feature flag.\r\nThe feature flag itself has been left in `experimental_features.ts`\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"745784f32a528705c04343f3c8a619b3caf939f2"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Charlotte Alexandra Wilson <CAWilson94@users.noreply.github.com> |
||
Bharat Pasupula
|
158cfac027
|
[8.18] [Automatic Import] Remove pipeline tests from the package (#211223) (#211398)
# Backport This will backport the following commits from `main` to `8.18`: - [[Automatic Import] Remove pipeline tests from the package (#211223)](https://github.com/elastic/kibana/pull/211223) <!--- Backport version: 9.6.4 --> ### 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-02-17T09:28:57Z","message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff","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","ci:build-cloud-image","ci:cloud-deploy","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Remove pipeline tests from the package","number":211223,"url":"https://github.com/elastic/kibana/pull/211223","mergeCommit":{"message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff"}},"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/211223","number":211223,"mergeCommit":{"message":"[Automatic Import] Remove pipeline tests from the package (#211223)\n\n## Summary\r\n\r\nThis PR removes unused pipeline tests from the packaging of integration.\r\n\r\nThe pipeline tests are not run today when the integration is built.\r\nHence removing them for now.","sha":"54b6e65a2047cdcc727032e1734170e7c8307aff"}}]}] BACKPORT--> |
||
|
Kibana Machine
|
e951cf2aab
|
[8.18] [Rules migration][Integration test] Get Prebuilt Rules APIs (#11232) (#211403) (#211426)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rules migration][Integration test] Get Prebuilt Rules APIs (#11232) (#211403)](https://github.com/elastic/kibana/pull/211403) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-17T12:31:30Z","message":"[Rules migration][Integration test] Get Prebuilt Rules APIs (#11232) (#211403)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Get prebuilt rules API (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/prebuilt_rules`)\r\nintegration test:\r\n* get all prebuilt rules matched by migration rules\r\n* return empty response when migration rules did not match prebuilt\r\nrules","sha":"0adce7a3dbdfc8d6a6bbdff3765da1d05e12c0fb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rules migration][Integration test] Get Prebuilt Rules APIs (#11232)","number":211403,"url":"https://github.com/elastic/kibana/pull/211403","mergeCommit":{"message":"[Rules migration][Integration test] Get Prebuilt Rules APIs (#11232) (#211403)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Get prebuilt rules API (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/prebuilt_rules`)\r\nintegration test:\r\n* get all prebuilt rules matched by migration rules\r\n* return empty response when migration rules did not match prebuilt\r\nrules","sha":"0adce7a3dbdfc8d6a6bbdff3765da1d05e12c0fb"}},"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/211403","number":211403,"mergeCommit":{"message":"[Rules migration][Integration test] Get Prebuilt Rules APIs (#11232) (#211403)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Get prebuilt rules API (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/prebuilt_rules`)\r\nintegration test:\r\n* get all prebuilt rules matched by migration rules\r\n* return empty response when migration rules did not match prebuilt\r\nrules","sha":"0adce7a3dbdfc8d6a6bbdff3765da1d05e12c0fb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
b42affdbfb
|
[8.18] [Rules migration][Integration test] Install APIs (#11232) (#211339) (#211401)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rules migration][Integration test] Install APIs (#11232) (#211339)](https://github.com/elastic/kibana/pull/211339) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-17T10:25:33Z","message":"[Rules migration][Integration test] Install APIs (#11232) (#211339)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Install API (route: `POST\r\n/internal/siem_migrations/rules/{migration_id}/install`) integration\r\ntest:\r\n* install all installable custom migration rules\r\n* install all installable migration rules matched with prebuilt rules\r\n* install and enable all installable migration rules\r\n* install migration rules by ids\r\n* install rules of non-existing migration - nothing should be installed\r\n* Error handling: an error if body payload is not passed","sha":"cd502acea12979979497f62897be663044ade3aa","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rules migration][Integration test] Install APIs (#11232)","number":211339,"url":"https://github.com/elastic/kibana/pull/211339","mergeCommit":{"message":"[Rules migration][Integration test] Install APIs (#11232) (#211339)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Install API (route: `POST\r\n/internal/siem_migrations/rules/{migration_id}/install`) integration\r\ntest:\r\n* install all installable custom migration rules\r\n* install all installable migration rules matched with prebuilt rules\r\n* install and enable all installable migration rules\r\n* install migration rules by ids\r\n* install rules of non-existing migration - nothing should be installed\r\n* Error handling: an error if body payload is not passed","sha":"cd502acea12979979497f62897be663044ade3aa"}},"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/211339","number":211339,"mergeCommit":{"message":"[Rules migration][Integration test] Install APIs (#11232) (#211339)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Install API (route: `POST\r\n/internal/siem_migrations/rules/{migration_id}/install`) integration\r\ntest:\r\n* install all installable custom migration rules\r\n* install all installable migration rules matched with prebuilt rules\r\n* install and enable all installable migration rules\r\n* install migration rules by ids\r\n* install rules of non-existing migration - nothing should be installed\r\n* Error handling: an error if body payload is not passed","sha":"cd502acea12979979497f62897be663044ade3aa"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
elastic-vault-github-plugin-prod[bot]
|
2c7a285eb6
|
[8.18] Sync bundled packages with Package Storage (#211270)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2284 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Angela Chuang
|
34e29d9d85
|
[8.18][SecuritySolution] Hover actions not working on the overview section of the host details page (#211207)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution]Hover actions not working on the overview section of the host details page (#210819)](https://github.com/elastic/kibana/pull/210819) --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
af7d98e7fd
|
[8.18] [Security Solution][Entity Analytics][Risk Score]Changes for the confirmation message after RiskScore SO is updated (#211372) (#211390)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Entity Analytics][Risk Score]Changes for the confirmation message after RiskScore SO is updated (#211372)](https://github.com/elastic/kibana/pull/211372) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-17T10:01:39Z","message":"[Security Solution][Entity Analytics][Risk Score]Changes for the confirmation message after RiskScore SO is updated (#211372)\n\n## Summary\n\n### **What has changed?** \nThis PR updates the text in the `toast` message when the Risk Score\nSaved Object configuration is modified by the user.\n\n### **Reason for the change:** \nThe update ensures compliance with the toast message guidelines: [EUI\nToast Guidelines](https://eui.elastic.co/#/display/toast/guidelines).\n\n### **Screenshots:**\n\n**Before:**\n\n\n\n\n\n**Now:**\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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":"24b75740fd08f0a3c3ba36f3fa67782e1c2b7c1a","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","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution][Entity Analytics][Risk Score]Changes for the confirmation message after RiskScore SO is updated","number":211372,"url":"https://github.com/elastic/kibana/pull/211372","mergeCommit":{"message":"[Security Solution][Entity Analytics][Risk Score]Changes for the confirmation message after RiskScore SO is updated (#211372)\n\n## Summary\n\n### **What has changed?** \nThis PR updates the text in the `toast` message when the Risk Score\nSaved Object configuration is modified by the user.\n\n### **Reason for the change:** \nThe update ensures compliance with the toast message guidelines: [EUI\nToast Guidelines](https://eui.elastic.co/#/display/toast/guidelines).\n\n### **Screenshots:**\n\n**Before:**\n\n\n\n\n\n**Now:**\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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":"24b75740fd08f0a3c3ba36f3fa67782e1c2b7c1a"}},"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/211372","number":211372,"mergeCommit":{"message":"[Security Solution][Entity Analytics][Risk Score]Changes for the confirmation message after RiskScore SO is updated (#211372)\n\n## Summary\n\n### **What has changed?** \nThis PR updates the text in the `toast` message when the Risk Score\nSaved Object configuration is modified by the user.\n\n### **Reason for the change:** \nThe update ensures compliance with the toast message guidelines: [EUI\nToast Guidelines](https://eui.elastic.co/#/display/toast/guidelines).\n\n### **Screenshots:**\n\n**Before:**\n\n\n\n\n\n**Now:**\n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] 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":"24b75740fd08f0a3c3ba36f3fa67782e1c2b7c1a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com> |
||
Gerard Soldevila
|
8b1f5f1a28
|
[8.18] [UA] Implement read-only and unfreeze flows for indices (#210199) (#211361)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[UA] Implement read-only and unfreeze flows for indices (#210199)](https://github.com/elastic/kibana/pull/210199) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T16:09:38Z","message":"[UA] Implement read-only and unfreeze flows for indices (#210199)\n\n## Summary\r\n\r\nAddress https://github.com/elastic/kibana-team/issues/1418,\r\nhttps://github.com/elastic/kibana/issues/205945\r\n\r\n* Implement the \"make readonly\" flow for _old index_ deprecations.\r\n* Implement the \"unfreeze\" flow for _old indices_ that are frozen and\r\n`verified_read_only: true` (making them read-only is no longer an option\r\nfor those).\r\n* Refactor the code so that the \"reindex\" flyout steps are generalised\r\nto support the new flows.\r\n* Rename vars with misleading names (see\r\nhttps://github.com/elastic/kibana/pull/209522).\r\n\r\n---------\r\n\r\nCo-authored-by: Rudolf Meijering <skaapgif@gmail.com>","sha":"3768c353b4ba0420e7d4e55100312d88b727cb3c","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:version","v8.18.0"],"title":"[UA] Implement read-only and unfreeze flows for indices","number":210199,"url":"https://github.com/elastic/kibana/pull/210199","mergeCommit":{"message":"[UA] Implement read-only and unfreeze flows for indices (#210199)\n\n## Summary\r\n\r\nAddress https://github.com/elastic/kibana-team/issues/1418,\r\nhttps://github.com/elastic/kibana/issues/205945\r\n\r\n* Implement the \"make readonly\" flow for _old index_ deprecations.\r\n* Implement the \"unfreeze\" flow for _old indices_ that are frozen and\r\n`verified_read_only: true` (making them read-only is no longer an option\r\nfor those).\r\n* Refactor the code so that the \"reindex\" flyout steps are generalised\r\nto support the new flows.\r\n* Rename vars with misleading names (see\r\nhttps://github.com/elastic/kibana/pull/209522).\r\n\r\n---------\r\n\r\nCo-authored-by: Rudolf Meijering <skaapgif@gmail.com>","sha":"3768c353b4ba0420e7d4e55100312d88b727cb3c"}},"sourceBranch":"8.x","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"}]}] BACKPORT--> |
||
|
Kibana Machine
|
f11680d3ce
|
[8.18] Pass system message to inferenceCliente.chatComplete (#211263) (#211358)
# Backport This will backport the following commits from `main` to `8.18`: - [Pass system message to inferenceCliente.chatComplete (#211263)](https://github.com/elastic/kibana/pull/211263) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-02-16T08:43:50Z","message":"Pass system message to inferenceCliente.chatComplete (#211263)\n\nCloses #211257 \r\n\r\n## Summary\r\n\r\nRegression introduced in 8.18\r\n(https://github.com/elastic/kibana/pull/199286)\r\n\r\nWe no longer pass the `system` message to the inference plugin, and\r\nthereby the LLM. This means that we are only passing user messages to\r\nthe LLM. The system message is important in steering the conversation,\r\nand providing guardrails to the LLM.","sha":"117802cbb2ba73df14f82a2ee1caee1bfe5b1ced","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 AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Pass system message to inferenceCliente.chatComplete","number":211263,"url":"https://github.com/elastic/kibana/pull/211263","mergeCommit":{"message":"Pass system message to inferenceCliente.chatComplete (#211263)\n\nCloses #211257 \r\n\r\n## Summary\r\n\r\nRegression introduced in 8.18\r\n(https://github.com/elastic/kibana/pull/199286)\r\n\r\nWe no longer pass the `system` message to the inference plugin, and\r\nthereby the LLM. This means that we are only passing user messages to\r\nthe LLM. The system message is important in steering the conversation,\r\nand providing guardrails to the LLM.","sha":"117802cbb2ba73df14f82a2ee1caee1bfe5b1ced"}},"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/211263","number":211263,"mergeCommit":{"message":"Pass system message to inferenceCliente.chatComplete (#211263)\n\nCloses #211257 \r\n\r\n## Summary\r\n\r\nRegression introduced in 8.18\r\n(https://github.com/elastic/kibana/pull/199286)\r\n\r\nWe no longer pass the `system` message to the inference plugin, and\r\nthereby the LLM. This means that we are only passing user messages to\r\nthe LLM. The system message is important in steering the conversation,\r\nand providing guardrails to the LLM.","sha":"117802cbb2ba73df14f82a2ee1caee1bfe5b1ced"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
Felix Stürmer
|
245ef3653f
|
[8.18] [Logs UI] Allow editing of non-resolving log views (#210633) (#211236)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[Logs UI] Allow editing of non-resolving log views (#210633)](https://github.com/elastic/kibana/pull/210633) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Felix Stürmer","email":"weltenwort@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T14:55:17Z","message":"[Logs UI] Allow editing of non-resolving log views (#210633)\n\nThis changes the settings page of the Logs UI such that it allows editing of log view settings even if the resolution or status check failed. This allows recovery from various situations that were previously only recoverable by resetting the log view completely.","sha":"41cd657811bd1c00ac15860268c018d4d80085ac","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Feature:Logs UI","backport:skip","Team:obs-ux-logs","v8.18.0","v8.17.3"],"title":"[Logs UI] Allow editing of non-resolving log views","number":210633,"url":"https://github.com/elastic/kibana/pull/210633","mergeCommit":{"message":"[Logs UI] Allow editing of non-resolving log views (#210633)\n\nThis changes the settings page of the Logs UI such that it allows editing of log view settings even if the resolution or status check failed. This allows recovery from various situations that were previously only recoverable by resetting the log view completely.","sha":"41cd657811bd1c00ac15860268c018d4d80085ac"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18","8.17"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
44ebe22671
|
[8.18] [Rules migration][Integration test] Stats APIs (#11232) (#211315) (#211336)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rules migration][Integration test] Stats APIs (#11232) (#211315)](https://github.com/elastic/kibana/pull/211315) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T23:30:43Z","message":"[Rules migration][Integration test] Stats APIs (#11232) (#211315)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Stats APIs:\r\n* Retrieves the stats for the specific migration: (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/stat`)\r\n* Retrieves the stats for all the existing migrations, aggregated by\r\n`migration_id`: (route: `GET /internal/siem_migrations/rules/stats`)\r\n* Retrieves the translation stats for the migration: (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/translation_stats`)","sha":"6006546dc4abd005eb05a587b28bbef2a2b39bc7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rules migration][Integration test] Stats APIs (#11232)","number":211315,"url":"https://github.com/elastic/kibana/pull/211315","mergeCommit":{"message":"[Rules migration][Integration test] Stats APIs (#11232) (#211315)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Stats APIs:\r\n* Retrieves the stats for the specific migration: (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/stat`)\r\n* Retrieves the stats for all the existing migrations, aggregated by\r\n`migration_id`: (route: `GET /internal/siem_migrations/rules/stats`)\r\n* Retrieves the translation stats for the migration: (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/translation_stats`)","sha":"6006546dc4abd005eb05a587b28bbef2a2b39bc7"}},"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/211315","number":211315,"mergeCommit":{"message":"[Rules migration][Integration test] Stats APIs (#11232) (#211315)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Stats APIs:\r\n* Retrieves the stats for the specific migration: (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/stat`)\r\n* Retrieves the stats for all the existing migrations, aggregated by\r\n`migration_id`: (route: `GET /internal/siem_migrations/rules/stats`)\r\n* Retrieves the translation stats for the migration: (route: `GET\r\n/internal/siem_migrations/rules/{migration_id}/translation_stats`)","sha":"6006546dc4abd005eb05a587b28bbef2a2b39bc7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
580a382918
|
[8.18] Update Logs Explorer deprecation messages (#201307) (#210682)
# Backport This will backport the following commits from `main` to `8.18`: - [Update Logs Explorer deprecation messages (#201307)](https://github.com/elastic/kibana/pull/201307) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-02-11T18:26:33Z","message":"Update Logs Explorer deprecation messages (#201307)\n\n## Summary\r\n\r\nIt was pointed out in\r\nhttps://github.com/elastic/kibana/pull/199255#discussion_r1842800664\r\nthat the Logs Explorer deprecation messages may no longer be accurate\r\nnow that contextual logs features are only available in Discover in the\r\nObservability solution view for 8.x:\r\n\r\n\r\n\r\nI'm not really sure what they should updated to instead, so hopefully\r\n@elastic/obs-ux-logs-team can offer some suggestions.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"056eba293728e2f67413a70f5021dff344054126","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:DataDiscovery","ci:project-deploy-observability","Team:obs-ux-logs","Project:OneDiscover","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"Update Logs Explorer deprecation messages","number":201307,"url":"https://github.com/elastic/kibana/pull/201307","mergeCommit":{"message":"Update Logs Explorer deprecation messages (#201307)\n\n## Summary\r\n\r\nIt was pointed out in\r\nhttps://github.com/elastic/kibana/pull/199255#discussion_r1842800664\r\nthat the Logs Explorer deprecation messages may no longer be accurate\r\nnow that contextual logs features are only available in Discover in the\r\nObservability solution view for 8.x:\r\n\r\n\r\n\r\nI'm not really sure what they should updated to instead, so hopefully\r\n@elastic/obs-ux-logs-team can offer some suggestions.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"056eba293728e2f67413a70f5021dff344054126"}},"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/201307","number":201307,"mergeCommit":{"message":"Update Logs Explorer deprecation messages (#201307)\n\n## Summary\r\n\r\nIt was pointed out in\r\nhttps://github.com/elastic/kibana/pull/199255#discussion_r1842800664\r\nthat the Logs Explorer deprecation messages may no longer be accurate\r\nnow that contextual logs features are only available in Discover in the\r\nObservability solution view for 8.x:\r\n\r\n\r\n\r\nI'm not really sure what they should updated to instead, so hopefully\r\n@elastic/obs-ux-logs-team can offer some suggestions.\r\n\r\n### Checklist\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"056eba293728e2f67413a70f5021dff344054126"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Davis McPhee <davis.mcphee@elastic.co> |
||
|
Kibana Machine
|
23610bc3f9
|
[8.18] [Security Solution][Detection Engine] fixes lists/items API when @timestamp field is number (#210440) (#211321)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Detection Engine] fixes lists/items API when @timestamp field is number (#210440)](https://github.com/elastic/kibana/pull/210440) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Vitalii Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T20:09:53Z","message":"[Security Solution][Detection Engine] fixes lists/items API when @timestamp field is number (#210440)\n\n## Summary\r\n\r\n- addresses https://github.com/elastic/security-team/issues/11831\r\n\r\n**To Reproduce**\r\n\r\n1. Create Security lists/items in 7.17 by uploading value list\r\nhttps://www.elastic.co/guide/en/security/current/value-lists-exceptions.html\r\n2. Upgrade to 8.18\r\n3. Visit detection engine page to ensure .lists-{SPACE} and\r\n.items-{SPACE} data streams have been created. Would be enough to lookup\r\nvalue lists in lists UI\r\nhttps://www.elastic.co/guide/en/security/current/value-lists-exceptions.html#edit-value-lists\r\n4. Go to Kibana Upgrade assistant\r\n5. Reindex .lists-{SPACE} and .items-{SPACE} data streams\r\n6. After reindex lists are not retrievable with error\r\n`\"data.0.@timestamp: Expected string, received number\"\r\n` through `/lists/_find` API\r\n\r\n**After fix**\r\n\r\n`@timestamp` of number type will be converted to ISO string\r\n\r\n**To test**\r\n\r\nuse 8.18 mirror of this branch:\r\nhttps://github.com/elastic/kibana/pull/210439\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"fc5adc02fea15d9095e2c6f7dd68c538f36bf24b","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 Engine","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution][Detection Engine] fixes lists/items API when @timestamp field is number","number":210440,"url":"https://github.com/elastic/kibana/pull/210440","mergeCommit":{"message":"[Security Solution][Detection Engine] fixes lists/items API when @timestamp field is number (#210440)\n\n## Summary\r\n\r\n- addresses https://github.com/elastic/security-team/issues/11831\r\n\r\n**To Reproduce**\r\n\r\n1. Create Security lists/items in 7.17 by uploading value list\r\nhttps://www.elastic.co/guide/en/security/current/value-lists-exceptions.html\r\n2. Upgrade to 8.18\r\n3. Visit detection engine page to ensure .lists-{SPACE} and\r\n.items-{SPACE} data streams have been created. Would be enough to lookup\r\nvalue lists in lists UI\r\nhttps://www.elastic.co/guide/en/security/current/value-lists-exceptions.html#edit-value-lists\r\n4. Go to Kibana Upgrade assistant\r\n5. Reindex .lists-{SPACE} and .items-{SPACE} data streams\r\n6. After reindex lists are not retrievable with error\r\n`\"data.0.@timestamp: Expected string, received number\"\r\n` through `/lists/_find` API\r\n\r\n**After fix**\r\n\r\n`@timestamp` of number type will be converted to ISO string\r\n\r\n**To test**\r\n\r\nuse 8.18 mirror of this branch:\r\nhttps://github.com/elastic/kibana/pull/210439\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"fc5adc02fea15d9095e2c6f7dd68c538f36bf24b"}},"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/210440","number":210440,"mergeCommit":{"message":"[Security Solution][Detection Engine] fixes lists/items API when @timestamp field is number (#210440)\n\n## Summary\r\n\r\n- addresses https://github.com/elastic/security-team/issues/11831\r\n\r\n**To Reproduce**\r\n\r\n1. Create Security lists/items in 7.17 by uploading value list\r\nhttps://www.elastic.co/guide/en/security/current/value-lists-exceptions.html\r\n2. Upgrade to 8.18\r\n3. Visit detection engine page to ensure .lists-{SPACE} and\r\n.items-{SPACE} data streams have been created. Would be enough to lookup\r\nvalue lists in lists UI\r\nhttps://www.elastic.co/guide/en/security/current/value-lists-exceptions.html#edit-value-lists\r\n4. Go to Kibana Upgrade assistant\r\n5. Reindex .lists-{SPACE} and .items-{SPACE} data streams\r\n6. After reindex lists are not retrievable with error\r\n`\"data.0.@timestamp: Expected string, received number\"\r\n` through `/lists/_find` API\r\n\r\n**After fix**\r\n\r\n`@timestamp` of number type will be converted to ISO string\r\n\r\n**To test**\r\n\r\nuse 8.18 mirror of this branch:\r\nhttps://github.com/elastic/kibana/pull/210439\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"fc5adc02fea15d9095e2c6f7dd68c538f36bf24b"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com> |
||
Viduni Wickramarachchi
|
d5d3274e55
|
[8.18] [Obs AI Assistant] Fix connector test in MKI (#211235) (#211303)
# Backport This will backport the following commits from `main` to `8.18`: - [[Obs AI Assistant] Fix connector test in MKI (#211235)](https://github.com/elastic/kibana/pull/211235) <!--- Backport version: 9.6.4 --> ### 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-02-14T16:35:42Z","message":"[Obs AI Assistant] Fix connector test in MKI (#211235)\n\nCloses https://github.com/elastic/kibana/issues/211175\n\n## Problem\n\nThe connectors test is failing Serverless because we now have a\npre-configured inference connector\n\n## Solution\n\nFilter out the pre-configured inference connector in tests\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":"c1d055973877bc66eec5e2cbf6b3b1a53396fdf5","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 AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Fix connector test in MKI","number":211235,"url":"https://github.com/elastic/kibana/pull/211235","mergeCommit":{"message":"[Obs AI Assistant] Fix connector test in MKI (#211235)\n\nCloses https://github.com/elastic/kibana/issues/211175\n\n## Problem\n\nThe connectors test is failing Serverless because we now have a\npre-configured inference connector\n\n## Solution\n\nFilter out the pre-configured inference connector in tests\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":"c1d055973877bc66eec5e2cbf6b3b1a53396fdf5"}},"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/211235","number":211235,"mergeCommit":{"message":"[Obs AI Assistant] Fix connector test in MKI (#211235)\n\nCloses https://github.com/elastic/kibana/issues/211175\n\n## Problem\n\nThe connectors test is failing Serverless because we now have a\npre-configured inference connector\n\n## Solution\n\nFilter out the pre-configured inference connector in tests\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":"c1d055973877bc66eec5e2cbf6b3b1a53396fdf5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
2f2c275eda
|
[8.18] [Rules migration][Integration test] Update migration API (#11232) (#211196) (#211296)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rules migration][Integration test] Update migration API (#11232) (#211196)](https://github.com/elastic/kibana/pull/211196) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:39:21Z","message":"[Rules migration][Integration test] Update migration API (#11232) (#211196)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Update API (route: `PUT\r\n/internal/siem_migrations/rules/{migration_id}`) integration test:\r\n* Happy path\r\n * update migration\r\n * ignore attributes that are not eligible for update\r\n* Error handling\r\n * an empty content response\r\n * an error when rule's id is not specified\r\n * an error when undefined payload has been passed\r\n\r\nAlso, as part of this PR, I added error handling cases for Create API:\r\n* no content error\r\n* an error when undefined payload has been passed\r\n* an error when original rule id is not specified\r\n* error when original rule vendor is not specified\r\n* an error when original rule title is not specified\r\n* an error when original rule description is not specified\r\n* an error when original rule query is not specified\r\n* an error when original rule query_language is not specified\r\n\r\n---------\r\n\r\nCo-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>","sha":"819fd7a3e9f0e885bc22f382dcc165ea1a4b55e7","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rules migration][Integration test] Update migration API (#11232)","number":211196,"url":"https://github.com/elastic/kibana/pull/211196","mergeCommit":{"message":"[Rules migration][Integration test] Update migration API (#11232) (#211196)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Update API (route: `PUT\r\n/internal/siem_migrations/rules/{migration_id}`) integration test:\r\n* Happy path\r\n * update migration\r\n * ignore attributes that are not eligible for update\r\n* Error handling\r\n * an empty content response\r\n * an error when rule's id is not specified\r\n * an error when undefined payload has been passed\r\n\r\nAlso, as part of this PR, I added error handling cases for Create API:\r\n* no content error\r\n* an error when undefined payload has been passed\r\n* an error when original rule id is not specified\r\n* error when original rule vendor is not specified\r\n* an error when original rule title is not specified\r\n* an error when original rule description is not specified\r\n* an error when original rule query is not specified\r\n* an error when original rule query_language is not specified\r\n\r\n---------\r\n\r\nCo-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>","sha":"819fd7a3e9f0e885bc22f382dcc165ea1a4b55e7"}},"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/211196","number":211196,"mergeCommit":{"message":"[Rules migration][Integration test] Update migration API (#11232) (#211196)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations Update API (route: `PUT\r\n/internal/siem_migrations/rules/{migration_id}`) integration test:\r\n* Happy path\r\n * update migration\r\n * ignore attributes that are not eligible for update\r\n* Error handling\r\n * an empty content response\r\n * an error when rule's id is not specified\r\n * an error when undefined payload has been passed\r\n\r\nAlso, as part of this PR, I added error handling cases for Create API:\r\n* no content error\r\n* an error when undefined payload has been passed\r\n* an error when original rule id is not specified\r\n* error when original rule vendor is not specified\r\n* an error when original rule title is not specified\r\n* an error when original rule description is not specified\r\n* an error when original rule query is not specified\r\n* an error when original rule query_language is not specified\r\n\r\n---------\r\n\r\nCo-authored-by: Sergi Massaneda <sergi.massaneda@gmail.com>","sha":"819fd7a3e9f0e885bc22f382dcc165ea1a4b55e7"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
5b03868aa2
|
[8.18] Upgrade elliptic 6.5.7 → 6.6.1 (#211225) (#211292)
# Backport This will backport the following commits from `main` to `8.18`: - [Upgrade elliptic 6.5.7 → 6.6.1 (#211225)](https://github.com/elastic/kibana/pull/211225) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:29:24Z","message":"Upgrade elliptic 6.5.7 → 6.6.1 (#211225)\n\n## Summary\n\nUpgrades `elliptic` from v6.5.7 to v6.6.1","sha":"20aac5c9158fbfcfa4bd3284b169eaa192da53db","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"],"title":"Upgrade elliptic 6.5.7 → 6.6.1","number":211225,"url":"https://github.com/elastic/kibana/pull/211225","mergeCommit":{"message":"Upgrade elliptic 6.5.7 → 6.6.1 (#211225)\n\n## Summary\n\nUpgrades `elliptic` from v6.5.7 to v6.6.1","sha":"20aac5c9158fbfcfa4bd3284b169eaa192da53db"}},"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/211225","number":211225,"mergeCommit":{"message":"Upgrade elliptic 6.5.7 → 6.6.1 (#211225)\n\n## Summary\n\nUpgrades `elliptic` from v6.5.7 to v6.6.1","sha":"20aac5c9158fbfcfa4bd3284b169eaa192da53db"}}]}] BACKPORT--> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> |
||
|
Kibana Machine
|
10bb0b2f9e
|
[8.18] [Security Solution] Refactor prebuilt rule customization test plans, part 1 (#211300) (#211306)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Refactor prebuilt rule customization test plans, part 1 (#211300)](https://github.com/elastic/kibana/pull/211300) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Georgii Gorbachev","email":"georgii.gorbachev@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T18:22:45Z","message":"[Security Solution] Refactor prebuilt rule customization test plans, part 1 (#211300)\n\n**Epic:** https://github.com/elastic/kibana/issues/174168\r\n**Partially addresses:**\r\nhttps://github.com/elastic/kibana/issues/202068,\r\nhttps://github.com/elastic/kibana/issues/202078,\r\nhttps://github.com/elastic/kibana/issues/202079\r\n\r\n## Summary\r\n\r\nWe're cleaning up and refactoring our existing test plans for prebuilt\r\nrule customization, upgrade, and export/import workflows.\r\n\r\nSpecifically, in this PR we're consistently:\r\n\r\n- Changing the file names and test plan titles.\r\n- Adding or expanding test plan summaries.\r\n- Regenerating tables of contents using the [Markdown All in\r\nOne](https://marketplace.visualstudio.com/items?itemName=yzhang.markdown-all-in-one)\r\nVS Code extension.\r\n\r\nNo \"functional\" changes have been made to any test plans, such as\r\nadding, removing, or updating any scenarios.\r\n\r\nThis refactoring prepares the test plans for being \"functionally\"\r\nchanged and improved in follow-up PRs. For example, we're going to cover\r\nthe logic described in https://github.com/elastic/kibana/issues/210358\r\nand address any other gaps in coverage.","sha":"9600de4338edc123dbac7c2cb3403ede2f016752","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","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] Refactor prebuilt rule customization test plans, part 1","number":211300,"url":"https://github.com/elastic/kibana/pull/211300","mergeCommit":{"message":"[Security Solution] Refactor prebuilt rule customization test plans, part 1 (#211300)\n\n**Epic:** https://github.com/elastic/kibana/issues/174168\r\n**Partially addresses:**\r\nhttps://github.com/elastic/kibana/issues/202068,\r\nhttps://github.com/elastic/kibana/issues/202078,\r\nhttps://github.com/elastic/kibana/issues/202079\r\n\r\n## Summary\r\n\r\nWe're cleaning up and refactoring our existing test plans for prebuilt\r\nrule customization, upgrade, and export/import workflows.\r\n\r\nSpecifically, in this PR we're consistently:\r\n\r\n- Changing the file names and test plan titles.\r\n- Adding or expanding test plan summaries.\r\n- Regenerating tables of contents using the [Markdown All in\r\nOne](https://marketplace.visualstudio.com/items?itemName=yzhang.markdown-all-in-one)\r\nVS Code extension.\r\n\r\nNo \"functional\" changes have been made to any test plans, such as\r\nadding, removing, or updating any scenarios.\r\n\r\nThis refactoring prepares the test plans for being \"functionally\"\r\nchanged and improved in follow-up PRs. For example, we're going to cover\r\nthe logic described in https://github.com/elastic/kibana/issues/210358\r\nand address any other gaps in coverage.","sha":"9600de4338edc123dbac7c2cb3403ede2f016752"}},"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/211300","number":211300,"mergeCommit":{"message":"[Security Solution] Refactor prebuilt rule customization test plans, part 1 (#211300)\n\n**Epic:** https://github.com/elastic/kibana/issues/174168\r\n**Partially addresses:**\r\nhttps://github.com/elastic/kibana/issues/202068,\r\nhttps://github.com/elastic/kibana/issues/202078,\r\nhttps://github.com/elastic/kibana/issues/202079\r\n\r\n## Summary\r\n\r\nWe're cleaning up and refactoring our existing test plans for prebuilt\r\nrule customization, upgrade, and export/import workflows.\r\n\r\nSpecifically, in this PR we're consistently:\r\n\r\n- Changing the file names and test plan titles.\r\n- Adding or expanding test plan summaries.\r\n- Regenerating tables of contents using the [Markdown All in\r\nOne](https://marketplace.visualstudio.com/items?itemName=yzhang.markdown-all-in-one)\r\nVS Code extension.\r\n\r\nNo \"functional\" changes have been made to any test plans, such as\r\nadding, removing, or updating any scenarios.\r\n\r\nThis refactoring prepares the test plans for being \"functionally\"\r\nchanged and improved in follow-up PRs. For example, we're going to cover\r\nthe logic described in https://github.com/elastic/kibana/issues/210358\r\nand address any other gaps in coverage.","sha":"9600de4338edc123dbac7c2cb3403ede2f016752"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co> |
||
|
Kibana Machine
|
dd449b3158
|
[8.18] [ES|QL] Fixes the values control FT (#211159) (#211280)
# Backport This will backport the following commits from `main` to `8.18`: - [[ES|QL] Fixes the values control FT (#211159)](https://github.com/elastic/kibana/pull/211159) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Stratoula Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:00:03Z","message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Presentation","Feature:ES|QL","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[ES|QL] Fixes the values control FT","number":211159,"url":"https://github.com/elastic/kibana/pull/211159","mergeCommit":{"message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211159","number":211159,"mergeCommit":{"message":"[ES|QL] Fixes the values control FT (#211159)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/208454\n\nAttempt to make the value controls FR more stable","sha":"d3fd2ed7701b54f6048046d3f93e1bc8929dd686"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co> |
||
Jean-Louis Leysens
|
d916369824
|
[8.18] [UA] Exclude enterprise search indices "Old index" deprecations (#210526) (#211162)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[UA] Exclude enterprise search indices "Old index" deprecations (#210526)](https://github.com/elastic/kibana/pull/210526) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jean-Louis Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T18:23:43Z","message":"[UA] Exclude enterprise search indices \"Old index\" deprecations (#210526)\n\n## Summary\r\n\r\nExclude any \"Old data\" deprecations for `.ent-search-` indices. Note,\r\nother deprecations will still be present like frozen index deprecations:\r\n\r\n<img width=\"1219\" alt=\"Screenshot 2025-02-11 at 11 23 14\"\r\nsrc=\"https://github.com/user-attachments/assets/f896b919-f7e0-4a7e-b2ee-418db2bc1724\"\r\n/>","sha":"058845046e698cd8a57b7dce1ea2fe3397569ce9","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["blocked","Team:Core","release_note:skip","Feature:Upgrade Assistant","backport:version","v8.18.0","v8.19.0"],"title":"[UA] Exclude enterprise search indices \"Old index\" deprecations","number":210526,"url":"https://github.com/elastic/kibana/pull/210526","mergeCommit":{"message":"[UA] Exclude enterprise search indices \"Old index\" deprecations (#210526)\n\n## Summary\r\n\r\nExclude any \"Old data\" deprecations for `.ent-search-` indices. Note,\r\nother deprecations will still be present like frozen index deprecations:\r\n\r\n<img width=\"1219\" alt=\"Screenshot 2025-02-11 at 11 23 14\"\r\nsrc=\"https://github.com/user-attachments/assets/f896b919-f7e0-4a7e-b2ee-418db2bc1724\"\r\n/>","sha":"058845046e698cd8a57b7dce1ea2fe3397569ce9"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4bcd166b3a
|
[8.18] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211284)
# Backport This will backport the following commits from `main` to `8.18`: - [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)](https://github.com/elastic/kibana/pull/211231) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:07:41Z","message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-major","v9.1.0"],"title":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin","number":211231,"url":"https://github.com/elastic/kibana/pull/211231","mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211231","number":211231,"mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}}]}] BACKPORT--> Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
Karen Grigoryan
|
ef85e7491b
|
[8.18] [Security Solution][Explore] Migrate from styled-components in shared (#210311) (#211226)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Explore] Migrate from styled-components in shared (#210311)](https://github.com/elastic/kibana/pull/210311) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Karen Grigoryan","email":"karen.grigoryan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T16:14:34Z","message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team:Threat Hunting:Explore","backport:version","v8.18.0","EUI Visual Refresh","v9.1.0","v8.19.0"],"title":"[Security Solution][Explore] Migrate from styled-components in shared","number":210311,"url":"https://github.com/elastic/kibana/pull/210311","mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210311","number":210311,"mergeCommit":{"message":"[Security Solution][Explore] Migrate from styled-components in shared (#210311)\n\nAddresses #206436\r\n\r\n- Replace styled-components with @emotion/react and @emotion/styled\r\nacross multiple components\r\n- Remove `@kbn/ui-theme` instances\r\n- Update test cases to use @emotion/jest matchers for toHaveStyleRule to\r\nwork properly\r\n- Adjust styles to use `css` from `@emotion/react`\r\n- Remove unused imports and updated snapshots\r\n\r\n\r\nhttps://github.com/user-attachments/assets/48b9ab41-23fd-4c00-ace9-c0cbe58c91f7","sha":"4b4c5ce491aa6539867c3de789ff604880a7fc2e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
9944e1af97
|
[8.18] [Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034) (#211227)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)](https://github.com/elastic/kibana/pull/211034) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T14:13:32Z","message":"[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)\n\n## Summary\r\n\r\nThis PR fixes Rule Management Prebuilt Rules preview Cypress tests flakiness. The flakiness was localized to `prebuilt_rules_preview.cy.ts`.\r\n\r\n## Problem details\r\n\r\nQuite recently Rule Management Prebuilt Cypress tests group started failing due to exceeding 1 hour execution limit. In normal conditions the group takes up to 45 minutes to run all the tests.\r\n\r\nInvestigation revealed the problem. It turned out the real prebuilt rules get installed while it's not expected. The absolute majority of the tests interact with a few prebuilt rule assets mocks to avoid heavy prebuilt rules package installation and installing more than 1K rules from the package. \r\n\r\n\r\nIn particular `/internal/detection_engine/prebuilt_rules/_bootstrap` endpoint is invoked upon loading any Security Solution plugin's page and leads to installing a prebuilt rules package. The Cypress test code was organized in way that first the Rule Management page is opened and then API calls interception is set up. Since page loading may vary sometimes real calls to `/internal/detection_engine/prebuilt_rules/_bootstrap` went through.\r\n\r\nTests set up prebuilt rule assets mocks but real prebuilt rules package installation wiped out the mocks leading to failing tests. Since Cypress reruns failed tests execution time increases and exceeds the limit.\r\n\r\n\r\n\r\n*`installPrebuiltRuleAssets()` sets up `/internal/detection_engine/prebuilt_rules/_bootstrap` calls interception.\r\n\r\n## Flaky test runs\r\n\r\n**Before:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` was run in Flaky test runner with 100 iterations. The CI is green but it's easy to notice some jobs took approximately 1 hour to run.\r\n 🔴 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7870\r\n\r\n**After:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` with the fix was run in Flaky test runner with 100 iterations. Execution time approximately 15 minutes for each job.\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7873\r\n\r\n- Rule Management Prebuilt Cypress tests group was run with 100 iterations\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7875","sha":"67163cb80231ad78cab96f091203660d4da7559f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["test","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] Fix flakiness in `prebuilt_rules_preview.cy.ts`","number":211034,"url":"https://github.com/elastic/kibana/pull/211034","mergeCommit":{"message":"[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)\n\n## Summary\r\n\r\nThis PR fixes Rule Management Prebuilt Rules preview Cypress tests flakiness. The flakiness was localized to `prebuilt_rules_preview.cy.ts`.\r\n\r\n## Problem details\r\n\r\nQuite recently Rule Management Prebuilt Cypress tests group started failing due to exceeding 1 hour execution limit. In normal conditions the group takes up to 45 minutes to run all the tests.\r\n\r\nInvestigation revealed the problem. It turned out the real prebuilt rules get installed while it's not expected. The absolute majority of the tests interact with a few prebuilt rule assets mocks to avoid heavy prebuilt rules package installation and installing more than 1K rules from the package. \r\n\r\n\r\nIn particular `/internal/detection_engine/prebuilt_rules/_bootstrap` endpoint is invoked upon loading any Security Solution plugin's page and leads to installing a prebuilt rules package. The Cypress test code was organized in way that first the Rule Management page is opened and then API calls interception is set up. Since page loading may vary sometimes real calls to `/internal/detection_engine/prebuilt_rules/_bootstrap` went through.\r\n\r\nTests set up prebuilt rule assets mocks but real prebuilt rules package installation wiped out the mocks leading to failing tests. Since Cypress reruns failed tests execution time increases and exceeds the limit.\r\n\r\n\r\n\r\n*`installPrebuiltRuleAssets()` sets up `/internal/detection_engine/prebuilt_rules/_bootstrap` calls interception.\r\n\r\n## Flaky test runs\r\n\r\n**Before:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` was run in Flaky test runner with 100 iterations. The CI is green but it's easy to notice some jobs took approximately 1 hour to run.\r\n 🔴 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7870\r\n\r\n**After:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` with the fix was run in Flaky test runner with 100 iterations. Execution time approximately 15 minutes for each job.\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7873\r\n\r\n- Rule Management Prebuilt Cypress tests group was run with 100 iterations\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7875","sha":"67163cb80231ad78cab96f091203660d4da7559f"}},"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/211034","number":211034,"mergeCommit":{"message":"[Security Solution] Fix flakiness in `prebuilt_rules_preview.cy.ts` (#211034)\n\n## Summary\r\n\r\nThis PR fixes Rule Management Prebuilt Rules preview Cypress tests flakiness. The flakiness was localized to `prebuilt_rules_preview.cy.ts`.\r\n\r\n## Problem details\r\n\r\nQuite recently Rule Management Prebuilt Cypress tests group started failing due to exceeding 1 hour execution limit. In normal conditions the group takes up to 45 minutes to run all the tests.\r\n\r\nInvestigation revealed the problem. It turned out the real prebuilt rules get installed while it's not expected. The absolute majority of the tests interact with a few prebuilt rule assets mocks to avoid heavy prebuilt rules package installation and installing more than 1K rules from the package. \r\n\r\n\r\nIn particular `/internal/detection_engine/prebuilt_rules/_bootstrap` endpoint is invoked upon loading any Security Solution plugin's page and leads to installing a prebuilt rules package. The Cypress test code was organized in way that first the Rule Management page is opened and then API calls interception is set up. Since page loading may vary sometimes real calls to `/internal/detection_engine/prebuilt_rules/_bootstrap` went through.\r\n\r\nTests set up prebuilt rule assets mocks but real prebuilt rules package installation wiped out the mocks leading to failing tests. Since Cypress reruns failed tests execution time increases and exceeds the limit.\r\n\r\n\r\n\r\n*`installPrebuiltRuleAssets()` sets up `/internal/detection_engine/prebuilt_rules/_bootstrap` calls interception.\r\n\r\n## Flaky test runs\r\n\r\n**Before:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` was run in Flaky test runner with 100 iterations. The CI is green but it's easy to notice some jobs took approximately 1 hour to run.\r\n 🔴 https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7870\r\n\r\n**After:**\r\n\r\n- `prebuilt_rules_preview.cy.ts` with the fix was run in Flaky test runner with 100 iterations. Execution time approximately 15 minutes for each job.\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7873\r\n\r\n- Rule Management Prebuilt Cypress tests group was run with 100 iterations\r\n ✅ https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7875","sha":"67163cb80231ad78cab96f091203660d4da7559f"}},{"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
|
d2a626f983
|
[8.18] [Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645) (#211249)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)](https://github.com/elastic/kibana/pull/205645) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T15:21:09Z","message":"[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)\n\n**Epics:** https://github.com/elastic/security-team/issues/1974\r\n(internal), https://github.com/elastic/kibana/issues/174168\r\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR adds a test plan for rule upgrade flyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"ecd33168b152d0c268d4cec7881deedeb7628814","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","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] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1","number":205645,"url":"https://github.com/elastic/kibana/pull/205645","mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)\n\n**Epics:** https://github.com/elastic/security-team/issues/1974\r\n(internal), https://github.com/elastic/kibana/issues/174168\r\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR adds a test plan for rule upgrade flyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"ecd33168b152d0c268d4cec7881deedeb7628814"}},"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/205645","number":205645,"mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules with preview (Rule Upgrade flyout) v1 (#205645)\n\n**Epics:** https://github.com/elastic/security-team/issues/1974\r\n(internal), https://github.com/elastic/kibana/issues/174168\r\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR adds a test plan for rule upgrade flyout.\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"ecd33168b152d0c268d4cec7881deedeb7628814"}},{"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
|
3f4fc859c8
|
[8.18] [Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922) (#211245)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)](https://github.com/elastic/kibana/pull/205922) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Maxim Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T15:18:40Z","message":"[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR extends rule upgrade test plan with customizable and\r\nnon-customizable field examples. Rule upgrade workflow test plan\r\n(excluding Rule Upgrade flyout) was initially extended in\r\nhttps://github.com/elastic/kibana/pull/203331.\r\n\r\nhttps://github.com/elastic/kibana/pull/203331 adds the following rule\r\nupgrade workflow scenarios\r\n\r\n- Scenario: User can upgrade conflict-free prebuilt rules one by one\r\n- Scenario: User cannot upgrade prebuilt rules one by one from Rules\r\nUpdate table if they have conflicts\r\n- Scenario: User can upgrade multiple conflict-free prebuilt rules\r\nselected on the page\r\n- Scenario: User cannot upgrade selected prebuilt rules with conflicts\r\n- Scenario: User can upgrade all available conflict-free prebuilt rules\r\nat once*\r\n- Scenario: User cannot upgrade all prebuilt rules at once if they have\r\nupgrade conflicts\r\n- Scenario: User can upgrade only conflict-free rules when a mix of\r\nrules with and without conflicts are selected for upgrade\r\n- Scenario: User can upgrade only conflict-free rules when attempting to\r\nupgrade all rules\r\n- Scenario: User can upgrade rule with rule type change individually\r\n- Scenario: User can not bulk upgrade selected rules with rule type\r\nchanges\r\n- Scenario: User can not bulk upgrade all rules with rule type changes\r\n- Scenario: API does not upgrade prebuilt rules if they are up to date\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"e29033a726930c3d891aa77ea4f7ed990c7ee511","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","test-plan","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] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2","number":205922,"url":"https://github.com/elastic/kibana/pull/205922","mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR extends rule upgrade test plan with customizable and\r\nnon-customizable field examples. Rule upgrade workflow test plan\r\n(excluding Rule Upgrade flyout) was initially extended in\r\nhttps://github.com/elastic/kibana/pull/203331.\r\n\r\nhttps://github.com/elastic/kibana/pull/203331 adds the following rule\r\nupgrade workflow scenarios\r\n\r\n- Scenario: User can upgrade conflict-free prebuilt rules one by one\r\n- Scenario: User cannot upgrade prebuilt rules one by one from Rules\r\nUpdate table if they have conflicts\r\n- Scenario: User can upgrade multiple conflict-free prebuilt rules\r\nselected on the page\r\n- Scenario: User cannot upgrade selected prebuilt rules with conflicts\r\n- Scenario: User can upgrade all available conflict-free prebuilt rules\r\nat once*\r\n- Scenario: User cannot upgrade all prebuilt rules at once if they have\r\nupgrade conflicts\r\n- Scenario: User can upgrade only conflict-free rules when a mix of\r\nrules with and without conflicts are selected for upgrade\r\n- Scenario: User can upgrade only conflict-free rules when attempting to\r\nupgrade all rules\r\n- Scenario: User can upgrade rule with rule type change individually\r\n- Scenario: User can not bulk upgrade selected rules with rule type\r\nchanges\r\n- Scenario: User can not bulk upgrade all rules with rule type changes\r\n- Scenario: API does not upgrade prebuilt rules if they are up to date\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"e29033a726930c3d891aa77ea4f7ed990c7ee511"}},"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/205922","number":205922,"mergeCommit":{"message":"[Security Solution] Test plan for upgrading prebuilt rules without preview (Rule Updates table) v2 (#205922)\n\n**Addresses:** https://github.com/elastic/kibana/issues/202078\r\n\r\n## Summary\r\n\r\nThis PR extends rule upgrade test plan with customizable and\r\nnon-customizable field examples. Rule upgrade workflow test plan\r\n(excluding Rule Upgrade flyout) was initially extended in\r\nhttps://github.com/elastic/kibana/pull/203331.\r\n\r\nhttps://github.com/elastic/kibana/pull/203331 adds the following rule\r\nupgrade workflow scenarios\r\n\r\n- Scenario: User can upgrade conflict-free prebuilt rules one by one\r\n- Scenario: User cannot upgrade prebuilt rules one by one from Rules\r\nUpdate table if they have conflicts\r\n- Scenario: User can upgrade multiple conflict-free prebuilt rules\r\nselected on the page\r\n- Scenario: User cannot upgrade selected prebuilt rules with conflicts\r\n- Scenario: User can upgrade all available conflict-free prebuilt rules\r\nat once*\r\n- Scenario: User cannot upgrade all prebuilt rules at once if they have\r\nupgrade conflicts\r\n- Scenario: User can upgrade only conflict-free rules when a mix of\r\nrules with and without conflicts are selected for upgrade\r\n- Scenario: User can upgrade only conflict-free rules when attempting to\r\nupgrade all rules\r\n- Scenario: User can upgrade rule with rule type change individually\r\n- Scenario: User can not bulk upgrade selected rules with rule type\r\nchanges\r\n- Scenario: User can not bulk upgrade all rules with rule type changes\r\n- Scenario: API does not upgrade prebuilt rules if they are up to date\r\n\r\n---------\r\n\r\nCo-authored-by: Georgii Gorbachev <georgii.gorbachev@elastic.co>","sha":"e29033a726930c3d891aa77ea4f7ed990c7ee511"}},{"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> |
||
|
Jean-Louis Leysens
|
22a7481989
|
[8.18] [UA] Handle frozen indices deprecations (#208156) (#211165)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[UA] Handle frozen indices deprecations (#208156)](https://github.com/elastic/kibana/pull/208156) <!--- Backport version: 8.9.8 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Gerard Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2025-01-30T22:36:28Z","message":"[UA] Handle frozen indices deprecations (#208156)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana-team/issues/1392\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cc358e3c46e5df2af834e341114f23aa1fd4f7d1","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:version","v8.18.0","v8.19.0"],"number":208156,"url":"https://github.com/elastic/kibana/pull/208156","mergeCommit":{"message":"[UA] Handle frozen indices deprecations (#208156)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana-team/issues/1392\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"cc358e3c46e5df2af834e341114f23aa1fd4f7d1"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co> |
||
Alex Szabo
|
bd324526fc | skip failing suite (#206068) | ||
|
Alex Szabo
|
f7a5e7dc7f | skip failing suite (#205987) | ||
|
Alex Szabo
|
e9e744dc95 | skip failing suite (#206368) | ||
|
Angela Chuang
|
92e54c4d69
|
[8.18][SecuritySolution] Update severity colors for Borealis theme (#206276) (#211021)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution]Update severity colors for Borealis theme (#206276)](https://github.com/elastic/kibana/pull/206276) |
||
Tiago Costa
|
c7f893aebd
|
[8.18] chore(NA): upgrade to webpack 5 (#191106) (#211147)
# Backport This will backport the following commits from `main` to `8.18`: - [chore(NA): upgrade to webpack 5 (#191106)](https://github.com/elastic/kibana/pull/191106) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T03:01:36Z","message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open","ci:build-webpack-bundle-analyzer","Team:obs-ux-infra_services","v9.1.0"],"title":"chore(NA): upgrade to webpack 5","number":191106,"url":"https://github.com/elastic/kibana/pull/191106","mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211145","number":211145,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/191106","number":191106,"mergeCommit":{"message":"chore(NA): upgrade to webpack 5 (#191106)\n\n### Summary\r\n\r\n- Closes #89741\r\n\r\nThis PR contains the resulting work of a massive effort that ports our\r\non top bundler abstraction (called @kbn/optimizer) from Webpack v4 into\r\nWebpack v5. It's essential in terms of long term maintenance since v4\r\nwas not receiving updates any longer but will also unblock some new\r\nfeatures that could be beneficial for our future DevEx endeavours.\r\n\r\nNext you can find a small list of all the accomplished tasks on this\r\njourney.\r\n\r\n### Completed Tasks\r\n- [x] Upgrade dependencies to match the ones on webpack v5\r\n- [x] Fix null-loader usages\r\n- [x] Fix raw-loader usages\r\n- [x] Fix file-loader usages\r\n- [x] Fix url-loader usages\r\n- [x] Fix `@kbn/optimizer-webpack-helpers` to support webpack v5 \r\n- [x] Adopt previous webpack v4 polyfill-all strategy with\r\nnode-polyfill-webpack-plugin\r\n- [x] Fix theme-loader on @kbn/optimizer\r\n- [x] Migrate configurations and ad-hoc loader options on all webpack\r\nconfigs from v4 to v5\r\n- [x] Fix @kbn/test jest resolver for file-loader cases\r\n- [x] Migrate public-path loader on UiSharedDeps\r\n- [x] Fix all usages of webpack-merge\r\n- [x] Migrate BundleRemoteModule\r\n- [x] Migrate BundleRemotesPlugin\r\n- [x] Correctly migrate PopulateBundleCachePlugin\r\n- [x] Correctly migrate BundleMetricsPlugin\r\n- [x] Check if the profiling plugins still work (--profile flag)\r\n- [x] Recover if possible the previous webpack v4 cacheGroup chunks\r\nrename to something like `data.plugin.chunk.0.js`\r\n- [x] Run `/ci` and make sure we get our first green CI, otherwise work\r\non the errors until we do\r\n- [x] Profile and solve bottlenecks until we get a cold build\r\nperformance similar to the one we had on webpack v4 (`node\r\nscripts/build_kibana_platform_plugins --no-cache`).\r\n- [x] OpenSSL Legacy Warnings: try to remove `--openssl-legacy-provider\r\n` flags\r\n- [x] Add Webpack to Renovate config\r\n- [x] Explore removing `NodePolyfillPlugin`\r\n([here](https://www.npmjs.com/package/node-polyfill-webpack-plugin)) and\r\nadd each polyfill needed individually per each webpack config to check\r\nif we get smaller bundles. If we do it's better to go with the case by\r\ncase need approach instead of deploying a bunch of polyfills with\r\nNodePolyfillPlugin. As another alternative, create a custom smaller\r\nplugin with only the union of all needed polyfills.\r\n- [x] Evaluate if we want to touch the resolutions on mainFields and\r\nconditionNames\r\n- [x] Understand why `@import 'src/core/public/mixins'` does not work\r\nanymore (not a problem, we should use relative paths anyway but we want\r\nto track why it changed from v4 to v5)\r\n- [x] BUG: Child compilers are having errors hidden and/or changed from\r\nerror to warning\r\n- [x] Fix license check for\r\n[Artistic-2.0](https://spdx.org/licenses/Artistic-2.0.html) is the\r\nlicense for\r\n[domain-browser](https://github.com/bevry/domain-browser?tab=License-1-ov-file).\r\nThis package is a dependency of\r\n[NodePolyfillPlugin](https://www.npmjs.com/package/node-polyfill-webpack-plugin).\r\nArtistic 2.0 license is [classified as\r\nyellow](https://github.com/elastic/open-source/blob/main/elastic-product-policy.md#yellow-list)\r\nand should only be used for dev dependencies.\r\n- [x] Make sure `resourceQuery: { not: /raw/ }` is not necessary on\r\nother webpack configs like storybook one\r\n- [x] Find what is being wrongly removed by usedExports optimization;\r\nhint: I believe it is identifying a lot of exports inside the sync entry\r\nof plugins as unused exports and removing them. Then `__kbnBootstrap__`\r\ncan't be found\r\n- [x] Rebalance @kbn/optimizer pickMaxWorkerCount\r\n- [x] Re-open the issue to fix sass-warnings\r\n[#190345](https://github.com/elastic/kibana/issues/190345) or downgrade\r\nsass-loader to v10\r\n- [x] Remove previous esm no parse rules\r\n- [x] Confirm esm support is working\r\n- [x] Confirm console override is needed\r\n- [x] Confirm react prod builds on ui shared deps for distributable\r\n- [x] Remove customization for\r\n[xyflow](https://github.com/xyflow/xyflow) from webpack configs\r\n- [x] Clean all the code\r\n- [x] Make sure collected metrics from stats are still aligned with what\r\nwe were collecting before; also verify if the modules used for optimizer\r\ncaches etc are well generated (@kbn/node-libs-browser)\r\n- [x] Fix watch performance\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Brad White <brad.white@elastic.co>","sha":"203bc284781cc830049b3f7948c8fcafa8b7d9a1"}},{"url":"https://github.com/elastic/kibana/pull/211146","number":211146,"branch":"8.x","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
a163691e0f
|
[8.18] Fix notify_badge.tsx toggle not working (#208996) (#211186)
# Backport This will backport the following commits from `main` to `8.18`: - [Fix notify_badge.tsx toggle not working (#208996)](https://github.com/elastic/kibana/pull/208996) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Eamonn-OL","email":"119305140+Eamonn-OL@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T09:56:43Z","message":"Fix notify_badge.tsx toggle not working (#208996)\n\n## Summary\n\nAt the moment, when you click on the notify badge in the \"rules\" page,\nthen click it again (expecting a toggle) it actually gets stuck on the\npage and only a refresh can fix it.\n\nThis change adds a toggle and implements it in place of the\n\"openPopover\" to correctly toggle the state of the popover.\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\n\n\n## Release Notes\n\nFixes an issue where the popover in the rules page may get stuck when\nbeing clicked more than once.\n\nBefore:\n\n\n |
||
|
Kibana Machine
|
6db8685223
|
[8.18] [Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826) (#211170)
# Backport This will backport the following commits from `main` to `8.18`: - [[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)](https://github.com/elastic/kibana/pull/210826) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-14T09:18:55Z","message":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)\n\n## Summary\n\nThis PR fixes a bug due to multiple subscription created by the ESQL\nvariables logic in the embeddable to never been cancelled.\nThe fix was to move the subscription in the loader module and make it\ncleanup correctly together with other subscription.\n\nUnit tests have been added to check the correct re-render behaviour.\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":"34baecba3e11a14f5aaf3badc053056084945b33","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-major","v9.1.0"],"title":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription","number":210826,"url":"https://github.com/elastic/kibana/pull/210826","mergeCommit":{"message":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)\n\n## Summary\n\nThis PR fixes a bug due to multiple subscription created by the ESQL\nvariables logic in the embeddable to never been cancelled.\nThe fix was to move the subscription in the loader module and make it\ncleanup correctly together with other subscription.\n\nUnit tests have been added to check the correct re-render behaviour.\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":"34baecba3e11a14f5aaf3badc053056084945b33"}},"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/210826","number":210826,"mergeCommit":{"message":"[Lens][Embeddable] Fix memory leak on ES|QL variables subscription (#210826)\n\n## Summary\n\nThis PR fixes a bug due to multiple subscription created by the ESQL\nvariables logic in the embeddable to never been cancelled.\nThe fix was to move the subscription in the loader module and make it\ncleanup correctly together with other subscription.\n\nUnit tests have been added to check the correct re-render behaviour.\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":"34baecba3e11a14f5aaf3badc053056084945b33"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
|
Bharat Pasupula
|
d7f4eddcf4
|
[8.18] [Automatic Import] Fix generated name for integration title (#210916) (#211150)
# Backport This will backport the following commits from `main` to `8.18`: - [[Automatic Import] Fix generated name for integration title (#210916)](https://github.com/elastic/kibana/pull/210916) <!--- Backport version: 9.6.4 --> ### 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-02-13T16:02:03Z","message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix generated name for integration title","number":210916,"url":"https://github.com/elastic/kibana/pull/210916","mergeCommit":{"message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211037","number":211037,"state":"MERGED","mergeCommit":{"sha":"badb523efc6e567dc33136f84bae6c240de7ab4c","message":"[9.0] [Automatic Import] Fix generated name for integration title (#210916) (#211037)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Automatic Import] Fix generated name for integration title\n(#210916)](https://github.com/elastic/kibana/pull/210916)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Bharat\nPasupula\",\"email\":\"123897612+bhapas@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-13T16:02:03Z\",\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\"backport:prev-minor\",\"Team:Security-Scalability\",\"Feature:AutomaticImport\",\"v9.1.0\"],\"title\":\"[Automatic\nImport] Fix generated name for integration\ntitle\",\"number\":210916,\"url\":\"https://github.com/elastic/kibana/pull/210916\",\"mergeCommit\":{\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\"}},\"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/210916\",\"number\":210916,\"mergeCommit\":{\"message\":\"[Automatic\nImport] Fix generated name for integration title (#210916)\\n\\n##\nSummary\\r\\n\\r\\nA bug was introduced with #210770 and this PR fixes that.\nThe Package\\r\\nname generated is\nvalidated.\",\"sha\":\"cf0f338d8749c90024b2409fbb7b036469bfab6e\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Bharat Pasupula <123897612+bhapas@users.noreply.github.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210916","number":210916,"mergeCommit":{"message":"[Automatic Import] Fix generated name for integration title (#210916)\n\n## Summary\r\n\r\nA bug was introduced with #210770 and this PR fixes that. The Package\r\nname generated is validated.","sha":"cf0f338d8749c90024b2409fbb7b036469bfab6e"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
0f548e8040
|
[8.18] [Fleet] Make sure null checks are included for agentless next steps tile (#211068) (#211143)
# Backport This will backport the following commits from `main` to `8.18`: - [[Fleet] Make sure null checks are included for agentless next steps tile (#211068)](https://github.com/elastic/kibana/pull/211068) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kyle Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T21:53:37Z","message":"[Fleet] Make sure null checks are included for agentless next steps tile (#211068)\n\n## Summary\n\nCloses https://github.com/elastic/security-team/issues/11870\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] 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: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"11211cfb273a49f5341db5da80bf401d577e57b4","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor","backport:prev-major","v9.1.0","backport:8.18"],"title":"[Fleet] Make sure null checks are included for agentless next steps tile","number":211068,"url":"https://github.com/elastic/kibana/pull/211068","mergeCommit":{"message":"[Fleet] Make sure null checks are included for agentless next steps tile (#211068)\n\n## Summary\n\nCloses https://github.com/elastic/security-team/issues/11870\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] 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: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"11211cfb273a49f5341db5da80bf401d577e57b4"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211120","number":211120,"state":"MERGED","mergeCommit":{"sha":"8fa37fdc98cf9d482c2f3e32640be3fd9aad43bd","message":"[9.0] [Fleet] Make sure null checks are included for agentless next steps tile (#211068) (#211120)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Fleet] Make sure null checks are included for agentless next steps\ntile (#211068)](https://github.com/elastic/kibana/pull/211068)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Kyle\nPollich\",\"email\":\"kyle.pollich@elastic.co\"},\"sourceCommit\":{\"committedDate\":\"2025-02-13T21:53:37Z\",\"message\":\"[Fleet]\nMake sure null checks are included for agentless next steps tile\n(#211068)\\n\\n## Summary\\n\\nCloses\nhttps://github.com/elastic/security-team/issues/11870\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] The PR\ndescription includes the appropriate Release Notes section,\\nand the\ncorrect `release_note:*` label is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n---------\\n\\nCo-authored-by:\nNicolas Chaulet\n<nicolas.chaulet@elastic.co>\",\"sha\":\"11211cfb273a49f5341db5da80bf401d577e57b4\",\"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\",\"backport:8.18\"],\"title\":\"[Fleet]\nMake sure null checks are included for agentless next steps\ntile\",\"number\":211068,\"url\":\"https://github.com/elastic/kibana/pull/211068\",\"mergeCommit\":{\"message\":\"[Fleet]\nMake sure null checks are included for agentless next steps tile\n(#211068)\\n\\n## Summary\\n\\nCloses\nhttps://github.com/elastic/security-team/issues/11870\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] The PR\ndescription includes the appropriate Release Notes section,\\nand the\ncorrect `release_note:*` label is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n---------\\n\\nCo-authored-by:\nNicolas Chaulet\n<nicolas.chaulet@elastic.co>\",\"sha\":\"11211cfb273a49f5341db5da80bf401d577e57b4\"}},\"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/211068\",\"number\":211068,\"mergeCommit\":{\"message\":\"[Fleet]\nMake sure null checks are included for agentless next steps tile\n(#211068)\\n\\n## Summary\\n\\nCloses\nhttps://github.com/elastic/security-team/issues/11870\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] [Unit or\nfunctional\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\nwere\nupdated or added to match the most common scenarios\\n- [ ] The PR\ndescription includes the appropriate Release Notes section,\\nand the\ncorrect `release_note:*` label is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n---------\\n\\nCo-authored-by:\nNicolas Chaulet\n<nicolas.chaulet@elastic.co>\",\"sha\":\"11211cfb273a49f5341db5da80bf401d577e57b4\"}}]}]\nBACKPORT-->\n\nCo-authored-by: Kyle Pollich <kyle.pollich@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211068","number":211068,"mergeCommit":{"message":"[Fleet] Make sure null checks are included for agentless next steps tile (#211068)\n\n## Summary\n\nCloses https://github.com/elastic/security-team/issues/11870\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] 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: Nicolas Chaulet <nicolas.chaulet@elastic.co>","sha":"11211cfb273a49f5341db5da80bf401d577e57b4"}}]}] BACKPORT--> Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co> |
||
|
Kibana Machine
|
74f6bcef63
|
[8.18] [Navigation] Add stack monitoring to Elasticsearch sidebar (#210139) (#211137)
# Backport This will backport the following commits from `main` to `8.18`: - [[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)](https://github.com/elastic/kibana/pull/210139) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T16:22:49Z","message":"[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"9dc67bfd8836e8d3a2f0480d997b11d9e7e9106f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","v9.0.0","Team:Search","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Navigation] Add stack monitoring to Elasticsearch sidebar","number":210139,"url":"https://github.com/elastic/kibana/pull/210139","mergeCommit":{"message":"[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"9dc67bfd8836e8d3a2f0480d997b11d9e7e9106f"}},"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/210139","number":210139,"mergeCommit":{"message":"[Navigation] Add stack monitoring to Elasticsearch sidebar (#210139)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"9dc67bfd8836e8d3a2f0480d997b11d9e7e9106f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
3af4fe9a68
|
[8.18] [Navigation] Add stack monitoring to Security sidebar (#210203) (#211128)
# Backport This will backport the following commits from `main` to `8.18`: - [[Navigation] Add stack monitoring to Security sidebar (#210203)](https://github.com/elastic/kibana/pull/210203) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T14:28:17Z","message":"[Navigation] Add stack monitoring to Security sidebar (#210203)\n\n## Summary\r\nThis PR adds Stack Monitoring to the side navigation.\r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"96381335e41d177f9851cc66eb9c5f7ec7d19d99","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Navigation] Add stack monitoring to Security sidebar","number":210203,"url":"https://github.com/elastic/kibana/pull/210203","mergeCommit":{"message":"[Navigation] Add stack monitoring to Security sidebar (#210203)\n\n## Summary\r\nThis PR adds Stack Monitoring to the side navigation.\r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"96381335e41d177f9851cc66eb9c5f7ec7d19d99"}},"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/210203","number":210203,"mergeCommit":{"message":"[Navigation] Add stack monitoring to Security sidebar (#210203)\n\n## Summary\r\nThis PR adds Stack Monitoring to the side navigation.\r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"96381335e41d177f9851cc66eb9c5f7ec7d19d99"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
3c729096e4
|
[8.18] [Navigation] Add stack monitoring to Observability sidebar (#210140) (#211133)
# Backport This will backport the following commits from `main` to `8.18`: - [[Navigation] Add stack monitoring to Observability sidebar (#210140)](https://github.com/elastic/kibana/pull/210140) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Krzysztof Kowalczyk","email":"krzysztof.kowalczyk@elastic.co"},"sourceCommit":{"committedDate":"2025-02-10T14:29:27Z","message":"[Navigation] Add stack monitoring to Observability sidebar (#210140)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"72265c026b875dd6dcefb07481784afd19f9347d","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Navigation] Add stack monitoring to Observability sidebar","number":210140,"url":"https://github.com/elastic/kibana/pull/210140","mergeCommit":{"message":"[Navigation] Add stack monitoring to Observability sidebar (#210140)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"72265c026b875dd6dcefb07481784afd19f9347d"}},"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/210140","number":210140,"mergeCommit":{"message":"[Navigation] Add stack monitoring to Observability sidebar (#210140)\n\n## Summary\r\n\r\nThis PR adds `Stack Monitoring` to the side navigation. \r\nAddresses: https://github.com/elastic/kibana-team/issues/1312\r\n\r\n","sha":"72265c026b875dd6dcefb07481784afd19f9347d"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Krzysztof Kowalczyk <krzysztof.kowalczyk@elastic.co> |
||
|
Kibana Machine
|
d2a5735822
|
[8.18] [Inference] Updating link text for model_id (#211087) (#211110)
# Backport This will backport the following commits from `main` to `8.18`: - [[Inference] Updating link text for model_id (#211087)](https://github.com/elastic/kibana/pull/211087) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Samiul Monir","email":"150824886+Samiul-TheSoccerFan@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T22:05:42Z","message":"[Inference] Updating link text for model_id (#211087)\n\n## Summary\r\n\r\nUpdating link text for `model_field` field to have `Learn more.` when\r\nthe provider is Elasticsearch.\r\n\r\n### screenshots:\r\n\r\n#### Elasticsearch provider\r\n\r\n\r\n#### Other providers\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"84fdbcba62206dd010086ae1ec590d6d0f5d16e5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Inference] Updating link text for model_id","number":211087,"url":"https://github.com/elastic/kibana/pull/211087","mergeCommit":{"message":"[Inference] Updating link text for model_id (#211087)\n\n## Summary\r\n\r\nUpdating link text for `model_field` field to have `Learn more.` when\r\nthe provider is Elasticsearch.\r\n\r\n### screenshots:\r\n\r\n#### Elasticsearch provider\r\n\r\n\r\n#### Other providers\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"84fdbcba62206dd010086ae1ec590d6d0f5d16e5"}},"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/211087","number":211087,"mergeCommit":{"message":"[Inference] Updating link text for model_id (#211087)\n\n## Summary\r\n\r\nUpdating link text for `model_field` field to have `Learn more.` when\r\nthe provider is Elasticsearch.\r\n\r\n### screenshots:\r\n\r\n#### Elasticsearch provider\r\n\r\n\r\n#### Other providers\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"84fdbcba62206dd010086ae1ec590d6d0f5d16e5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Samiul Monir <150824886+Samiul-TheSoccerFan@users.noreply.github.com> |
||
seanrathier
|
fbd05120da
|
[8.18] [Cloud Security] fix setupTechnology GCP credential type swapping (#210668) (#211089)
# Backport This will backport the following commits from `main` to `8.18`: - [[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)](https://github.com/elastic/kibana/pull/210668) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-02-13T19:06:37Z","message":"[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)","sha":"4fe72b62b114d9b12f581ac4938e133eb869529f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Cloud Security","backport:prev-minor","v9.1.0"],"title":"[Cloud Security] fix setupTechnology GCP credential type swapping","number":210668,"url":"https://github.com/elastic/kibana/pull/210668","mergeCommit":{"message":"[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)","sha":"4fe72b62b114d9b12f581ac4938e133eb869529f"}},"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/210668","number":210668,"mergeCommit":{"message":"[Cloud Security] fix setupTechnology GCP credential type swapping (#210668)","sha":"4fe72b62b114d9b12f581ac4938e133eb869529f"}},{"url":"https://github.com/elastic/kibana/pull/211082","number":211082,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4d64ea4130
|
[8.18] [Links] Fix link settings not persisting (#211041) (#211103)
# Backport This will backport the following commits from `main` to `8.18`: - [[Links] Fix link settings not persisting (#211041)](https://github.com/elastic/kibana/pull/211041) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Hannah Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T21:03:31Z","message":"[Links] Fix link settings not persisting (#211041)\n\nCloses https://github.com/elastic/kibana/issues/211022\r\n\r\n## Summary\r\n\r\nThis PR fixes a bug with persisting Link options where, because we\r\nweren't providing the \"initial\" state to the options editor, it was\r\nalways starting with the default state - therefore, editing something\r\n**other** than the options would reset the link options back to the\r\ndefault.\r\n\r\nI tested this in `8.14` and the bug was present there, too - based on\r\n[the file history / git\r\nblame](https://github.com/elastic/kibana/blame/main/src/platform/plugins/private/links/public/components/editor/link_editor.tsx#L60),\r\nthis bug has been around from the very beginning 🙈\r\n\r\n**Before:**\r\n\r\n\r\n |
||
|
Kibana Machine
|
51b5251f7b
|
[8.18] [Security Solution][Network details] add ability to show full network flyout from preview (#211065) (#211099)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][Network details] add ability to show full network flyout from preview (#211065)](https://github.com/elastic/kibana/pull/211065) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Philippe Oberti","email":"philippe.oberti@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T20:54:34Z","message":"[Security Solution][Network details] add ability to show full network flyout from preview (#211065)\n\n## Summary\r\n\r\nThis PR is a follow up of [this\r\nPR](https://github.com/elastic/kibana/pull/187870) that replaced the old\r\nnetwork/ip flyout with a new panel for the expandable flyout. Since then\r\nwe improved the UI or preview and added the ability to jump to a full\r\nflyout from its preview.\r\n\r\nThis PR fixes the issues where users could not navigate to the full\r\ndetails network/ip flyout from a preview. This functionality already\r\nexists for the alert, event, host and user flyouts. The PR adds a new\r\nfooter to the network/ip flyout - only shown in preview mode - that\r\nallows users to navigate to the full detail network/ip flyout.\r\n\r\n| Old behavior | New behavior |\r\n| ------------- | ------------- |\r\n| \r\n| \r\n|\r\n\r\nThe user has the ability to navigate to the full detail flyout:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4c809e5d-0b59-4498-9966-0133d139233b\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"96b4f8442e29f3e2aca919e9552c479ea0811393","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:Investigations","backport:version","v8.18.0","v9.1.0"],"title":"[Security Solution][Network details] add ability to show full network flyout from preview","number":211065,"url":"https://github.com/elastic/kibana/pull/211065","mergeCommit":{"message":"[Security Solution][Network details] add ability to show full network flyout from preview (#211065)\n\n## Summary\r\n\r\nThis PR is a follow up of [this\r\nPR](https://github.com/elastic/kibana/pull/187870) that replaced the old\r\nnetwork/ip flyout with a new panel for the expandable flyout. Since then\r\nwe improved the UI or preview and added the ability to jump to a full\r\nflyout from its preview.\r\n\r\nThis PR fixes the issues where users could not navigate to the full\r\ndetails network/ip flyout from a preview. This functionality already\r\nexists for the alert, event, host and user flyouts. The PR adds a new\r\nfooter to the network/ip flyout - only shown in preview mode - that\r\nallows users to navigate to the full detail network/ip flyout.\r\n\r\n| Old behavior | New behavior |\r\n| ------------- | ------------- |\r\n| \r\n| \r\n|\r\n\r\nThe user has the ability to navigate to the full detail flyout:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4c809e5d-0b59-4498-9966-0133d139233b\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"96b4f8442e29f3e2aca919e9552c479ea0811393"}},"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/211065","number":211065,"mergeCommit":{"message":"[Security Solution][Network details] add ability to show full network flyout from preview (#211065)\n\n## Summary\r\n\r\nThis PR is a follow up of [this\r\nPR](https://github.com/elastic/kibana/pull/187870) that replaced the old\r\nnetwork/ip flyout with a new panel for the expandable flyout. Since then\r\nwe improved the UI or preview and added the ability to jump to a full\r\nflyout from its preview.\r\n\r\nThis PR fixes the issues where users could not navigate to the full\r\ndetails network/ip flyout from a preview. This functionality already\r\nexists for the alert, event, host and user flyouts. The PR adds a new\r\nfooter to the network/ip flyout - only shown in preview mode - that\r\nallows users to navigate to the full detail network/ip flyout.\r\n\r\n| Old behavior | New behavior |\r\n| ------------- | ------------- |\r\n| \r\n| \r\n|\r\n\r\nThe user has the ability to navigate to the full detail flyout:\r\n\r\n\r\nhttps://github.com/user-attachments/assets/4c809e5d-0b59-4498-9966-0133d139233b\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios","sha":"96b4f8442e29f3e2aca919e9552c479ea0811393"}}]}] BACKPORT--> Co-authored-by: Philippe Oberti <philippe.oberti@elastic.co> |
||
|
Kibana Machine
|
13b3983116
|
[8.18] [Rules migration][Integration test] Create migration API (#11232) (#210999) (#211083)
# Backport This will backport the following commits from `main` to `8.18`: - [[Rules migration][Integration test] Create migration API (#11232) (#210999)](https://github.com/elastic/kibana/pull/210999) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T19:20:06Z","message":"[Rules migration][Integration test] Create migration API (#11232) (#210999)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations CREATE API (route:\r\n`/internal/siem_migrations/rules/{migration_id?}`) integration test:\r\n* Create migration with provided ID\r\n* Create migration without provided ID\r\n* Create migration with rules that have resources\r\n* Error handling (\"no content\") when no rules provided\r\n\r\nAlso, as part of this PR, I addressed this comment to my previous\r\nchanges\r\nhttps://github.com/elastic/kibana/pull/210867#discussion_r1954344990","sha":"44fdf81bbec5c053ebccfbdbb062d39de0d7358c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Rules migration][Integration test] Create migration API (#11232)","number":210999,"url":"https://github.com/elastic/kibana/pull/210999","mergeCommit":{"message":"[Rules migration][Integration test] Create migration API (#11232) (#210999)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations CREATE API (route:\r\n`/internal/siem_migrations/rules/{migration_id?}`) integration test:\r\n* Create migration with provided ID\r\n* Create migration without provided ID\r\n* Create migration with rules that have resources\r\n* Error handling (\"no content\") when no rules provided\r\n\r\nAlso, as part of this PR, I addressed this comment to my previous\r\nchanges\r\nhttps://github.com/elastic/kibana/pull/210867#discussion_r1954344990","sha":"44fdf81bbec5c053ebccfbdbb062d39de0d7358c"}},"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/210999","number":210999,"mergeCommit":{"message":"[Rules migration][Integration test] Create migration API (#11232) (#210999)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nPart of https://github.com/elastic/security-team/issues/11232\r\n\r\nThis PR covers SIEM Migrations CREATE API (route:\r\n`/internal/siem_migrations/rules/{migration_id?}`) integration test:\r\n* Create migration with provided ID\r\n* Create migration without provided ID\r\n* Create migration with rules that have resources\r\n* Error handling (\"no content\") when no rules provided\r\n\r\nAlso, as part of this PR, I addressed this comment to my previous\r\nchanges\r\nhttps://github.com/elastic/kibana/pull/210867#discussion_r1954344990","sha":"44fdf81bbec5c053ebccfbdbb062d39de0d7358c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
f34b73a969
|
[8.18] [SecuritySolution] Network page crashes after interacting with map (#206773) (#211078)
# Backport This will backport the following commits from `main` to `8.18`: - [[SecuritySolution] Network page crashes after interacting with map (#206773)](https://github.com/elastic/kibana/pull/206773) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Angela Chuang","email":"6295984+angorayc@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T18:57:07Z","message":"[SecuritySolution] Network page crashes after interacting with map (#206773)\n\n## Summary\r\n\r\nIssues and steps to reproduce:\r\n |
||
Mark J. Hoy
|
6953738701
|
[8.18] [8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688) (#211077)
# Backport This will backport the following commits from `8.x` to `8.18`: - [[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688)](https://github.com/elastic/kibana/pull/210688) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Mark J. Hoy","email":"mark.hoy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T18:21:48Z","message":"[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688)\n\n## Summary\r\n\r\nAdds deprecations for the Kibana Upgrade Assistant if Enterprise Search\r\nindices from pre version 8.x are found. These indices are not compatible\r\nto upgrade to 9.x, so they must be set to read only or deleted.\r\n\r\nThe deprecations call out the specific indices, and offers a \"quick\r\nresolve\" button to set the affected indices to read only.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"271e40e9753417bb083748017aa7fa528fc34510","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Feature:Upgrade Assistant","Team:EnterpriseSearch","v8.18.0","v8.19.0","backport:8.18"],"title":"[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations","number":210688,"url":"https://github.com/elastic/kibana/pull/210688","mergeCommit":{"message":"[8.x] Add Pre-8.x Enterprise Search Index Incompatibility Deprecations (#210688)\n\n## Summary\r\n\r\nAdds deprecations for the Kibana Upgrade Assistant if Enterprise Search\r\nindices from pre version 8.x are found. These indices are not compatible\r\nto upgrade to 9.x, so they must be set to read only or deleted.\r\n\r\nThe deprecations call out the specific indices, and offers a \"quick\r\nresolve\" button to set the affected indices to read only.\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [x] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"271e40e9753417bb083748017aa7fa528fc34510"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
d02a02dff0
|
[8.18] [Security Solution][SIEM migrations] Use cloud onboarding config (#210921) (#211074)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)](https://github.com/elastic/kibana/pull/210921) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T18:28:22Z","message":"[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)\n\n## Summary\r\n\r\nThis PR retrieves the Cloud onboarding data to pre-select the SIEM\r\nmigration topic in the onboarding hub when necessary.\r\nThe Cloud logic was implemented\r\n[here](https://github.com/elastic/kibana/pull/204129)\r\n\r\n<img width=\"1364\" alt=\"Captura de pantalla 2025-02-13 a les 11 50 31\"\r\nsrc=\"https://github.com/user-attachments/assets/28707314-da9b-439a-baa9-f6fb53c170fa\"\r\n/>","sha":"789986ce4846f8a32e40c00d52268a1beaa6231e","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] Use cloud onboarding config","number":210921,"url":"https://github.com/elastic/kibana/pull/210921","mergeCommit":{"message":"[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)\n\n## Summary\r\n\r\nThis PR retrieves the Cloud onboarding data to pre-select the SIEM\r\nmigration topic in the onboarding hub when necessary.\r\nThe Cloud logic was implemented\r\n[here](https://github.com/elastic/kibana/pull/204129)\r\n\r\n<img width=\"1364\" alt=\"Captura de pantalla 2025-02-13 a les 11 50 31\"\r\nsrc=\"https://github.com/user-attachments/assets/28707314-da9b-439a-baa9-f6fb53c170fa\"\r\n/>","sha":"789986ce4846f8a32e40c00d52268a1beaa6231e"}},"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/210921","number":210921,"mergeCommit":{"message":"[Security Solution][SIEM migrations] Use cloud onboarding config (#210921)\n\n## Summary\r\n\r\nThis PR retrieves the Cloud onboarding data to pre-select the SIEM\r\nmigration topic in the onboarding hub when necessary.\r\nThe Cloud logic was implemented\r\n[here](https://github.com/elastic/kibana/pull/204129)\r\n\r\n<img width=\"1364\" alt=\"Captura de pantalla 2025-02-13 a les 11 50 31\"\r\nsrc=\"https://github.com/user-attachments/assets/28707314-da9b-439a-baa9-f6fb53c170fa\"\r\n/>","sha":"789986ce4846f8a32e40c00d52268a1beaa6231e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> |
||
|
Kibana Machine
|
78bf483e60
|
[8.18] [Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922) (#211008)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)](https://github.com/elastic/kibana/pull/210922) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T13:37:37Z","message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","review","release_note:fix","v9.0.0","sdh-linked","Team:Detection Engine","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal","number":210922,"url":"https://github.com/elastic/kibana/pull/210922","mergeCommit":{"message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f"}},"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/210922","number":210922,"mergeCommit":{"message":"[Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922)\n\n## Summary\n\nDisables sorting ip range values in a value list until this bug is\nfixed in elasticsearch.\n\nrelated: https://github.com/elastic/elasticsearch/issues/122358","sha":"18ef744a9c3bf5b5eff585cbddcc4cb34eab9b8f"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
Kibana Machine
|
469d8d68c8
|
[8.18] [Security Solution] Update entity store copies (#210991) (#211032)
# Backport This will backport the following commits from `main` to `8.18`: - [[Security Solution] Update entity store copies (#210991)](https://github.com/elastic/kibana/pull/210991) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T15:42:09Z","message":"[Security Solution] Update entity store copies (#210991)\n\n## Summary\n\n* Update `Initializing entity store` to `Configuring Entity Store`\n* Update `Your entity store is currently empty. Add information...` to\n`Add information...`\n\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/f64bf5de-bb42-4675-a816-6202dca4bb80\"/>\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/cf1ea4c0-416d-408a-a166-b85c3e57135a\"/>","sha":"fe96fe2dbc040e8ab2bcc10995d71f9bc29571cb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team: SecuritySolution","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Update entity store copies","number":210991,"url":"https://github.com/elastic/kibana/pull/210991","mergeCommit":{"message":"[Security Solution] Update entity store copies (#210991)\n\n## Summary\n\n* Update `Initializing entity store` to `Configuring Entity Store`\n* Update `Your entity store is currently empty. Add information...` to\n`Add information...`\n\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/f64bf5de-bb42-4675-a816-6202dca4bb80\"/>\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/cf1ea4c0-416d-408a-a166-b85c3e57135a\"/>","sha":"fe96fe2dbc040e8ab2bcc10995d71f9bc29571cb"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x"],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210991","number":210991,"mergeCommit":{"message":"[Security Solution] Update entity store copies (#210991)\n\n## Summary\n\n* Update `Initializing entity store` to `Configuring Entity Store`\n* Update `Your entity store is currently empty. Add information...` to\n`Add information...`\n\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/f64bf5de-bb42-4675-a816-6202dca4bb80\"/>\n<img width=\"400\"\nsrc=\"https://github.com/user-attachments/assets/cf1ea4c0-416d-408a-a166-b85c3e57135a\"/>","sha":"fe96fe2dbc040e8ab2bcc10995d71f9bc29571cb"}},{"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> |