mirror of
https://github.com/elastic/kibana.git
synced 2025-04-20 07:48:52 -04:00
81046 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
0ec6573aa8
|
[8.17] [Data View Field] Fix popularity score bugs (#211201) (#212614)
# Backport This will backport the following commits from `main` to `8.17`: - [[Data View Field] Fix popularity score bugs (#211201)](https://github.com/elastic/kibana/pull/211201) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2025-02-27T10:34:22Z","message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\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":"97260415030a3b816b3a8507c51c4a5184ff25df","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Feature:Data Views","v9.0.0","Team:DataDiscovery","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Data View Field] Fix popularity score bugs ","number":211201,"url":"https://github.com/elastic/kibana/pull/211201","mergeCommit":{"message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\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":"97260415030a3b816b3a8507c51c4a5184ff25df"}},"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/211201","number":211201,"mergeCommit":{"message":"[Data View Field] Fix popularity score bugs (#211201)\n\n- Fixes https://github.com/elastic/kibana/issues/211109\n\n## Summary\n\nThis PR fixes a number of bugs in fields popularity logic:\n- [x] If field popularity was customized via UI form, the value will be\nsaved now as a number instead of a string\n- [x] Same for runtime fields in another part of the code\n- [x] Since the data was polluted with string values, this PR makes sure\nthat the incrementing would still work and the result would be converted\nto number.\n- [x] If user opened the field flyout, when selected/deselected fields\nas columns in the table, then opened the field flyout again, the data\nshown as Popularity was outdated. Now it should be fixed.\n- [x] Prevents reseting of Popularity scores in other fields.\n- [x] Functional tests in\n`test/functional/apps/discover/group6/_sidebar.ts` and\n`test/functional/apps/management/data_views/_index_pattern_popularity.ts`.\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":"97260415030a3b816b3a8507c51c4a5184ff25df"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co> |
||
Charlotte Alexandra Wilson
|
f3192d7aed
|
[8.17] [refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441) (#212561)
# Backport This will backport the following commits from `main` to `8.17`: - [[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)](https://github.com/elastic/kibana/pull/212441) <!--- Backport version: 9.6.6 --> ### 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-26T13:29:21Z","message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["refactoring","release_note:skip","v9.0.0","Theme: entity_analytics","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel ","number":212441,"url":"https://github.com/elastic/kibana/pull/212441","mergeCommit":{"message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212554","number":212554,"state":"OPEN"},{"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,"url":"https://github.com/elastic/kibana/pull/212519","number":212519,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212441","number":212441,"mergeCommit":{"message":"[refactoring] Distinguish User Controls from Risk Engine in DashboardEnablementPanel (#212441)\n\n## Summary\nThis PR refactors naming and logic in EntityStoreEnablementModal to\nimprove readability and better distinguish between:\n1. Feature enablement state – Whether Risk Score or Entity Store is\nactually enabled.\n2. User-selected state – Whether the user has checked the corresponding\ntoggle.\n\n#### Changes\n\n- Renamed disabled → canToggle to clearly represent UI interaction.\n- Renamed enablements → userSelectedEnablements to reflect user-selected\ntoggle states, not feature enablement.\n- Refactored shouldAllowEnablement logic for clarity and correctness:\n- If riskScore is enabled, return whether the user has enabled\nentityStore.\n- If entityStore is enabled, return whether the user has enabled\nriskScore.\n - Otherwise, return true if either toggle is selected.\n- Updated corresponding tests to reflect naming and logic changes.\n\n## Testing/Validation\nManually tested the toggling behaviour still works as before and modal\nstill shows warning, and disables the \"enable\" button when there are no\navailable options selected.\n\n### Validation Video\n\n\nhttps://github.com/user-attachments/assets/0f2a3f59-e2a0-4c8b-a350-70a9573a8566","sha":"874cee2c575efe75ede0702ac243855abe008a69"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212556","number":212556,"state":"OPEN"}]}] BACKPORT--> |
||
Philippe Oberti
|
b86ad4dac3
|
[8.17] [Security Solution] Fixed Table height row rendering - Event Rendered View (#212130) (#212597)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)](https://github.com/elastic/kibana/pull/212130) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jatin Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T22:36:50Z","message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\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- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c","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","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Fixed Table height row rendering - Event Rendered View","number":212130,"url":"https://github.com/elastic/kibana/pull/212130","mergeCommit":{"message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\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- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212596","number":212596,"state":"OPEN"},{"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/212130","number":212130,"mergeCommit":{"message":"[Security Solution] Fixed Table height row rendering - Event Rendered View (#212130)\n\n## Summary\n\nToday Alert table has a height of 600px if the number of items it\ndisplays exceeds 20. If not, it has a height of `auto` which means it\nadjust the table height according to the number of rows displayed.\n\nThis height `auto` surfaces an issue with EuiDataGrid where it is not\nable to calculate the height of the displayed rows. This results in\narbitrary height everytime the number of rows < 20.\n\n\n## Solution\n\nWe are working with EUI Team to permanently fix the issue. But as a\nworkaround, we are setting up a fixed height of EuiDataGrid to `600px`\nirrespective of the number of rows that are visible on the screen. This\nwould sometime lead of extra flush space visible as can be seen in below\ndemo.\n\nBut it ensures that user is never in an unusable state. Below is the\nsummary of changes applied\n\n- Fixed height of `600px` in case of Event Rendered View\n\nBelow `Before` and `After` Sections show the demo\n\n### Before\n\n\nhttps://github.com/user-attachments/assets/6efd70b1-a33f-4c98-bd8f-82f57e9cd0cd\n\n### After\n\n\n\nhttps://github.com/user-attachments/assets/8da31611-12ff-4609-bafb-4b0f53398407\n\n\n\n\n\n\n\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- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Philippe Oberti <philippe.oberti@elastic.co>","sha":"88ab8b672f71033c0f5683464de52dd8fe89863c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212594","number":212594,"state":"OPEN"}]}] BACKPORT--> Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co> |
||
|
Kibana Machine
|
86fb404db7
|
[8.17] [Fleet] Fix API key insertion into standalone agent policy (#212440) (#212578)
# Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] Fix API key insertion into standalone agent policy (#212440)](https://github.com/elastic/kibana/pull/212440) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Satvikkaushal","email":"39619179+Satvikkaushal@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-26T19:02:11Z","message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","💝community","Team:Fleet","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[Fleet] Fix API key insertion into standalone agent policy","number":212440,"url":"https://github.com/elastic/kibana/pull/212440","mergeCommit":{"message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49"}},"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/212440","number":212440,"mergeCommit":{"message":"[Fleet] Fix API key insertion into standalone agent policy (#212440)\n\n## Summary\n\nResolves-#210161\n\nReplaced `RegExp(/\\'\\${API_KEY}\\'/, 'g');` with `RegExp(/\\$\\{API_KEY}/,\n'g');` to correctly match the ${API_KEY} pattern without requiring\nsingle quotes. This ensures proper substitution and avoids unintended\nmismatches.\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"f49e6adbb58539ea844b9c276002f4114e0b9c49"}}]}] BACKPORT--> Co-authored-by: Satvikkaushal <39619179+Satvikkaushal@users.noreply.github.com> |
||
Giorgos Bamparopoulos
|
899a7eb5da
|
[8.17] [Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694) (#212388)
# Backport This will backport the following commits from `main` to `8.17`: - [[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)](https://github.com/elastic/kibana/pull/205694) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Giorgos Bamparopoulos","email":"georgios.bamparopoulos@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T15:41:28Z","message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","ci:project-deploy-observability","backport:version","v8.18.0"],"title":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow","number":205694,"url":"https://github.com/elastic/kibana/pull/205694","mergeCommit":{"message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205694","number":205694,"mergeCommit":{"message":"[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)\n\n## 📓 Summary\r\n🛑 **Don't merge before the 8.17.1 release as the file doesn't exist in\r\n[v8.17.0](https://github.com/elastic/elastic-agent/tree/v8.17.0/deploy/helm/edot-collector/kube-stack),\r\nas the [backport PR](https://github.com/elastic/elastic-agent/pull/6267)\r\nwas merged the day of the release.**\r\n\r\nUpdates the URL of the `values.yml` file for the OTel onboarding\r\nKubernetes flow using the relevant release tag.\r\n\r\nThe file is available in the `elastic-agent` repo under the\r\n[deploy/helm/edot-collector/kube-stack/values.yaml](https://github.com/elastic/elastic-agent/blob/v8.16.2/deploy/helm/edot-collector/kube-stack/values.yaml)\r\npath.\r\n\r\n### 8.16 branch\r\n<img width=\"1156\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/b1e3848b-7d1a-4d50-9968-d124859a054f\"\r\n/>\r\n\r\n### main branch\r\n<img width=\"1152\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/e0b33a08-405d-475d-af48-0bbc93abfa27\"\r\n/>\r\n\r\nCloses https://github.com/elastic/kibana/issues/197644\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8580f4f4f169bbf23cabdb970e20ed1482dc003b"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/207866","number":207866,"state":"MERGED","mergeCommit":{"sha":"0d22f08c4bd7da291ab6037980512be9b57ce5d7","message":"[8.x] [Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694) (#207866)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Observability Onboarding] Update values.yml file URL for the OTel\nK8s flow (#205694)](https://github.com/elastic/kibana/pull/205694)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co>"}}]}] BACKPORT--> |
||
Ievgen Sorokopud
|
f65b7a1d66
|
[8.17] [Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122) (#212505)
# Backport This will backport the following commits from `main` to `8.17`: - [[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)](https://github.com/elastic/kibana/pull/212122) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T11:03:09Z","message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23","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:Security Generative AI","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783)","number":212122,"url":"https://github.com/elastic/kibana/pull/212122","mergeCommit":{"message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212501","number":212501,"state":"OPEN"},{"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,"url":"https://github.com/elastic/kibana/pull/212500","number":212500,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212122","number":212122,"mergeCommit":{"message":"[Bug][Assistant API] - chat/complete endpoint is not persisting the model response to the chosen conversation ID (#11783) (#212122)\n\n## Summary\n\nBUG: https://github.com/elastic/security-team/issues/11783\n\nThis PR fixes the behaviour of the\n`/api/security_ai_assistant/chat/complete` route where the `persist`\nflag:\n1. when set to `true` does not append the assistant reply to existing\nconversation\n2. when set to `false` appends user message to existing conversation\n\n### Expected behaviour\n\n\n[Details](https://github.com/elastic/security-team/issues/11783#issuecomment-2674565194).\n\n1. `conversationId == undefined && persist == false`: no new\nconversations and nothing persisted\n2. `conversationId == undefined && persist == true`: new conversations\nis created and both user message and assistant reply appended to the new\nconversation\n3. `conversationId == 'existing-id' && persist == false`: nothing\nappended to the existing conversation\n4. `conversationId == 'existing-id' && persist == true`: both user\nmessage and assistant reply appended to the existing conversation\n\n### Testing\n\n* Use this `curl` command (with replace `connectorId` and\n`conversationId`) to test the endpoint.\n\n```\ncurl --location 'http://localhost:5601/api/security_ai_assistant/chat/complete' \\\n--header 'kbn-xsrf: true' \\\n--header 'Content-Type: application/json' \\\n--data '{\n \"connectorId\": \"{{my-gpt4o-ai}}\",\n \"conversationId\": \"{{existing-conversation-id | undefined}}\",\n \"isStream\": false,\n \"messages\": [\n {\n \"content\": \"Follow up\",\n \"role\": \"user\"\n }\n ],\n \"persist\": true\n}'\n```\n\n* To retrieve the conversation ID:\n(/api/security_ai_assistant/current_user/conversations/_find)\n* `conversationId` can be either existing conversation id or `undefined`","sha":"a2b2e81b5b74ffc56302953d186a36984b3b1c23"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
4454a54133
|
[8.17] [Docs] Add missing setting in advanced options (#212528) (#212538)
# Backport This will backport the following commits from `main` to `8.17`: - [[Docs] Add missing setting in advanced options (#212528)](https://github.com/elastic/kibana/pull/212528) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"florent-leborgne","email":"florent.leborgne@elastic.co"},"sourceCommit":{"committedDate":"2025-02-26T15:23:13Z","message":"[Docs] Add missing setting in advanced options (#212528)\n\nThis PR reproduces https://github.com/elastic/kibana/pull/212514 to make\nit simpler to backport down to the 8.13 version.\n\nI'll port the change to the new location for 9.0+ docs as well.","sha":"76ae900e1abb468a0015a62f90667c3c0c357e52","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","docs","v8.13.0","v8.14.0","v8.15.0","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0","v8.19.0"],"title":"[Docs] Add missing setting in advanced options","number":212528,"url":"https://github.com/elastic/kibana/pull/212528","mergeCommit":{"message":"[Docs] Add missing setting in advanced options (#212528)\n\nThis PR reproduces https://github.com/elastic/kibana/pull/212514 to make\nit simpler to backport down to the 8.13 version.\n\nI'll port the change to the new location for 9.0+ docs as well.","sha":"76ae900e1abb468a0015a62f90667c3c0c357e52"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.13","8.14","8.15","8.16","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.13","label":"v8.13.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.14","label":"v8.14.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.15","label":"v8.15.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.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/212528","number":212528,"mergeCommit":{"message":"[Docs] Add missing setting in advanced options (#212528)\n\nThis PR reproduces https://github.com/elastic/kibana/pull/212514 to make\nit simpler to backport down to the 8.13 version.\n\nI'll port the change to the new location for 9.0+ docs as well.","sha":"76ae900e1abb468a0015a62f90667c3c0c357e52"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: florent-leborgne <florent.leborgne@elastic.co> |
||
José Luis González
|
1e06975863
|
[8.17] [Search][Connectors] Fixing custom connector icon rendering (#212225) (#212484)
# Backport This will backport the following commits from `main` to `8.17`: - [[Search][Connectors] Fixing custom connector icon rendering (#212225)](https://github.com/elastic/kibana/pull/212225) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"José Luis González","email":"joseluisgj@gmail.com"},"sourceCommit":{"committedDate":"2025-02-25T14:49:33Z","message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"965cbbabc0d59fa3419d0238b4eb460ab930d2db","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-major","backport:version","v9.1.0"],"title":"[Search][Connectors] Fixing custom connector icon rendering","number":212225,"url":"https://github.com/elastic/kibana/pull/212225","mergeCommit":{"message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"965cbbabc0d59fa3419d0238b4eb460ab930d2db"}},"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/212386","number":212386,"state":"MERGED","mergeCommit":{"sha":"e6799ea001e2ef5178294d3e7dc570e7861d19c7","message":"[9.0] [Search][Connectors] Fixing custom connector icon rendering (#212225) (#212386)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Search][Connectors] Fixing custom connector icon rendering\n(#212225)](https://github.com/elastic/kibana/pull/212225)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: José Luis González <joseluisgj@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212225","number":212225,"mergeCommit":{"message":"[Search][Connectors] Fixing custom connector icon rendering (#212225)\n\n## Summary\r\n\r\nFixing areas where we were not rendering well the custom connector icon\r\nas described in this ticket:\r\nhttps://github.com/elastic/search-team/issues/9362\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [ ]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] If a plugin configuration key changed, check if it needs to be\r\nallowlisted in the cloud and added to the [docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n- [ ] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [ ] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_note:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n### Identify risks\r\n\r\nDoes this PR introduce any risks? For example, consider risks like hard\r\nto test bugs, performance regression, potential of data loss.\r\n\r\nDescribe the risk, its severity, and mitigation for each identified\r\nrisk. Invite stakeholders and evaluate how to proceed before merging.\r\n\r\n- [ ] [See some risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\r\n- [ ] ...","sha":"965cbbabc0d59fa3419d0238b4eb460ab930d2db"}}]}] BACKPORT--> |
||
Abhishek Bhatia
|
01a430a06c
|
[8.17] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#212378)
# Backport This will backport the following commits from `main` to `8.17`: - [[Entity Analytics] API changes for right placement of deleting the old component template (#199734)](https://github.com/elastic/kibana/pull/199734) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2024-11-18T15:07:13Z","message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3","branchLabelMapping":{"^v9.0.0$":"main","^v8.17.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","QA:Validated","Team:Entity Analytics","backport:version","v8.17.0","v8.16.1","v8.18.0"],"title":"[Entity Analytics] API changes for right placement of deleting the old component template","number":199734,"url":"https://github.com/elastic/kibana/pull/199734","mergeCommit":{"message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3"}},"sourceBranch":"main","suggestedTargetBranches":["8.18"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/199734","number":199734,"mergeCommit":{"message":"[Entity Analytics] API changes for right placement of deleting the old component template (#199734)\n\n## Summary\r\n\r\n- Delete the old component template after the index template has\r\nreferenced to the new component template\r\n- Test cases for the same flow\r\n\r\n\r\n```JSON\r\n# Let's assume this is 8.15.3\r\n# Create the component template when Risk Score engine is initialised\r\n# Create the index template which references the created component template\r\n\r\nPUT /_component_template/.risk-score-mappings\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\n# The deployment is updated to 8.16\r\n# User tries to enable the Entity store which init's the Risk Score engine (again!!) \r\n# Fails, but creates the component template and cannot update the index template to reference the new component template due to the error\r\n\r\nPUT /_component_template/.risk-score-mappings-default\r\n{\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_shards\": 1\r\n },\r\n \"mappings\": {\r\n \"properties\": {\r\n \"timestamp\": {\r\n \"type\": \"date\"\r\n },\r\n \"user\": {\r\n \"properties\": {\r\n \"id\": {\r\n \"type\": \"keyword\"\r\n },\r\n \"name\": {\r\n \"type\": \"text\"\r\n }\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"version\": 1\r\n}\r\n\r\nGET /_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\r\n\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Fails \r\n\r\n# changed flow\r\nPUT /_index_template/.risk-score.risk-score-default-index-template\r\n{\r\n \"index_patterns\": [\".risk-score.risk-score-default-index-template\"],\r\n \"template\": {\r\n \"settings\": {\r\n \"number_of_replicas\": 1\r\n }\r\n },\r\n \"composed_of\": [\".risk-score-mappings-default\"],\r\n \"priority\": 100,\r\n \"version\": 1,\r\n \"_meta\": {\r\n \"description\": \"Index template for indices with the pattern my_index-*\"\r\n }\r\n}\r\n\r\nDELETE /_component_template/.risk-score-mappings\r\n\r\n# Succeeds\r\n\r\n#########\r\n```\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable to this PR.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for breaking API changes and was [labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\r\n- [ ] This will appear in the **Release Notes** and follow the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"771c139269ac0eac27274e0858be2fbcf87b31e3"}},{"branch":"8.x","label":"v8.17.0","branchLabelMappingKey":"^v8.17.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200673","number":200673,"state":"MERGED","mergeCommit":{"sha":"24cbc3ee37cca9610bb8848c7361deeb4dc63ac4","message":"[8.x] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#200673)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[Entity Analytics] API changes for right placement of deleting the\nold component template\n(#199734)](https://github.com/elastic/kibana/pull/199734)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Abhishek\nBhatia\",\"email\":\"117628830+abhishekbhatia1710@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-18T15:07:13Z\",\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"Team:Entity\nAnalytics\",\"backport:version\",\"v8.17.0\",\"v8.16.1\"],\"number\":199734,\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"number\":199734,\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},{\"branch\":\"8.x\",\"label\":\"v8.17.0\",\"labelRegex\":\"^v8.17.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.1\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"url\":\"https://github.com/elastic/kibana/pull/200591\",\"number\":200591,\"state\":\"MERGED\",\"mergeCommit\":{\"sha\":\"06999139d210464c236a3784c58b7e5dcbd64ce3\",\"message\":\"[8.16]\n[Entity Analytics] API changes for right placement of deleting the old\ncomponent template (#199734) (#200591)\\n\\n# Backport\\n\\nThis will\nbackport the following commits from `main` to `8.16`:\\n- [[Entity\nAnalytics] API changes for right placement of deleting the\\nold\ncomponent\ntemplate\\n(#199734)](https://github.com/elastic/kibana/pull/199734)\\n\\n<!---\nBackport version: 8.9.8 -->\\n\\n### Questions ?\\nPlease refer to the\n[Backport\ntool\\ndocumentation](https://github.com/sqren/backport)\\n\\n<!--BACKPORT\n[{\\\"author\\\":{\\\"name\\\":\\\"Abhishek\\nBhatia\\\",\\\"email\\\":\\\"117628830+abhishekbhatia1710@users.noreply.github.com\\\"},\\\"sourceCommit\\\":{\\\"committedDate\\\":\\\"2024-11-18T15:07:13Z\\\",\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\",\\\"branchLabelMapping\\\":{\\\"^v9.0.0$\\\":\\\"main\\\",\\\"^v8.17.0$\\\":\\\"8.x\\\",\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\":\\\"$1.$2\\\"}},\\\"sourcePullRequest\\\":{\\\"labels\\\":[\\\"bug\\\",\\\"release_note:fix\\\",\\\"v9.0.0\\\",\\\"Team:Entity\\nAnalytics\\\",\\\"backport:version\\\",\\\"v8.17.0\\\",\\\"v8.16.1\\\"],\\\"number\\\":199734,\\\"url\\\":\\\"https://github.com/elastic/kibana/pull/199734\\\",\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\"}},\\\"sourceBranch\\\":\\\"main\\\",\\\"suggestedTargetBranches\\\":[\\\"8.x\\\",\\\"8.16\\\"],\\\"targetPullRequestStates\\\":[{\\\"branch\\\":\\\"main\\\",\\\"label\\\":\\\"v9.0.0\\\",\\\"labelRegex\\\":\\\"^v9.0.0$\\\",\\\"isSourceBranch\\\":true,\\\"state\\\":\\\"MERGED\\\",\\\"url\\\":\\\"https://github.com/elastic/kibana/pull/199734\\\",\\\"number\\\":199734,\\\"mergeCommit\\\":{\\\"message\\\":\\\"[Entity\\nAnalytics]\nAPI changes for right placement of deleting the old component\\ntemplate\n(#199734)\\\\n\\\\n## Summary\\\\r\\\\n\\\\r\\\\n- Delete the old\ncomponent\\ntemplate after the index template has\\\\r\\\\nreferenced to the\nnew component\\ntemplate\\\\r\\\\n- Test cases for the same\nflow\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n```JSON\\\\r\\\\n# Let's\\nassume this is 8.15.3\\\\r\\\\n#\nCreate the component template when Risk Score\\nengine is\ninitialised\\\\r\\\\n# Create the index template which references\\nthe\ncreated component\ntemplate\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n \\\\\\\"mappings\\\\\\\":\\n{\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"date\\\\\\\"\\\\r\\\\n\\n},\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n \\\\\\\"properties\\\\\\\":\n{\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n\n},\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\": \\\\\\\"text\\\\\\\"\\\\r\\\\n\n}\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n \\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\": [\\\\\\\".risk-score-mappings\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\": 100,\\\\r\\\\n\\n\\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index template\\nfor indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n }\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\n# The\\ndeployment is\nupdated to 8.16\\\\r\\\\n# User tries to enable the Entity store\\nwhich\ninit's the Risk Score engine (again!!) \\\\r\\\\n# Fails, but creates\\nthe\ncomponent template and cannot update the index template to\nreference\\nthe new component template due to the\nerror\\\\r\\\\n\\\\r\\\\nPUT\\n/_component_template/.risk-score-mappings-default\\\\r\\\\n{\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_shards\\\\\\\": 1\\\\r\\\\n },\\\\r\\\\n\\n\\\\\\\"mappings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"timestamp\\\\\\\": {\\\\r\\\\n\n\\\\\\\"type\\\\\\\":\\n\\\\\\\"date\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"user\\\\\\\": {\\\\r\\\\n\n\\\\\\\"properties\\\\\\\": {\\\\r\\\\n \\\\\\\"id\\\\\\\": {\\\\r\\\\n\\n\\\\\\\"type\\\\\\\":\n\\\\\\\"keyword\\\\\\\"\\\\r\\\\n },\\\\r\\\\n \\\\\\\"name\\\\\\\": {\\\\r\\\\n \\\\\\\"type\\\\\\\":\n\\\\\\\"text\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n }\\\\r\\\\n },\\\\r\\\\n\n\\\\\\\"version\\\\\\\":\n1\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nGET\\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\\\r\\\\n\\\\r\\\\n\\\\r\\\\nDELETE\\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\nFails \\\\r\\\\n\\\\r\\\\n#\\nchanged\nflow\\\\r\\\\nPUT\\n/_index_template/.risk-score.risk-score-default-index-template\\\\r\\\\n{\\\\r\\\\n\\n\\\\\\\"index_patterns\\\\\\\":\\n[\\\\\\\".risk-score.risk-score-default-index-template\\\\\\\"],\\\\r\\\\n\n\\\\\\\"template\\\\\\\":\\n{\\\\r\\\\n \\\\\\\"settings\\\\\\\": {\\\\r\\\\n\n\\\\\\\"number_of_replicas\\\\\\\": 1\\\\r\\\\n }\\\\r\\\\n\n},\\\\r\\\\n\\n\\\\\\\"composed_of\\\\\\\":\n[\\\\\\\".risk-score-mappings-default\\\\\\\"],\\\\r\\\\n\n\\\\\\\"priority\\\\\\\":\\n100,\\\\r\\\\n \\\\\\\"version\\\\\\\": 1,\\\\r\\\\n \\\\\\\"_meta\\\\\\\":\n{\\\\r\\\\n \\\\\\\"description\\\\\\\": \\\\\\\"Index\\ntemplate for indices with the\npattern my_index-*\\\\\\\"\\\\r\\\\n\\n}\\\\r\\\\n}\\\\r\\\\n\\\\r\\\\nDELETE\n/_component_template/.risk-score-mappings\\\\r\\\\n\\\\r\\\\n#\\nSucceeds\\\\r\\\\n\\\\r\\\\n#########\\\\r\\\\n```\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nChecklist\\\\r\\\\n\\\\r\\\\nDelete\\nany items that are not applicable to this\nPR.\\\\r\\\\n\\\\r\\\\n- [ ] [Unit\nor\\nfunctional\\\\r\\\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\\\r\\\\nwere\\nupdated\nor added to match the most common scenarios\\\\r\\\\n- [ ]\n[Flaky\\nTest\\\\r\\\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\\nwas\\\\r\\\\nused\non any tests changed\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n\\\\r\\\\n###\nFor\\nmaintainers\\\\r\\\\n\\\\r\\\\n- [ ] This was checked for breaking API\nchanges\nand\\nwas\\n[labeled\\\\r\\\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\\\r\\\\n-\\n[\n] This will appear in the **Release Notes** and\nfollow\\nthe\\\\r\\\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\\",\\\"sha\\\":\\\"771c139269ac0eac27274e0858be2fbcf87b31e3\\\"}},{\\\"branch\\\":\\\"8.x\\\",\\\"label\\\":\\\"v8.17.0\\\",\\\"labelRegex\\\":\\\"^v8.17.0$\\\",\\\"isSourceBranch\\\":false,\\\"state\\\":\\\"NOT_CREATED\\\"},{\\\"branch\\\":\\\"8.16\\\",\\\"label\\\":\\\"v8.16.1\\\",\\\"labelRegex\\\":\\\"^v(\\\\\\\\d+).(\\\\\\\\d+).\\\\\\\\d+$\\\",\\\"isSourceBranch\\\":false,\\\"state\\\":\\\"NOT_CREATED\\\"}]}]\\nBACKPORT-->\"}}]}]\nBACKPORT-->\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>"}},{"branch":"8.16","label":"v8.16.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/200591","number":200591,"state":"MERGED","mergeCommit":{"sha":"06999139d210464c236a3784c58b7e5dcbd64ce3","message":"[8.16] [Entity Analytics] API changes for right placement of deleting the old component template (#199734) (#200591)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [[Entity Analytics] API changes for right placement of deleting the\nold component template\n(#199734)](https://github.com/elastic/kibana/pull/199734)\n\n<!--- Backport version: 8.9.8 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Abhishek\nBhatia\",\"email\":\"117628830+abhishekbhatia1710@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2024-11-18T15:07:13Z\",\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.17.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"bug\",\"release_note:fix\",\"v9.0.0\",\"Team:Entity\nAnalytics\",\"backport:version\",\"v8.17.0\",\"v8.16.1\"],\"number\":199734,\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.x\",\"8.16\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"labelRegex\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/199734\",\"number\":199734,\"mergeCommit\":{\"message\":\"[Entity\nAnalytics] API changes for right placement of deleting the old component\ntemplate (#199734)\\n\\n## Summary\\r\\n\\r\\n- Delete the old component\ntemplate after the index template has\\r\\nreferenced to the new component\ntemplate\\r\\n- Test cases for the same flow\\r\\n\\r\\n\\r\\n```JSON\\r\\n# Let's\nassume this is 8.15.3\\r\\n# Create the component template when Risk Score\nengine is initialised\\r\\n# Create the index template which references\nthe created component template\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings\\r\\n{\\r\\n \\\"template\\\": {\\r\\n\n\\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n \\\"mappings\\\":\n{\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\": \\\"date\\\"\\r\\n\n},\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n \\\"type\\\":\n\\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n }\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings\\\"],\\r\\n \\\"priority\\\": 100,\\r\\n\n\\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index template\nfor indices with the pattern my_index-*\\\"\\r\\n }\\r\\n}\\r\\n\\r\\n# The\ndeployment is updated to 8.16\\r\\n# User tries to enable the Entity store\nwhich init's the Risk Score engine (again!!) \\r\\n# Fails, but creates\nthe component template and cannot update the index template to reference\nthe new component template due to the error\\r\\n\\r\\nPUT\n/_component_template/.risk-score-mappings-default\\r\\n{\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_shards\\\": 1\\r\\n },\\r\\n\n\\\"mappings\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"timestamp\\\": {\\r\\n \\\"type\\\":\n\\\"date\\\"\\r\\n },\\r\\n \\\"user\\\": {\\r\\n \\\"properties\\\": {\\r\\n \\\"id\\\": {\\r\\n\n\\\"type\\\": \\\"keyword\\\"\\r\\n },\\r\\n \\\"name\\\": {\\r\\n \\\"type\\\": \\\"text\\\"\\r\\n\n}\\r\\n }\\r\\n }\\r\\n }\\r\\n }\\r\\n },\\r\\n \\\"version\\\": 1\\r\\n}\\r\\n\\r\\nGET\n/_component_template?filter_path=component_templates.name&name=.risk-score-mappings*\\r\\n\\r\\n\\r\\nDELETE\n/_component_template/.risk-score-mappings\\r\\n\\r\\n# Fails \\r\\n\\r\\n#\nchanged flow\\r\\nPUT\n/_index_template/.risk-score.risk-score-default-index-template\\r\\n{\\r\\n\n\\\"index_patterns\\\":\n[\\\".risk-score.risk-score-default-index-template\\\"],\\r\\n \\\"template\\\":\n{\\r\\n \\\"settings\\\": {\\r\\n \\\"number_of_replicas\\\": 1\\r\\n }\\r\\n },\\r\\n\n\\\"composed_of\\\": [\\\".risk-score-mappings-default\\\"],\\r\\n \\\"priority\\\":\n100,\\r\\n \\\"version\\\": 1,\\r\\n \\\"_meta\\\": {\\r\\n \\\"description\\\": \\\"Index\ntemplate for indices with the pattern my_index-*\\\"\\r\\n\n}\\r\\n}\\r\\n\\r\\nDELETE /_component_template/.risk-score-mappings\\r\\n\\r\\n#\nSucceeds\\r\\n\\r\\n#########\\r\\n```\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nDelete\nany items that are not applicable to this PR.\\r\\n\\r\\n- [ ] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [ ] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n\\r\\n\\r\\n\\r\\n### For\nmaintainers\\r\\n\\r\\n- [ ] This was checked for breaking API changes and\nwas\n[labeled\\r\\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#_add_your_labels)\\r\\n-\n[ ] This will appear in the **Release Notes** and follow\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\",\"sha\":\"771c139269ac0eac27274e0858be2fbcf87b31e3\"}},{\"branch\":\"8.x\",\"label\":\"v8.17.0\",\"labelRegex\":\"^v8.17.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.1\",\"labelRegex\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Konrad Szwarc
|
83391ca5d9
|
[8.17] [EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205) (#212387)
# Backport This will backport the following commits from `main` to `8.17`: - [[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)](https://github.com/elastic/kibana/pull/212205) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Konrad Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2025-02-25T13:18:56Z","message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","v8.16.0","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[EDR Workflows] OpenApi Missing Content - Endpoint Management","number":212205,"url":"https://github.com/elastic/kibana/pull/212205","mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb"}},"sourceBranch":"main","suggestedTargetBranches":["8.16","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212374","number":212374,"state":"OPEN"},{"branch":"8.16","label":"v8.16.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,"url":"https://github.com/elastic/kibana/pull/212373","number":212373,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212205","number":212205,"mergeCommit":{"message":"[EDR Workflows] OpenApi Missing Content - Endpoint Management (#212205)\n\nPart of DW team effort -\nhttps://github.com/elastic/security-team/issues/11804\n\nThis PR aligns the property/schema descriptions and examples in\nAsciiDocs with OpenAPI schemas. The primary goal of this PR was not to\nextend or enhance the documentation but to migrate from one system to\nanother.\n\nAscii docs -\nhttps://www.elastic.co/guide/en/kibana/8.17/osquery-manager-api.html\nOpenApi generated docs -\nhttps://www.elastic.co/docs/api/doc/kibana/operation/operation-endpointgetactionslist\n\nChanges:\n\nCopied missing property descriptions from AsciiDoc to OpenApi properties\nCopied existing AsciiDoc examples for both requests and responses\nFixed falsy query object in some GET requests - in OpenApi it was\ndefined as an object, not as path query params.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>","sha":"3492f12c6c47d36de200682e43fae5684dbf49bb"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
elastic-renovate-prod[bot]
|
84027ef899
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to c66fdaf (8.17) (#212394)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `0801a43` -> `c66fdaf` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
Patryk Kopyciński
|
0ccc106cac
|
[8.17] Fix calling Sonnet 3.7 (#212372) (#212411)
# Backport This will backport the following commits from `main` to `8.17`: - [Fix calling Sonnet 3.7 (#212372)](https://github.com/elastic/kibana/pull/212372) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-02-25T15:41:55Z","message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.17.3"],"title":"Fix calling Sonnet 3.7","number":212372,"url":"https://github.com/elastic/kibana/pull/212372","mergeCommit":{"message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212399","number":212399,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212398","number":212398,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212372","number":212372,"mergeCommit":{"message":"Fix calling Sonnet 3.7 (#212372)\n\n## Summary\n\nFixes \n<img width=\"1509\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ba409fde-f52b-4864-a81a-70025ef61f2f\"\n/>","sha":"8c456d1e1eb172a2550455caa42cc503cf589e27"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
13cfa3ef48
|
[8.17] Fix Chart Trend by Severity Bug (#212358)
# Backport This will backport the following commits from `main` to `8.17`: - [Fix Chart Trend by Severity Bug](https://github.com/elastic/kibana/pull/211735) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ido Cohen","email":"90558359+CohenIdo@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-25T11:24:50Z","message":"Fix Chart Trend by Severity Bug","sha":"7f2df7cd427506486ac8f7a34498d0448c431992","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:Cloud Security","backport:prev-major","v8.16.0","v8.17.0","v8.18.0","v9.1.0"],"title":"Fix Chart Trend by Severity Bug","number":211735,"url":"https://github.com/elastic/kibana/pull/211735","mergeCommit":{"message":"Fix Chart Trend by Severity Bug","sha":"7f2df7cd427506486ac8f7a34498d0448c431992"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.16","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.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/211735","number":211735,"mergeCommit":{"message":"Fix Chart Trend by Severity Bug","sha":"7f2df7cd427506486ac8f7a34498d0448c431992"}}]}] BACKPORT--> Co-authored-by: Ido Cohen <90558359+CohenIdo@users.noreply.github.com> |
||
|
Kibana Machine
|
bf94e613b9
|
[8.17] [Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143) (#210881)
# Backport This will backport the following commits from `main` to `8.17`: - [[Discover Session] Fix "Untitled" export title when exporting CSV on a dashboard (#210143)](https://github.com/elastic/kibana/pull/210143) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthias Wilhelm","email":"matthias.wilhelm@elastic.co"},"sourceCommit":{"committedDate":"2025-02-12T16:24:43Z","message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard","number":210143,"url":"https://github.com/elastic/kibana/pull/210143","mergeCommit":{"message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8"}},"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/210143","number":210143,"mergeCommit":{"message":"[Discover Session] Fix \"Untitled\" export title when exporting CSV on a dashboard (#210143)\n\n- Fixes \"Untitled\" CSV exports when an export of a Discover session CSV is triggered on a Dashboard\n- Switches to make use of the embeddable title when exporting CSV of Discover session embeddables on a Dashboard.","sha":"7a72b14fd5a032f6bcf5ad5d68f84d7e092a23c8"}}]}] BACKPORT--> --------- Co-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co> |
||
|
Charlotte Alexandra Wilson
|
9e886b57cd
|
[8.17] [Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078) (#212265)
# Backport This will backport the following commits from `main` to `8.17`: - [[Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078)](https://github.com/elastic/kibana/pull/212078) <!--- Backport version: 9.6.6 --> ### 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-24T14:35:30Z","message":"[Security Solution] Fix Incorrect Enable Button Behavior in Entity Store Modal (#212078)\n\n## Summary\n\nEnsure Enable Button Considers Disabled State of Risk Score & Entity\nStore. Previously only used the checked state of the toggle.\n\n### Reproduce the Issue\nSteps, as [per bug\nticket:](https://github.com/elastic/kibana/issues/209242#issue-2826951496)\n\n1. Kibana version 8.16.0 or above should exist\n2. Navigate to the Dashboards tab under Security\n3. Select Entity Analytics dashboard\n4. Click on the enable button and enable risk score\n5. Disable the options for Entity store\n6. Then again select the enable button for Entity store\n7. Disable the enable button\n8. Observe the Enable button is still enabled\n\n### After Issue Solved\n\nSame steps as above, but should show the warning and disable the button.\n\n#### Videos\n\nVideos show when either riskScore or entityStore is enabled, and the\nother is unchecked, the warning should show and the button should be\ndisabled.\n\n\n |
||
Felix Stürmer
|
43587d848f
|
[8.17] [Logs UI] Fix log view loading states (#212124) (#212140)
# Backport This will backport the following commits from `8.x` to `8.17`: - [[Logs UI] Fix log view loading states (#212124)](https://github.com/elastic/kibana/pull/212124) <!--- Backport version: 9.6.6 --> ### 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-21T18:49:34Z","message":"[Logs UI] Fix log view loading states (#212124)\n\nThis fixes a problem with the log view resolution when entering the log\nsettings page under certain conditions.","sha":"aa26fe3c0b921c3696dba7023a4fced72c4a2043","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","backport:version","v8.18.0","v8.19.0","v8.17.3"],"title":"[Logs UI] Fix log view loading states","number":212124,"url":"https://github.com/elastic/kibana/pull/212124","mergeCommit":{"message":"[Logs UI] Fix log view loading states (#212124)\n\nThis fixes a problem with the log view resolution when entering the log\nsettings page under certain conditions.","sha":"aa26fe3c0b921c3696dba7023a4fced72c4a2043"}},"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.19","label":"v8.19.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--> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
elastic-vault-github-plugin-prod[bot]
|
f83518d598
|
[8.17] Sync bundled packages with Package Storage (#212223)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2343 Co-authored-by: elasticmachine <elasticmachine@elastic.co> |
||
|
Kibana Machine
|
3bd3eecdb4
|
[8.17] Log request ID in SAML provider (#211877) (#212218)
# Backport This will backport the following commits from `main` to `8.17`: - [Log request ID in SAML provider (#211877)](https://github.com/elastic/kibana/pull/211877) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jeramy Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2025-02-24T11:00:06Z","message":"Log request ID in SAML provider (#211877)\n\n## Summary\n\nThis PR adds logging of request ID in SAML provider. Having the request\nID assists in troubleshooting by providing a means to correlate\nauthentication attempts across Kibana and ES logs.\n\nThe full request ID is logged because it is not considered sensitive\ninformation - it is a temporary identifier that is only relevant for a\nsingle authentication attempt.","sha":"317580fdd56572323195b3fec7bfab226b46fdf6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","backport:prev-major","v9.1.0"],"title":"Log request ID in SAML provider","number":211877,"url":"https://github.com/elastic/kibana/pull/211877","mergeCommit":{"message":"Log request ID in SAML provider (#211877)\n\n## Summary\n\nThis PR adds logging of request ID in SAML provider. Having the request\nID assists in troubleshooting by providing a means to correlate\nauthentication attempts across Kibana and ES logs.\n\nThe full request ID is logged because it is not considered sensitive\ninformation - it is a temporary identifier that is only relevant for a\nsingle authentication attempt.","sha":"317580fdd56572323195b3fec7bfab226b46fdf6"}},"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/211877","number":211877,"mergeCommit":{"message":"Log request ID in SAML provider (#211877)\n\n## Summary\n\nThis PR adds logging of request ID in SAML provider. Having the request\nID assists in troubleshooting by providing a means to correlate\nauthentication attempts across Kibana and ES logs.\n\nThe full request ID is logged because it is not considered sensitive\ninformation - it is a temporary identifier that is only relevant for a\nsingle authentication attempt.","sha":"317580fdd56572323195b3fec7bfab226b46fdf6"}}]}] BACKPORT--> Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co> |
||
|
elastic-vault-github-plugin-prod[bot]
|
7bcc6c02c3
|
[8.17] Sync bundled packages with Package Storage (#211978)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2327 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Jen Huang
|
beb0f5945b
|
[8.17] [UII] Drop ssl field from output if it's in an invalid format (#211848) (#212151)
# Backport This will backport the following commits from `main` to `8.17`: - [[UII] Drop ssl field from output if it's in an invalid format (#211848)](https://github.com/elastic/kibana/pull/211848) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2025-02-21T08:52:17Z","message":"[UII] Drop ssl field from output if it's in an invalid format (#211848)\n\n## Summary\n\nReported in https://github.com/elastic/sdh-beats/issues/5676. When\nretrieving outputs information, drop the `ssl` field if it's in an\ninvalid format (causing `JSON.parse` to fail).\n\nThis can happen for ES output with `ssl` field set via API, and then\nsubsequently editing it from the UI (ES output `ssl` fields are\ncurrently unsupported, soon to be supported by\nhttps://github.com/elastic/kibana/issues/207326.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0c932fd4aba794767bf2298911e0f2e2ec2bffb3","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-major","v8.18.0","v9.1.0","v8.19.0"],"title":"[UII] Drop ssl field from output if it's in an invalid format","number":211848,"url":"https://github.com/elastic/kibana/pull/211848","mergeCommit":{"message":"[UII] Drop ssl field from output if it's in an invalid format (#211848)\n\n## Summary\n\nReported in https://github.com/elastic/sdh-beats/issues/5676. When\nretrieving outputs information, drop the `ssl` field if it's in an\ninvalid format (causing `JSON.parse` to fail).\n\nThis can happen for ES output with `ssl` field set via API, and then\nsubsequently editing it from the UI (ES output `ssl` fields are\ncurrently unsupported, soon to be supported by\nhttps://github.com/elastic/kibana/issues/207326.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0c932fd4aba794767bf2298911e0f2e2ec2bffb3"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212015","number":212015,"state":"MERGED","mergeCommit":{"sha":"fc82a79ec2f0f6ad1d91c7a32f06822ebd7bf535","message":"[8.18] [UII] Drop ssl field from output if it's in an invalid format (#211848) (#212015)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [[UII] Drop ssl field from output if it's in an invalid format\n(#211848)](https://github.com/elastic/kibana/pull/211848)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jen Huang <its.jenetic@gmail.com>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211848","number":211848,"mergeCommit":{"message":"[UII] Drop ssl field from output if it's in an invalid format (#211848)\n\n## Summary\n\nReported in https://github.com/elastic/sdh-beats/issues/5676. When\nretrieving outputs information, drop the `ssl` field if it's in an\ninvalid format (causing `JSON.parse` to fail).\n\nThis can happen for ES output with `ssl` field set via API, and then\nsubsequently editing it from the UI (ES output `ssl` fields are\ncurrently unsupported, soon to be supported by\nhttps://github.com/elastic/kibana/issues/207326.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"0c932fd4aba794767bf2298911e0f2e2ec2bffb3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/212016","number":212016,"state":"MERGED","mergeCommit":{"sha":"26fe14935bc6c1be610057662c55f3b6bc0c2fde","message":"[8.x] [UII] Drop ssl field from output if it's in an invalid format (#211848) (#212016)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [[UII] Drop ssl field from output if it's in an invalid format\n(#211848)](https://github.com/elastic/kibana/pull/211848)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n\n\nCo-authored-by: Jen Huang <its.jenetic@gmail.com>"}}]}] BACKPORT--> |
||
Davis McPhee
|
f9f26752de
|
[8.17] [Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678) (#212142)
# Backport This will backport the following commits from `main` to `8.17`: - [[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)](https://github.com/elastic/kibana/pull/211678) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Davis McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2025-02-21T17:26:22Z","message":"[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)\n\n## Summary\n\nThis PR re-adds drilldown support to the Discover session embeddable\nafter it was accidentally removed during the refactoring in #180536\n(related PR where drilldowns / dynamic actions were refactored:\n#178896). A new functional test has also been added to prevent future\nregressions.\n\nFixes #211677.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"257971d4c0f99c0da56b9b817cff731977f8891f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Discover] [Embeddable] Fix Discover session embeddable drilldown","number":211678,"url":"https://github.com/elastic/kibana/pull/211678","mergeCommit":{"message":"[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)\n\n## Summary\n\nThis PR re-adds drilldown support to the Discover session embeddable\nafter it was accidentally removed during the refactoring in #180536\n(related PR where drilldowns / dynamic actions were refactored:\n#178896). A new functional test has also been added to prevent future\nregressions.\n\nFixes #211677.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"257971d4c0f99c0da56b9b817cff731977f8891f"}},"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/211678","number":211678,"mergeCommit":{"message":"[Discover] [Embeddable] Fix Discover session embeddable drilldown (#211678)\n\n## Summary\n\nThis PR re-adds drilldown support to the Discover session embeddable\nafter it was accidentally removed during the refactoring in #180536\n(related PR where drilldowns / dynamic actions were refactored:\n#178896). A new functional test has also been added to prevent future\nregressions.\n\nFixes #211677.\n\n### Checklist\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Matthias Wilhelm <matthias.wilhelm@elastic.co>","sha":"257971d4c0f99c0da56b9b817cff731977f8891f"}}]}] BACKPORT--> |
||
|
elastic-renovate-prod[bot]
|
5ec051eb89
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 0801a43 (8.17) (#212068)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `d74b1fd` -> `0801a43` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
cf07b4882d
|
[8.17] [Fleet] fix prerelease:boolean in package_service (#212054) (#212083)
# Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] fix `prerelease:boolean` in package_service (#212054)](https://github.com/elastic/kibana/pull/212054) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-21T13:51:21Z","message":"[Fleet] fix `prerelease:boolean` in package_service (#212054)\n\nUse `boolean` instead of `false` in `getPackages` to support querying\nprerelease packages.","sha":"dbfb433ec28a080879c26232c7a8ea516efd082f","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-major","v9.1.0"],"title":"[Fleet] fix `prerelease:boolean` in package_service","number":212054,"url":"https://github.com/elastic/kibana/pull/212054","mergeCommit":{"message":"[Fleet] fix `prerelease:boolean` in package_service (#212054)\n\nUse `boolean` instead of `false` in `getPackages` to support querying\nprerelease packages.","sha":"dbfb433ec28a080879c26232c7a8ea516efd082f"}},"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/212054","number":212054,"mergeCommit":{"message":"[Fleet] fix `prerelease:boolean` in package_service (#212054)\n\nUse `boolean` instead of `false` in `getPackages` to support querying\nprerelease packages.","sha":"dbfb433ec28a080879c26232c7a8ea516efd082f"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
bb810fa05b
|
[8.17] [Feature Flags] Remove apm.captureError on slow setup (#212037) (#212057)
# Backport This will backport the following commits from `main` to `8.17`: - [[Feature Flags] Remove `apm.captureError` on slow setup (#212037)](https://github.com/elastic/kibana/pull/212037) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-02-21T12:20:37Z","message":"[Feature Flags] Remove `apm.captureError` on slow setup (#212037)","sha":"f4d3652832c557f68890aca68df12003de7a1652","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","technical debt","release_note:skip","backport:prev-major","v9.1.0"],"title":"[Feature Flags] Remove `apm.captureError` on slow setup","number":212037,"url":"https://github.com/elastic/kibana/pull/212037","mergeCommit":{"message":"[Feature Flags] Remove `apm.captureError` on slow setup (#212037)","sha":"f4d3652832c557f68890aca68df12003de7a1652"}},"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/212037","number":212037,"mergeCommit":{"message":"[Feature Flags] Remove `apm.captureError` on slow setup (#212037)","sha":"f4d3652832c557f68890aca68df12003de7a1652"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
Bryce Buchanan
|
c1220342a6
|
[8.17] Added versioning to inventory_view_saved_object (#207007) (#211634)
# Backport This will backport the following commits from `main` to `8.17`: - [Added versioning to inventory_view_saved_object (#207007)](https://github.com/elastic/kibana/pull/207007) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Bryce Buchanan","email":"75274611+bryce-b@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-27T18:09:32Z","message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\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] [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] 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":"a108c632a459240f9c27262395e2584f92d43779","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:fix","backport missing","v9.0.0","Team:obs-ux-infra_services"],"title":"Added versioning to inventory_view_saved_object","number":207007,"url":"https://github.com/elastic/kibana/pull/207007","mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\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] [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] 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":"a108c632a459240f9c27262395e2584f92d43779"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207007","number":207007,"mergeCommit":{"message":"Added versioning to inventory_view_saved_object (#207007)\n\n## Summary\r\n\r\nFixes #187254 \r\nStrict checks on the attribute `legend.steps` was added to the inventory\r\nview API in v8.10 (#160852), but they were not defined in the\r\nsaved object type for that data, resulting in older versions migrating\r\nbad data, and being unable to use the API. This PR adds versioning to\r\nthe Inventory view saved object type that constrains legend.steps to\r\nbetween 2 and 18, per the strict typing added in #160852\r\n\r\n#### Open questions\r\nShould we add notes to all versions of kibana between v8.10 and oldest\r\nversion available for backport describing this bug?\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] [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] 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":"a108c632a459240f9c27262395e2584f92d43779"}}]}] BACKPORT--> |
||
Quynh Nguyen (Quinn)
|
6836e6c67d
|
[8.17] [Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217) (#211809)
# Backport This will backport the following commits from `main` to `8.17`: - [[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)](https://github.com/elastic/kibana/pull/210217) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Quynh Nguyen (Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-13T05:49:58Z","message":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)\n\n## Summary\n\nThis PR partially addresses an issue with\nhttps://github.com/elastic/integrations/issues/12486 where the transform\ndoesn't \"restart\" immediately after reauthorizing. This is because for\nunattended transform, calling `_start` will come back with 409 transform\nalready started error. So this PR tracks if the transform has\n`settings.unattended: true`, if yes, stop the transform first before\nstarting.\n\nWithout this step, the transform will retry again and become healthy\nagain anyway but it takes longer for that retry to happen, so this PR\nspeeds up the process of retrying.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e710f09d0c1159a9018ff6b9dfbac151509213f9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:Fleet","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing","number":210217,"url":"https://github.com/elastic/kibana/pull/210217","mergeCommit":{"message":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)\n\n## Summary\n\nThis PR partially addresses an issue with\nhttps://github.com/elastic/integrations/issues/12486 where the transform\ndoesn't \"restart\" immediately after reauthorizing. This is because for\nunattended transform, calling `_start` will come back with 409 transform\nalready started error. So this PR tracks if the transform has\n`settings.unattended: true`, if yes, stop the transform first before\nstarting.\n\nWithout this step, the transform will retry again and become healthy\nagain anyway but it takes longer for that retry to happen, so this PR\nspeeds up the process of retrying.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e710f09d0c1159a9018ff6b9dfbac151509213f9"}},"sourceBranch":"main","suggestedTargetBranches":["8.18","8.x","8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210950","number":210950,"state":"MERGED","mergeCommit":{"sha":"a8d9319cdd70a1ead8228d0da858c71bd709efe6","message":"[9.0] [Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217) (#210950)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [[Fleet] Fix unattended Transforms in integration packages not\nautomatically restarting after reauthorizing\n(#210217)](https://github.com/elastic/kibana/pull/210217)\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\":\"Quynh Nguyen\n(Quinn)\",\"email\":\"43350163+qn895@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-13T05:49:58Z\",\"message\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after reauthorizing (#210217)\\n\\n## Summary\\n\\nThis PR\npartially addresses an issue\nwith\\nhttps://github.com/elastic/integrations/issues/12486 where the\ntransform\\ndoesn't \\\"restart\\\" immediately after reauthorizing. This is\nbecause for\\nunattended transform, calling `_start` will come back with\n409 transform\\nalready started error. So this PR tracks if the transform\nhas\\n`settings.unattended: true`, if yes, stop the transform first\nbefore\\nstarting.\\n\\nWithout this step, the transform will retry again\nand become healthy\\nagain anyway but it takes longer for that retry to\nhappen, so this PR\\nspeeds up the process of retrying.\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] Any text\nadded follows [EUI's\nwriting\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\nsentence case text and includes\n[i18n\\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\\n-\n[\n]\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\nwas\nadded for features that require explanation or tutorials\\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- [ ] If a plugin\nconfiguration key changed, check if it needs to be\\nallowlisted in the\ncloud and added to the\n[docker\\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\\n-\n[ ] This was checked for breaking HTTP API changes, and any\nbreaking\\nchanges have been approved by the breaking-change committee.\nThe\\n`release_note:breaking` label should be applied in these\nsituations.\\n- [ ] [Flaky\nTest\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\nused on any tests changed\\n- [ ] The PR description includes the\nappropriate Release Notes section,\\nand the correct `release_note:*`\nlabel is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n###\nIdentify risks\\n\\nDoes this PR introduce any risks? For example,\nconsider risks like hard\\nto test bugs, performance regression,\npotential of data loss.\\n\\nDescribe the risk, its severity, and\nmitigation for each identified\\nrisk. Invite stakeholders and evaluate\nhow to proceed before merging.\\n\\n- [ ] [See some\nrisk\\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\\n-\n[ ] ...\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"e710f09d0c1159a9018ff6b9dfbac151509213f9\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:fix\",\":ml\",\"Team:Fleet\",\"v9.0.0\",\"backport:version\",\"v8.18.0\",\"v9.1.0\",\"v8.19.0\",\"v8.17.3\",\"v8.16.5\"],\"title\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after\nreauthorizing\",\"number\":210217,\"url\":\"https://github.com/elastic/kibana/pull/210217\",\"mergeCommit\":{\"message\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after reauthorizing (#210217)\\n\\n## Summary\\n\\nThis PR\npartially addresses an issue\nwith\\nhttps://github.com/elastic/integrations/issues/12486 where the\ntransform\\ndoesn't \\\"restart\\\" immediately after reauthorizing. This is\nbecause for\\nunattended transform, calling `_start` will come back with\n409 transform\\nalready started error. So this PR tracks if the transform\nhas\\n`settings.unattended: true`, if yes, stop the transform first\nbefore\\nstarting.\\n\\nWithout this step, the transform will retry again\nand become healthy\\nagain anyway but it takes longer for that retry to\nhappen, so this PR\\nspeeds up the process of retrying.\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] Any text\nadded follows [EUI's\nwriting\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\nsentence case text and includes\n[i18n\\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\\n-\n[\n]\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\nwas\nadded for features that require explanation or tutorials\\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- [ ] If a plugin\nconfiguration key changed, check if it needs to be\\nallowlisted in the\ncloud and added to the\n[docker\\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\\n-\n[ ] This was checked for breaking HTTP API changes, and any\nbreaking\\nchanges have been approved by the breaking-change committee.\nThe\\n`release_note:breaking` label should be applied in these\nsituations.\\n- [ ] [Flaky\nTest\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\nused on any tests changed\\n- [ ] The PR description includes the\nappropriate Release Notes section,\\nand the correct `release_note:*`\nlabel is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n###\nIdentify risks\\n\\nDoes this PR introduce any risks? For example,\nconsider risks like hard\\nto test bugs, performance regression,\npotential of data loss.\\n\\nDescribe the risk, its severity, and\nmitigation for each identified\\nrisk. Invite stakeholders and evaluate\nhow to proceed before merging.\\n\\n- [ ] [See some\nrisk\\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\\n-\n[ ] ...\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"e710f09d0c1159a9018ff6b9dfbac151509213f9\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"9.0\",\"8.18\",\"8.x\",\"8.17\",\"8.16\"],\"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/210217\",\"number\":210217,\"mergeCommit\":{\"message\":\"[Fleet]\nFix unattended Transforms in integration packages not automatically\nrestarting after reauthorizing (#210217)\\n\\n## Summary\\n\\nThis PR\npartially addresses an issue\nwith\\nhttps://github.com/elastic/integrations/issues/12486 where the\ntransform\\ndoesn't \\\"restart\\\" immediately after reauthorizing. This is\nbecause for\\nunattended transform, calling `_start` will come back with\n409 transform\\nalready started error. So this PR tracks if the transform\nhas\\n`settings.unattended: true`, if yes, stop the transform first\nbefore\\nstarting.\\n\\nWithout this step, the transform will retry again\nand become healthy\\nagain anyway but it takes longer for that retry to\nhappen, so this PR\\nspeeds up the process of retrying.\\n\\n\\n###\nChecklist\\n\\nCheck the PR satisfies following conditions. \\n\\nReviewers\nshould verify this PR satisfies this list as well.\\n\\n- [ ] Any text\nadded follows [EUI's\nwriting\\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),\nuses\\nsentence case text and includes\n[i18n\\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\\n-\n[\n]\\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\\nwas\nadded for features that require explanation or tutorials\\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- [ ] If a plugin\nconfiguration key changed, check if it needs to be\\nallowlisted in the\ncloud and added to the\n[docker\\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\\n-\n[ ] This was checked for breaking HTTP API changes, and any\nbreaking\\nchanges have been approved by the breaking-change committee.\nThe\\n`release_note:breaking` label should be applied in these\nsituations.\\n- [ ] [Flaky\nTest\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\nused on any tests changed\\n- [ ] The PR description includes the\nappropriate Release Notes section,\\nand the correct `release_note:*`\nlabel is applied per\nthe\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\n\\n###\nIdentify risks\\n\\nDoes this PR introduce any risks? For example,\nconsider risks like hard\\nto test bugs, performance regression,\npotential of data loss.\\n\\nDescribe the risk, its severity, and\nmitigation for each identified\\nrisk. Invite stakeholders and evaluate\nhow to proceed before merging.\\n\\n- [ ] [See some\nrisk\\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\\n-\n[ ] ...\\n\\n---------\\n\\nCo-authored-by: Elastic Machine\n<elasticmachine@users.noreply.github.com>\",\"sha\":\"e710f09d0c1159a9018ff6b9dfbac151509213f9\"}},{\"branch\":\"8.x\",\"label\":\"v8.19.0\",\"branchLabelMappingKey\":\"^v8.19.0$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.17\",\"label\":\"v8.17.3\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"},{\"branch\":\"8.16\",\"label\":\"v8.16.5\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>"}},{"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/210217","number":210217,"mergeCommit":{"message":"[Fleet] Fix unattended Transforms in integration packages not automatically restarting after reauthorizing (#210217)\n\n## Summary\n\nThis PR partially addresses an issue with\nhttps://github.com/elastic/integrations/issues/12486 where the transform\ndoesn't \"restart\" immediately after reauthorizing. This is because for\nunattended transform, calling `_start` will come back with 409 transform\nalready started error. So this PR tracks if the transform has\n`settings.unattended: true`, if yes, stop the transform first before\nstarting.\n\nWithout this step, the transform will retry again and become healthy\nagain anyway but it takes longer for that retry to happen, so this PR\nspeeds up the process of retrying.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...\n\n---------\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"e710f09d0c1159a9018ff6b9dfbac151509213f9"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
5e5f56de9e
|
[8.17] [SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845) (#211754)
# Backport This will backport the following commits from `main` to `8.17`: - [[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)](https://github.com/elastic/kibana/pull/210845) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ash","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-19T12:52:30Z","message":"[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)\n\n## Summary\n\nRe enables skipped test (which was flaky due to Vagrant not available on\nCI).\ncloses https://github.com/elastic/kibana/issues/187932\n\n### Flaky runner\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867\nx 50 (1 fail)\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904\nx 50 (all pass)\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"98b565dd017d4e4c487f1d0b229caabb5dda4997","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend Workflows","OLM Sprint","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"[SecuritySolution][Endpoint] Re enable scan response action e2e test","number":210845,"url":"https://github.com/elastic/kibana/pull/210845","mergeCommit":{"message":"[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)\n\n## Summary\n\nRe enables skipped test (which was flaky due to Vagrant not available on\nCI).\ncloses https://github.com/elastic/kibana/issues/187932\n\n### Flaky runner\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867\nx 50 (1 fail)\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904\nx 50 (all pass)\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"98b565dd017d4e4c487f1d0b229caabb5dda4997"}},"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/210845","number":210845,"mergeCommit":{"message":"[SecuritySolution][Endpoint] Re enable scan response action e2e test (#210845)\n\n## Summary\n\nRe enables skipped test (which was flaky due to Vagrant not available on\nCI).\ncloses https://github.com/elastic/kibana/issues/187932\n\n### Flaky runner\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7867\nx 50 (1 fail)\n-\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/7904\nx 50 (all pass)\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] 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### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"98b565dd017d4e4c487f1d0b229caabb5dda4997"}}]}] BACKPORT--> Co-authored-by: Ash <1849116+ashokaditya@users.noreply.github.com> |
||
|
Charlotte Alexandra Wilson
|
a35f5057e2
|
[8.17] Entity Flyout flickers when loading risk score panel (#211568) (#211697)
# Backport This will backport the following commits from `8.x` to `8.17`: - [Entity Flyout flickers when loading risk score panel (#211568)](https://github.com/elastic/kibana/pull/211568) <!--- Backport version: 9.6.6 --> ### 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-18T15:09:12Z","message":"Entity Flyout flickers when loading risk score panel (#211568)\n\n## Summary\r\nThis PR fixes the issue where the Risk Score Panel flickers into view\r\nwhen no risk score is available yet. This occurs in two cases:\r\n1. Opening the flyout for a user or host.\r\n2. Updating Asset Criticality from the flyout.\r\n\r\n### Steps to Reproduce (Before Fix)\r\n[@abhishekbhatia1710](https://github.com/abhishekbhatia1710) [provided\r\nsteps as below in original\r\nticket](https://github.com/elastic/security-team/issues/11590#issuecomment-2643056694):\r\n\r\n1. Ensure you are using version 8.18\r\n2. Enable the Risk Engine.\r\n3. Enable the Entity Store.\r\n4. Upload the asset criticality file.\r\n5. Do not run the risk score on the newly added entities yet.\r\n6. Navigate to the EA Dashboard.\r\n7. Scroll down to the Entities section.\r\n8. Search for the user/host uploaded in the asset criticality file.\r\n9. Click on the entity to open the flyout.\r\n10. Assign asset criticality within the flyout.\r\n11. Before fix: Risk Score panel briefly appears (flickers) despite no\r\nrisk score being available.\r\n\r\n### Expected Behaviour (After Fix)\r\nFollowing the same steps, the Risk Score Panel no longer flickers when\r\nopening the flyout or updating asset criticality - for both user and\r\nhost entity types.\r\n\r\n### Video (After Fix)\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7ef28ee1-7e5d-43ae-b6d3-7075b63229be","sha":"f486939e0aa00163f4c41cdfaae96110ca508dc4","branchLabelMapping":{"^v8.16.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","fixed","Team: SecuritySolution","ci:project-deploy-security","ci:project-persist-deployment","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0"],"title":"Entity Flyout flickers when loading risk score panel","number":211568,"url":"https://github.com/elastic/kibana/pull/211568","mergeCommit":{"message":"Entity Flyout flickers when loading risk score panel (#211568)\n\n## Summary\r\nThis PR fixes the issue where the Risk Score Panel flickers into view\r\nwhen no risk score is available yet. This occurs in two cases:\r\n1. Opening the flyout for a user or host.\r\n2. Updating Asset Criticality from the flyout.\r\n\r\n### Steps to Reproduce (Before Fix)\r\n[@abhishekbhatia1710](https://github.com/abhishekbhatia1710) [provided\r\nsteps as below in original\r\nticket](https://github.com/elastic/security-team/issues/11590#issuecomment-2643056694):\r\n\r\n1. Ensure you are using version 8.18\r\n2. Enable the Risk Engine.\r\n3. Enable the Entity Store.\r\n4. Upload the asset criticality file.\r\n5. Do not run the risk score on the newly added entities yet.\r\n6. Navigate to the EA Dashboard.\r\n7. Scroll down to the Entities section.\r\n8. Search for the user/host uploaded in the asset criticality file.\r\n9. Click on the entity to open the flyout.\r\n10. Assign asset criticality within the flyout.\r\n11. Before fix: Risk Score panel briefly appears (flickers) despite no\r\nrisk score being available.\r\n\r\n### Expected Behaviour (After Fix)\r\nFollowing the same steps, the Risk Score Panel no longer flickers when\r\nopening the flyout or updating asset criticality - for both user and\r\nhost entity types.\r\n\r\n### Video (After Fix)\r\n\r\n\r\n\r\nhttps://github.com/user-attachments/assets/7ef28ee1-7e5d-43ae-b6d3-7075b63229be","sha":"f486939e0aa00163f4c41cdfaae96110ca508dc4"}},"sourceBranch":"8.x","suggestedTargetBranches":["8.17","8.18"],"targetPullRequestStates":[{"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"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Tiago Costa
|
8f8369753b
|
[8.17] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211672)
# Backport This will backport the following commits from `main` to `8.17`: - [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)](https://github.com/elastic/kibana/pull/211231) <!--- Backport version: 9.6.6 --> ### 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-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","v8.18.0","v9.1.0","v8.19.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":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211284","number":211284,"state":"MERGED","mergeCommit":{"sha":"4bcd166b3aabbccbca03bd0a86110e29f0812171","message":"[8.18] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211284)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>"}},{"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"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211285","number":211285,"state":"MERGED","mergeCommit":{"sha":"73a5339547c64f9060465c4368e216744ce8d514","message":"[8.x] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211285)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>"}}]}] BACKPORT--> |
||
|
Tiago Costa
|
42f6645391
|
[8.17] chore(NA): upgrade to webpack 5 (#191106) (#211148)
# Backport This will backport the following commits from `main` to `8.17`: - [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"},{"url":"https://github.com/elastic/kibana/pull/211147","number":211147,"branch":"8.18","state":"OPEN"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Hannah Mudge
|
95ccee0a43
|
[8.17] [Links] Fix link settings not persisting (#211041) (#211106)
# Backport This will backport the following commits from `main` to `8.17`: - [[Links] Fix link settings not persisting (#211041)](https://github.com/elastic/kibana/pull/211041) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/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 |
||
|
elastic-renovate-prod[bot]
|
09ee7a2fcb
|
Update ftr (8.17) (#208429)
This PR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [chromedriver](https://redirect.github.com/giggio/node-chromedriver) | devDependencies | major | [`^132.0.0` -> `^133.0.0`](https://renovatebot.com/diffs/npm/chromedriver/132.0.0/133.0.0) | `133.0.1` | | [selenium-webdriver](https://redirect.github.com/SeleniumHQ/selenium/tree/trunk/javascript/node/selenium-webdriver#readme) ([source](https://redirect.github.com/SeleniumHQ/selenium)) | devDependencies | minor | [`^4.27.0` -> `^4.28.1`](https://renovatebot.com/diffs/npm/selenium-webdriver/4.27.0/4.28.1) | | --- ### Release Notes <details> <summary>giggio/node-chromedriver (chromedriver)</summary> ### [`v133.0.0`](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.2...133.0.0) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.2...133.0.0) ### [`v132.0.2`](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.1...132.0.2) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.1...132.0.2) ### [`v132.0.1`](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.0...132.0.1) [Compare Source](https://redirect.github.com/giggio/node-chromedriver/compare/132.0.0...132.0.1) </details> <details> <summary>SeleniumHQ/selenium (selenium-webdriver)</summary> ### [`v4.28.1`]( |
||
Nathan Reese
|
1829e15687
|
[dashboard] fix legacy embeddables do not render in print mode (#211072)
Closes https://github.com/elastic/kibana/issues/211070 Immediately resolve `DashboardContainer.untilContainerInitialized` when in print mode since controlGroupApi will never become available. Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
|
elastic-vault-github-plugin-prod[bot]
|
c509757553
|
[8.17] Sync bundled packages with Package Storage (#211467)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2298 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
ff21da4036
|
[8.17] Bump backport to v9.6.6 (#211424) (#211480)
# Backport This will backport the following commits from `main` to `8.17`: - [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> |
||
Alejandro Fernández Haro
|
088b1fd100
|
[8.17] Update dependency semver to ^7.7.1 (main) (#210557) (#211333)
# Backport This will backport the following commits from `main` to `8.17`: - [Update dependency semver to ^7.7.1 (main) (#210557)](https://github.com/elastic/kibana/pull/210557) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T12:16:24Z","message":"Update dependency semver to ^7.7.1 (main) (#210557)","sha":"bcfdd13c11871b37685a701eb781d9b9dbfa80e3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:all-open","v8.18.0","v9.1.0","v8.19.0"],"title":"Update dependency semver to ^7.7.1 (main)","number":210557,"url":"https://github.com/elastic/kibana/pull/210557","mergeCommit":{"message":"Update dependency semver to ^7.7.1 (main) (#210557)","sha":"bcfdd13c11871b37685a701eb781d9b9dbfa80e3"}},"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/210813","number":210813,"state":"MERGED","mergeCommit":{"sha":"ccb00f4d4b142cbd7cc7d840f46ecad075d62702","message":"[9.0] Update dependency semver to ^7.7.1 (main) (#210557) (#210813)\n\n# Backport\n\nThis will backport the following commits from `main` to `9.0`:\n- [Update dependency semver to ^7.7.1 (main)\n(#210557)](https://github.com/elastic/kibana/pull/210557)\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\n[{\"author\":{\"name\":\"elastic-renovate-prod[bot]\",\"email\":\"174716857+elastic-renovate-prod[bot]@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T12:16:24Z\",\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Core\",\"release_note:skip\",\"backport:all-open\",\"v9.1.0\"],\"title\":\"Update\ndependency semver to ^7.7.1\n(main)\",\"number\":210557,\"url\":\"https://github.com/elastic/kibana/pull/210557\",\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}},\"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/210557\",\"number\":210557,\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}}]}]\nBACKPORT-->\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>"}},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210811","number":210811,"state":"MERGED","mergeCommit":{"sha":"c2d3c70ac99c80ed03381ecec7f91cf41910fbc0","message":"[8.18] Update dependency semver to ^7.7.1 (main) (#210557) (#210811)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [Update dependency semver to ^7.7.1 (main)\n(#210557)](https://github.com/elastic/kibana/pull/210557)\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\n[{\"author\":{\"name\":\"elastic-renovate-prod[bot]\",\"email\":\"174716857+elastic-renovate-prod[bot]@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T12:16:24Z\",\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Core\",\"release_note:skip\",\"backport:all-open\",\"v9.1.0\"],\"title\":\"Update\ndependency semver to ^7.7.1\n(main)\",\"number\":210557,\"url\":\"https://github.com/elastic/kibana/pull/210557\",\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}},\"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/210557\",\"number\":210557,\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}}]}]\nBACKPORT-->\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@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/210557","number":210557,"mergeCommit":{"message":"Update dependency semver to ^7.7.1 (main) (#210557)","sha":"bcfdd13c11871b37685a701eb781d9b9dbfa80e3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/210812","number":210812,"state":"MERGED","mergeCommit":{"sha":"5e9835c1d65b0b44999f3e23963d556b7d4d7b43","message":"[8.x] Update dependency semver to ^7.7.1 (main) (#210557) (#210812)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [Update dependency semver to ^7.7.1 (main)\n(#210557)](https://github.com/elastic/kibana/pull/210557)\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\n[{\"author\":{\"name\":\"elastic-renovate-prod[bot]\",\"email\":\"174716857+elastic-renovate-prod[bot]@users.noreply.github.com\"},\"sourceCommit\":{\"committedDate\":\"2025-02-12T12:16:24Z\",\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\",\"branchLabelMapping\":{\"^v9.1.0$\":\"main\",\"^v8.19.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"Team:Core\",\"release_note:skip\",\"backport:all-open\",\"v9.1.0\"],\"title\":\"Update\ndependency semver to ^7.7.1\n(main)\",\"number\":210557,\"url\":\"https://github.com/elastic/kibana/pull/210557\",\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}},\"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/210557\",\"number\":210557,\"mergeCommit\":{\"message\":\"Update\ndependency semver to ^7.7.1 (main)\n(#210557)\",\"sha\":\"bcfdd13c11871b37685a701eb781d9b9dbfa80e3\"}}]}]\nBACKPORT-->\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>"}}]}] BACKPORT--> --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
Bharat Pasupula
|
6b2ed55f13
|
[8.17] [Automatic Import] Remove pipeline tests from the package (#211223) (#211405)
# Backport This will backport the following commits from `main` to `8.17`: - [[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--> |
||
|
elastic-vault-github-plugin-prod[bot]
|
372ff5c54f
|
[8.17] Sync bundled packages with Package Storage (#211273)
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> |
||
|
Felix Stürmer
|
4de5655725
|
[8.17] [Logs UI] Allow editing of non-resolving log views (#210633) (#211242)
# Backport This will backport the following commits from `8.x` to `8.17`: - [[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
|
b7cd76ef91
|
[8.17] Update Logs Explorer deprecation messages (#201307) (#210681)
# Backport This will backport the following commits from `main` to `8.17`: - [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
|
473352f876
|
[8.17] Upgrade elliptic 6.5.7 → 6.6.1 (#211225) (#211291)
# Backport This will backport the following commits from `main` to `8.17`: - [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> |
||
|
Nathan Reese
|
ed6b357377
|
[8.17] [visualize] fix Save to library action from a by value panel breaks the chart panel (#210125) (#211054)
# Backport This will backport the following commits from `main` to `8.17`: - [[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)](https://github.com/elastic/kibana/pull/210125) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nathan Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2025-02-13T17:09:29Z","message":"[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)\n\nFixes https://github.com/elastic/kibana/issues/206921\r\n\r\n### Problem\r\nThe visualize embeddable is inconstant when passing runtime state to\r\n`buildEmbeddable`. Sometimes, only `{ savedObjectId }` is provided. The\r\nembeddable tried to work around this by calling `deserializeState` in\r\n`buildEmbeddable`.\r\n\r\nThere was a different bug with the `deserializeState` guard in\r\n`buildEmbeddable` where state like `{ savedObjectId, savedVis: {} }`\r\nwould not pass the guard. Dashboard adds runtime state so `savedVis` was\r\ngetting added to `initialState` and thus failing the guard\r\n\r\nThis resulted in the visualize embeddable trying to initialize with\r\nstate `{ savedObjectId }` instead of state in the shape `{\r\nsavedObjectId, serializedVis: {} }`. This resulted in error message like\r\n\"Could not read properties of undefined\" when the embeddable tried to\r\nread from `state.serializedVis.type`.\r\n\r\n### Solution\r\nThe solution is to ensure that `buildEmbeddable` is always passed\r\nruntime state containing `serializedVis`. This pattern is in line with\r\nthe lens embeddable.\r\n\r\n### Test instructions\r\n* install sample web logs\r\n* create agg based visualization\r\n* create new dashboard, add agg based visualization. Open context menu\r\nof vis and select \"Unlink from library\". (Side note, removing legacy\r\nvisualizations from add panel makes it hard to add by-value agg based\r\nvisualizations to a dashboard)\r\n* save dashboard\r\n* edit agg based vis\r\n* Click \"Save to library\" and fill out form\r\n* Verify visualization is rendered in dashboard.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"109dcce33864a4d8be2e5dc6ac088d8a9976afb5","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","v9.0.0","project:embeddableRebuild","backport:version","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"[visualize] fix Save to library action from a by value panel breaks the chart panel","number":210125,"url":"https://github.com/elastic/kibana/pull/210125","mergeCommit":{"message":"[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)\n\nFixes https://github.com/elastic/kibana/issues/206921\r\n\r\n### Problem\r\nThe visualize embeddable is inconstant when passing runtime state to\r\n`buildEmbeddable`. Sometimes, only `{ savedObjectId }` is provided. The\r\nembeddable tried to work around this by calling `deserializeState` in\r\n`buildEmbeddable`.\r\n\r\nThere was a different bug with the `deserializeState` guard in\r\n`buildEmbeddable` where state like `{ savedObjectId, savedVis: {} }`\r\nwould not pass the guard. Dashboard adds runtime state so `savedVis` was\r\ngetting added to `initialState` and thus failing the guard\r\n\r\nThis resulted in the visualize embeddable trying to initialize with\r\nstate `{ savedObjectId }` instead of state in the shape `{\r\nsavedObjectId, serializedVis: {} }`. This resulted in error message like\r\n\"Could not read properties of undefined\" when the embeddable tried to\r\nread from `state.serializedVis.type`.\r\n\r\n### Solution\r\nThe solution is to ensure that `buildEmbeddable` is always passed\r\nruntime state containing `serializedVis`. This pattern is in line with\r\nthe lens embeddable.\r\n\r\n### Test instructions\r\n* install sample web logs\r\n* create agg based visualization\r\n* create new dashboard, add agg based visualization. Open context menu\r\nof vis and select \"Unlink from library\". (Side note, removing legacy\r\nvisualizations from add panel makes it hard to add by-value agg based\r\nvisualizations to a dashboard)\r\n* save dashboard\r\n* edit agg based vis\r\n* Click \"Save to library\" and fill out form\r\n* Verify visualization is rendered in dashboard.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"109dcce33864a4d8be2e5dc6ac088d8a9976afb5"}},"sourceBranch":"main","suggestedTargetBranches":["8.17","8.16"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211052","number":211052,"state":"OPEN"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211050","number":211050,"state":"OPEN"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/210125","number":210125,"mergeCommit":{"message":"[visualize] fix Save to library action from a by value panel breaks the chart panel (#210125)\n\nFixes https://github.com/elastic/kibana/issues/206921\r\n\r\n### Problem\r\nThe visualize embeddable is inconstant when passing runtime state to\r\n`buildEmbeddable`. Sometimes, only `{ savedObjectId }` is provided. The\r\nembeddable tried to work around this by calling `deserializeState` in\r\n`buildEmbeddable`.\r\n\r\nThere was a different bug with the `deserializeState` guard in\r\n`buildEmbeddable` where state like `{ savedObjectId, savedVis: {} }`\r\nwould not pass the guard. Dashboard adds runtime state so `savedVis` was\r\ngetting added to `initialState` and thus failing the guard\r\n\r\nThis resulted in the visualize embeddable trying to initialize with\r\nstate `{ savedObjectId }` instead of state in the shape `{\r\nsavedObjectId, serializedVis: {} }`. This resulted in error message like\r\n\"Could not read properties of undefined\" when the embeddable tried to\r\nread from `state.serializedVis.type`.\r\n\r\n### Solution\r\nThe solution is to ensure that `buildEmbeddable` is always passed\r\nruntime state containing `serializedVis`. This pattern is in line with\r\nthe lens embeddable.\r\n\r\n### Test instructions\r\n* install sample web logs\r\n* create agg based visualization\r\n* create new dashboard, add agg based visualization. Open context menu\r\nof vis and select \"Unlink from library\". (Side note, removing legacy\r\nvisualizations from add panel makes it hard to add by-value agg based\r\nvisualizations to a dashboard)\r\n* save dashboard\r\n* edit agg based vis\r\n* Click \"Save to library\" and fill out form\r\n* Verify visualization is rendered in dashboard.\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"109dcce33864a4d8be2e5dc6ac088d8a9976afb5"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211051","number":211051,"state":"OPEN"},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
3ac78a46ea
|
[8.17] Fix notify_badge.tsx toggle not working (#208996) (#211184)
# Backport This will backport the following commits from `main` to `8.17`: - [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 |
||
|
Bharat Pasupula
|
3367949254
|
[8.17] [Automatic Import] Fix generated name for integration title (#210916) (#211151)
# Backport This will backport the following commits from `main` to `8.17`: - [[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> |
||
|
Bharat Pasupula
|
276752e8b1
|
[8.17] [Automatic Import] Fix package name validation (#210770) (#210816)
# Backport This will backport the following commits from `main` to `8.17`: - [[Automatic Import] Fix package name validation (#210770)](https://github.com/elastic/kibana/pull/210770) <!--- 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-12T11:48:20Z","message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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] 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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","backport:prev-minor","backport:prev-major","Team:Security-Scalability","Feature:AutomaticImport","v9.1.0"],"title":"[Automatic Import] Fix package name validation","number":210770,"url":"https://github.com/elastic/kibana/pull/210770","mergeCommit":{"message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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] 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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf"}},"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/210770","number":210770,"mergeCommit":{"message":"[Automatic Import] Fix package name validation (#210770)\n\n## Release Note\r\n\r\nFix package name validation on Datastream page.\r\n\r\n## Summary\r\n\r\nCloses - #199893\r\n\r\nIf the package name starts with a number [ Only number , alphabet ,\r\nunderscore are allowed ] then some of the script processors in the\r\npipeline fail with dot annotation since the fields are formed like\r\n`ctx.123_abc.something` which fails with `Illegal Argument Exception` in\r\nscript processor.\r\n\r\nHence the package name has additional validation on Data stream page to\r\nrestrict it to start with an alphabet or underscore instead.\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] 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":"9c87ded7d1e1f5c9fe8b3accce1beda01268d5cf"}},{"url":"https://github.com/elastic/kibana/pull/210801","number":210801,"branch":"9.0","state":"OPEN"}]}] BACKPORT--> |
||
|
Kibana Machine
|
c7cd1bb8c3
|
[8.17] [Security Solution] [Detections] Disables sorting ip ranges in value list modal (#210922) (#211007)
# Backport This will backport the following commits from `main` to `8.17`: - [[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> |
||
Alex Prozorov
|
bd4b57de68
|
[8.17] [Cloud Security] skip flaky tests (#197143) (#190967) (#210741)
# Backport This will skip the following tests in version `8.17`: - (https://github.com/elastic/kibana/issues/197143) - https://github.com/elastic/kibana/issues/190967 ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) |
||
|
elastic-renovate-prod[bot]
|
19abeec7c7
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to d74b1fd (8.17) (#210724)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `8df3ca6` -> `d74b1fd` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOC4xNyIsImxhYmVscyI6WyJUZWFtOk9wZXJhdGlvbnMiLCJiYWNrcG9ydDpza2lwIiwicmVsZWFzZV9ub3RlOnNraXAiXX0=--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
afa47d599a
|
[8.17] [Search] Increase search timeout toast lifetime to 1 week (#210576) (#210904)
# Backport This will backport the following commits from `main` to `8.17`: - [[Search] Increase search timeout toast lifetime to 1 week (#210576)](https://github.com/elastic/kibana/pull/210576) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ania Kowalska","email":"63072419+akowalska622@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T17:40:10Z","message":"[Search] Increase search timeout toast lifetime to 1 week (#210576)","sha":"7ed105d7151663966e2bb4c7b29fe3de92763a01","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Search","enhancement","loe:small","impact:medium","Team:DataDiscovery","backport:prev-major","v9.1.0"],"title":"[Search] Increase search timeout toast lifetime to 1 week","number":210576,"url":"https://github.com/elastic/kibana/pull/210576","mergeCommit":{"message":"[Search] Increase search timeout toast lifetime to 1 week (#210576)","sha":"7ed105d7151663966e2bb4c7b29fe3de92763a01"}},"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/210576","number":210576,"mergeCommit":{"message":"[Search] Increase search timeout toast lifetime to 1 week (#210576)","sha":"7ed105d7151663966e2bb4c7b29fe3de92763a01"}}]}] BACKPORT--> Co-authored-by: Ania Kowalska <63072419+akowalska622@users.noreply.github.com> |
||
|
Kibana Machine
|
aa116585c5
|
[8.17] Update dependency polished to v4 (main) (#206220) (#210897)
# Backport This will backport the following commits from `main` to `8.17`: - [Update dependency polished to v4 (main) (#206220)](https://github.com/elastic/kibana/pull/206220) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-02-12T17:33:46Z","message":"Update dependency polished to v4 (main) (#206220)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [polished](https://polished.js.org)\n([source](https://togithub.com/styled-components/polished)) |\ndependencies | major | [`^3.7.2` ->\n`^4.3.1`](https://renovatebot.com/diffs/npm/polished/3.7.2/4.3.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>styled-components/polished (polished)</summary>\n\n###\n[`v4.3.1`](https://togithub.com/styled-components/polished/releases/tag/v4.3.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.3.0...v4.3.1)\n\n### Bug Fixes & Improvements\n\n- Remove annotate-pure-calls plugin to address incompatibility with\nlater versions of rollup.\n- Update dependencies.\n\n###\n[`v4.3.0`](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n###\n[`v4.2.2`](https://togithub.com/styled-components/polished/releases/tag/v4.2.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.1...v4.2.2)\n\n### Bug Fixes\n\n- **Color Modules** - addresses an issue with longer floats in color\nvalues.\n([#​610](https://togithub.com/styled-components/polished/issues/610)\n- Thanks to [@​levymetal](https://togithub.com/levymetal))\n\n###\n[`v4.2.1`](https://togithub.com/styled-components/polished/releases/tag/v4.2.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.0...v4.2.1)\n\n### Bug Fixes\n\n- **`hls(a)`** - now properly parses percentages for opacity.\n- **`rgb(a)`** - now properly parses percentages for opacity.\n\n###\n[`v4.2.0`](https://togithub.com/styled-components/polished/releases/tag/v4.2.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.4...v4.2.0)\n\n### Improvements\n\n- **color Modules** - now support space-separated CSS color values for\nrgb(a) and hsl(a).\n([#​605](https://togithub.com/styled-components/polished/issues/605))\n- **`rgb`** - now accepts optional opacity value.\n- **`hsl`** - now accepts optional opacity value.\n\n###\n[`v4.1.4`](https://togithub.com/styled-components/polished/releases/tag/v4.1.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.3...v4.1.4)\n\n### Bug Fixes\n\n- **mix** - remove unnecessary division by 1\n([#​59](https://togithub.com/styled-components/polished/issues/59))\n\n###\n[`v4.1.3`](https://togithub.com/styled-components/polished/releases/tag/v4.1.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.2...v4.1.3)\n\n### Bug Fixes\n\n- Addressed several performance issues with regexes.\n\n###\n[`v4.1.2`](https://togithub.com/styled-components/polished/releases/tag/v4.1.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.1...v4.1.2)\n\n### Bug Fixes\n\n- **fluidRange** - updated return value to use an array to address\nunclear object property typing error in flow.\n\n###\n[`v4.1.1`](https://togithub.com/styled-components/polished/releases/tag/v4.1.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.0...v4.1.1)\n\n### Bug Fixes\n\n- **scarf** - removed scarf analytics package due to yarn\nincompatibilities and concerns over GDPR compliance.\n\n###\n[`v4.1.0`](https://togithub.com/styled-components/polished/releases/tag/v4.1.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.5...v4.1.0)\n\n### Introducing polished.js v4.1.0!\n\nWe're super stoked to announce that polished.js v4.1.0 is officially\nout! It is available via your package manager of choice. This will be\nthe final non-patch release before v5.\n\n`npm install polished`\n`yarn add polished`\n\n#### Release Highlights\n\n##### New Module\n\n- **`remToPx`**: We've introduced a new module to handle converting to\n`rem` values to `px` values.\n([#​376](https://togithub.com/styled-components/polished/issues/376))\n\n##### Analytics\n\n- We are now leveraging [Scarf](https://scarf.sh) to track package\nanalytics. You can opt-out of this functionality by following [these\ninstructions](https://docs.scarf.sh/package-analytics/#as-a-user-of-a-package-using-scarf-js-how-can-i-opt-out-of-analytics)\n\n###\n[`v4.0.5`](https://togithub.com/styled-components/polished/releases/tag/v4.0.5)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.4...v4.0.5)\n\n#### Documentation\n\n- `readableColor` - Update docs and function signature to be clearer\nabout the use of each parameter.\n\n###\n[`v4.0.4`](https://togithub.com/styled-components/polished/releases/tag/v4.0.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.3...v4.0.4)\n\n### Bug Fixes\n\n- **transparentize** - addressed an issue where we weren't handling\ncases where floats were greater than 2 decimals.\n([#​548](https://togithub.com/styled-components/polished/issues/548))\n- **npm** - addressed an issue where .yarn cache was bloating published\npackage size, along with some other ignore optimization.\n([#​553](https://togithub.com/styled-components/polished/issues/553)\nThanks [@​scttcper](https://togithub.com/scttcper))\n\n###\n[`v4.0.3`](https://togithub.com/styled-components/polished/releases/tag/v4.0.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.2...v4.0.3)\n\n### Bug Fix\n\n- Updated [@​babel/runtime](https://togithub.com/babel/runtime) to\naddress webpack v5 compatibility issue (Thanks\n[@​koba04](https://togithub.com/koba04) -\n[#​547](https://togithub.com/styled-components/polished/issues/547)\n)\n\n###\n[`v4.0.2`](https://togithub.com/styled-components/polished/releases/tag/v4.0.2)\n\n### Bug Fix\n\n- `ellipsis`: Fixes an issue where the `webkit` prefix was not properly\napplied with the multiline option. (Thanks\n[@​drakang4](https://togithub.com/drakang4) -\n[#​546](https://togithub.com/styled-components/polished/issues/546))\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://togithub.com/renovatebot/renovate).\n\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOlNoYXJlZFVYIiwiYmFja3BvcnQ6YWxsLW9wZW4iLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"a402f4e584165b44d03b4773b1158b83e9b94551","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:SharedUX","backport:all-open","v9.1.0"],"title":"Update dependency polished to v4 (main)","number":206220,"url":"https://github.com/elastic/kibana/pull/206220","mergeCommit":{"message":"Update dependency polished to v4 (main) (#206220)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [polished](https://polished.js.org)\n([source](https://togithub.com/styled-components/polished)) |\ndependencies | major | [`^3.7.2` ->\n`^4.3.1`](https://renovatebot.com/diffs/npm/polished/3.7.2/4.3.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>styled-components/polished (polished)</summary>\n\n###\n[`v4.3.1`](https://togithub.com/styled-components/polished/releases/tag/v4.3.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.3.0...v4.3.1)\n\n### Bug Fixes & Improvements\n\n- Remove annotate-pure-calls plugin to address incompatibility with\nlater versions of rollup.\n- Update dependencies.\n\n###\n[`v4.3.0`](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n###\n[`v4.2.2`](https://togithub.com/styled-components/polished/releases/tag/v4.2.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.1...v4.2.2)\n\n### Bug Fixes\n\n- **Color Modules** - addresses an issue with longer floats in color\nvalues.\n([#​610](https://togithub.com/styled-components/polished/issues/610)\n- Thanks to [@​levymetal](https://togithub.com/levymetal))\n\n###\n[`v4.2.1`](https://togithub.com/styled-components/polished/releases/tag/v4.2.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.0...v4.2.1)\n\n### Bug Fixes\n\n- **`hls(a)`** - now properly parses percentages for opacity.\n- **`rgb(a)`** - now properly parses percentages for opacity.\n\n###\n[`v4.2.0`](https://togithub.com/styled-components/polished/releases/tag/v4.2.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.4...v4.2.0)\n\n### Improvements\n\n- **color Modules** - now support space-separated CSS color values for\nrgb(a) and hsl(a).\n([#​605](https://togithub.com/styled-components/polished/issues/605))\n- **`rgb`** - now accepts optional opacity value.\n- **`hsl`** - now accepts optional opacity value.\n\n###\n[`v4.1.4`](https://togithub.com/styled-components/polished/releases/tag/v4.1.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.3...v4.1.4)\n\n### Bug Fixes\n\n- **mix** - remove unnecessary division by 1\n([#​59](https://togithub.com/styled-components/polished/issues/59))\n\n###\n[`v4.1.3`](https://togithub.com/styled-components/polished/releases/tag/v4.1.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.2...v4.1.3)\n\n### Bug Fixes\n\n- Addressed several performance issues with regexes.\n\n###\n[`v4.1.2`](https://togithub.com/styled-components/polished/releases/tag/v4.1.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.1...v4.1.2)\n\n### Bug Fixes\n\n- **fluidRange** - updated return value to use an array to address\nunclear object property typing error in flow.\n\n###\n[`v4.1.1`](https://togithub.com/styled-components/polished/releases/tag/v4.1.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.0...v4.1.1)\n\n### Bug Fixes\n\n- **scarf** - removed scarf analytics package due to yarn\nincompatibilities and concerns over GDPR compliance.\n\n###\n[`v4.1.0`](https://togithub.com/styled-components/polished/releases/tag/v4.1.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.5...v4.1.0)\n\n### Introducing polished.js v4.1.0!\n\nWe're super stoked to announce that polished.js v4.1.0 is officially\nout! It is available via your package manager of choice. This will be\nthe final non-patch release before v5.\n\n`npm install polished`\n`yarn add polished`\n\n#### Release Highlights\n\n##### New Module\n\n- **`remToPx`**: We've introduced a new module to handle converting to\n`rem` values to `px` values.\n([#​376](https://togithub.com/styled-components/polished/issues/376))\n\n##### Analytics\n\n- We are now leveraging [Scarf](https://scarf.sh) to track package\nanalytics. You can opt-out of this functionality by following [these\ninstructions](https://docs.scarf.sh/package-analytics/#as-a-user-of-a-package-using-scarf-js-how-can-i-opt-out-of-analytics)\n\n###\n[`v4.0.5`](https://togithub.com/styled-components/polished/releases/tag/v4.0.5)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.4...v4.0.5)\n\n#### Documentation\n\n- `readableColor` - Update docs and function signature to be clearer\nabout the use of each parameter.\n\n###\n[`v4.0.4`](https://togithub.com/styled-components/polished/releases/tag/v4.0.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.3...v4.0.4)\n\n### Bug Fixes\n\n- **transparentize** - addressed an issue where we weren't handling\ncases where floats were greater than 2 decimals.\n([#​548](https://togithub.com/styled-components/polished/issues/548))\n- **npm** - addressed an issue where .yarn cache was bloating published\npackage size, along with some other ignore optimization.\n([#​553](https://togithub.com/styled-components/polished/issues/553)\nThanks [@​scttcper](https://togithub.com/scttcper))\n\n###\n[`v4.0.3`](https://togithub.com/styled-components/polished/releases/tag/v4.0.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.2...v4.0.3)\n\n### Bug Fix\n\n- Updated [@​babel/runtime](https://togithub.com/babel/runtime) to\naddress webpack v5 compatibility issue (Thanks\n[@​koba04](https://togithub.com/koba04) -\n[#​547](https://togithub.com/styled-components/polished/issues/547)\n)\n\n###\n[`v4.0.2`](https://togithub.com/styled-components/polished/releases/tag/v4.0.2)\n\n### Bug Fix\n\n- `ellipsis`: Fixes an issue where the `webkit` prefix was not properly\napplied with the multiline option. (Thanks\n[@​drakang4](https://togithub.com/drakang4) -\n[#​546](https://togithub.com/styled-components/polished/issues/546))\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://togithub.com/renovatebot/renovate).\n\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOlNoYXJlZFVYIiwiYmFja3BvcnQ6YWxsLW9wZW4iLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"a402f4e584165b44d03b4773b1158b83e9b94551"}},"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/206220","number":206220,"mergeCommit":{"message":"Update dependency polished to v4 (main) (#206220)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| [polished](https://polished.js.org)\n([source](https://togithub.com/styled-components/polished)) |\ndependencies | major | [`^3.7.2` ->\n`^4.3.1`](https://renovatebot.com/diffs/npm/polished/3.7.2/4.3.1) |\n\n---\n\n### Release Notes\n\n<details>\n<summary>styled-components/polished (polished)</summary>\n\n###\n[`v4.3.1`](https://togithub.com/styled-components/polished/releases/tag/v4.3.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.3.0...v4.3.1)\n\n### Bug Fixes & Improvements\n\n- Remove annotate-pure-calls plugin to address incompatibility with\nlater versions of rollup.\n- Update dependencies.\n\n###\n[`v4.3.0`](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.2...v4.3.0)\n\n###\n[`v4.2.2`](https://togithub.com/styled-components/polished/releases/tag/v4.2.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.1...v4.2.2)\n\n### Bug Fixes\n\n- **Color Modules** - addresses an issue with longer floats in color\nvalues.\n([#​610](https://togithub.com/styled-components/polished/issues/610)\n- Thanks to [@​levymetal](https://togithub.com/levymetal))\n\n###\n[`v4.2.1`](https://togithub.com/styled-components/polished/releases/tag/v4.2.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.2.0...v4.2.1)\n\n### Bug Fixes\n\n- **`hls(a)`** - now properly parses percentages for opacity.\n- **`rgb(a)`** - now properly parses percentages for opacity.\n\n###\n[`v4.2.0`](https://togithub.com/styled-components/polished/releases/tag/v4.2.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.4...v4.2.0)\n\n### Improvements\n\n- **color Modules** - now support space-separated CSS color values for\nrgb(a) and hsl(a).\n([#​605](https://togithub.com/styled-components/polished/issues/605))\n- **`rgb`** - now accepts optional opacity value.\n- **`hsl`** - now accepts optional opacity value.\n\n###\n[`v4.1.4`](https://togithub.com/styled-components/polished/releases/tag/v4.1.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.3...v4.1.4)\n\n### Bug Fixes\n\n- **mix** - remove unnecessary division by 1\n([#​59](https://togithub.com/styled-components/polished/issues/59))\n\n###\n[`v4.1.3`](https://togithub.com/styled-components/polished/releases/tag/v4.1.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.2...v4.1.3)\n\n### Bug Fixes\n\n- Addressed several performance issues with regexes.\n\n###\n[`v4.1.2`](https://togithub.com/styled-components/polished/releases/tag/v4.1.2)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.1...v4.1.2)\n\n### Bug Fixes\n\n- **fluidRange** - updated return value to use an array to address\nunclear object property typing error in flow.\n\n###\n[`v4.1.1`](https://togithub.com/styled-components/polished/releases/tag/v4.1.1)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.1.0...v4.1.1)\n\n### Bug Fixes\n\n- **scarf** - removed scarf analytics package due to yarn\nincompatibilities and concerns over GDPR compliance.\n\n###\n[`v4.1.0`](https://togithub.com/styled-components/polished/releases/tag/v4.1.0)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.5...v4.1.0)\n\n### Introducing polished.js v4.1.0!\n\nWe're super stoked to announce that polished.js v4.1.0 is officially\nout! It is available via your package manager of choice. This will be\nthe final non-patch release before v5.\n\n`npm install polished`\n`yarn add polished`\n\n#### Release Highlights\n\n##### New Module\n\n- **`remToPx`**: We've introduced a new module to handle converting to\n`rem` values to `px` values.\n([#​376](https://togithub.com/styled-components/polished/issues/376))\n\n##### Analytics\n\n- We are now leveraging [Scarf](https://scarf.sh) to track package\nanalytics. You can opt-out of this functionality by following [these\ninstructions](https://docs.scarf.sh/package-analytics/#as-a-user-of-a-package-using-scarf-js-how-can-i-opt-out-of-analytics)\n\n###\n[`v4.0.5`](https://togithub.com/styled-components/polished/releases/tag/v4.0.5)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.4...v4.0.5)\n\n#### Documentation\n\n- `readableColor` - Update docs and function signature to be clearer\nabout the use of each parameter.\n\n###\n[`v4.0.4`](https://togithub.com/styled-components/polished/releases/tag/v4.0.4)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.3...v4.0.4)\n\n### Bug Fixes\n\n- **transparentize** - addressed an issue where we weren't handling\ncases where floats were greater than 2 decimals.\n([#​548](https://togithub.com/styled-components/polished/issues/548))\n- **npm** - addressed an issue where .yarn cache was bloating published\npackage size, along with some other ignore optimization.\n([#​553](https://togithub.com/styled-components/polished/issues/553)\nThanks [@​scttcper](https://togithub.com/scttcper))\n\n###\n[`v4.0.3`](https://togithub.com/styled-components/polished/releases/tag/v4.0.3)\n\n[Compare\nSource](https://togithub.com/styled-components/polished/compare/v4.0.2...v4.0.3)\n\n### Bug Fix\n\n- Updated [@​babel/runtime](https://togithub.com/babel/runtime) to\naddress webpack v5 compatibility issue (Thanks\n[@​koba04](https://togithub.com/koba04) -\n[#​547](https://togithub.com/styled-components/polished/issues/547)\n)\n\n###\n[`v4.0.2`](https://togithub.com/styled-components/polished/releases/tag/v4.0.2)\n\n### Bug Fix\n\n- `ellipsis`: Fixes an issue where the `webkit` prefix was not properly\napplied with the multiline option. (Thanks\n[@​drakang4](https://togithub.com/drakang4) -\n[#​546](https://togithub.com/styled-components/polished/issues/546))\n\n</details>\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://togithub.com/renovatebot/renovate).\n\n<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJUZWFtOlNoYXJlZFVYIiwiYmFja3BvcnQ6YWxsLW9wZW4iLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==-->\n\n---------\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: jennypavlova <dzheni.pavlova@elastic.co>\nCo-authored-by: Shahzad <shahzad31comp@gmail.com>","sha":"a402f4e584165b44d03b4773b1158b83e9b94551"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |