mirror of
https://github.com/elastic/kibana.git
synced 2025-04-24 17:59:23 -04:00
81937 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
e177f1576e
|
[8.x] Update dependency @redocly/cli to ^1.27.2 (main) (#207527) (#207948)
# Backport This will backport the following commits from `main` to `8.x`: - [Update dependency @redocly/cli to ^1.27.2 (main) (#207527)](https://github.com/elastic/kibana/pull/207527) <!--- 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-01-22T22:48:54Z","message":"Update dependency @redocly/cli to ^1.27.2 (main) (#207527)","sha":"c6e9821bb8ec6a5705f765b5734cdb7c2a429267","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor"],"title":"Update dependency @redocly/cli to ^1.27.2 (main)","number":207527,"url":"https://github.com/elastic/kibana/pull/207527","mergeCommit":{"message":"Update dependency @redocly/cli to ^1.27.2 (main) (#207527)","sha":"c6e9821bb8ec6a5705f765b5734cdb7c2a429267"}},"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/207527","number":207527,"mergeCommit":{"message":"Update dependency @redocly/cli to ^1.27.2 (main) (#207527)","sha":"c6e9821bb8ec6a5705f765b5734cdb7c2a429267"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
fbc7d7f6e4
|
[8.x] [ResponseOps][Cases]Fix unit tests for React@18 (#207072) (#207848)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps][Cases]Fix unit tests for React@18 (#207072)](https://github.com/elastic/kibana/pull/207072) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Georgiana-Andreea Onoleață","email":"georgiana.onoleata@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T14:48:32Z","message":"[ResponseOps][Cases]Fix unit tests for React@18 (#207072)\n\nCloses https://github.com/elastic/kibana/issues/206954\r\n\r\n## Summary\r\n\r\n- fixed\r\n\r\n-\r\n[[job]]( |
||
Sean Story
|
3fde9d6ae9
|
check for active fleet servers (#207920)
## Summary The Upgrade Assistant deprecations for Native Connectors -> Agentless Connectors care about if Fleet Server is _actively_ running, but it seems that the check we're using is whether one was _ever_ running. This change introduces an optional `activeOnly` param to `hasFleetServer`, and uses it for these deprecations. |
||
|
Kibana Machine
|
ae8be0d485
|
[8.x] [Response Ops] [Rule Form] Add Show Request and Add Action screens to flyout (#206154) (#207903)
# Backport This will backport the following commits from `main` to `8.x`: - [[Response Ops] [Rule Form] Add Show Request and Add Action screens to flyout (#206154)](https://github.com/elastic/kibana/pull/206154) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Zacqary Adam Xeper","email":"Zacqary@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-22T18:53:08Z","message":"[Response Ops] [Rule Form] Add Show Request and Add Action screens to flyout (#206154)\n\n## Summary\r\n\r\nPart of #195211\r\n\r\n- Adds Show Request screen to the new rule form flyout\r\n\r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"585\" alt=\"Screenshot 2025-01-10 at 1 30 15 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/72500b0d-d959-4d17-944e-a7dc0894fb98\"\r\n/>\r\n</details>\r\n\r\n- Renders the action connectors UI within the flyout instead of opening\r\na modal\r\n \r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"505\" alt=\"Screenshot 2025-01-10 at 1 28 38 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/b5b464c0-7359-43ab-bea1-93d2981a5794\"\r\n/>\r\n</details>\r\n\r\n- Duplicates the dropdown filter design from the flyout UI within the\r\naction connectors modal when displayed on a smaller screen\r\n\r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"809\" alt=\"Screenshot 2025-01-10 at 1 30 28 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/5ef28458-1b6d-4a29-961d-fbcc1640e706\"\r\n/>\r\n</details>\r\n\r\n### Implementation notes\r\n\r\nIn order to get the action connectors UI to render the same way in both\r\na modal and the flyout, without duplicating a large amount of code, I\r\nhad to introduce a little bit of complexity. Within the Rule Page, it's\r\nas simple as opening the UI inside a modal, but the flyout cannot open a\r\nsecond flyout; it has to know when and how to completely replace its own\r\ncontents.\r\n\r\n- The bulk of the action connectors UI is now moved to\r\n`<RuleActionsConnectorsBody>`. `<RuleActionsConnectorsModal>` and\r\n`<RuleFlyoutSelectConnector>` act as wrappers for this component.\r\n- The `<RuleActions>` step no longer handles rendering the connector UI,\r\nbecause it's not at a high enough level to know if it's in the\r\n`<RulePage>` or the `<RuleFlyout>`. Instead, it simply sends a signal up\r\nthe context hierarchy to `setIsConnectorsScreenVisible`.\r\n- A new context called `RuleFormScreenContext` keeps track of\r\n`isConnectorsScreenVisible`, a state for whether or not the action\r\nconnectors \"screen\" is open, regardless of whether that screen is\r\ndisplayed in a modal or a flyout.\r\n- The Rule Page uses `isConnectorsScreenVisible` to determine whether to\r\nrender the modal. This works the same way as it used to, but handled by\r\nthe `<RulePage>` instead of the `<RuleActions>` component.\r\n- The Rule Flyout uses `isConnectorsScreenVisible` to determine whether\r\nto continue to render `<RuleFlyoutBody>` or to completely replace its\r\ncontents with `<RuleFlyoutSelectConnector>`\r\n\r\nFor consistency, this PR also moves the Show Request modal/flyout screen\r\ninto the same system.\r\n\r\n### Testing\r\n\r\nTo test the new flyout, edit\r\n`packages/response-ops/rule_form/src/create_rule_form.tsx` and\r\n`packages/response-ops/rule_form/src/edit_rule_form.tsx` so that they\r\nrender `<RuleFlyout>` instead of `<RulePage>`.\r\n\r\n<details>\r\n<summary><strong>Use this diff block</strong></summary>\r\n\r\n```diff\r\ndiff --git a/packages/response-ops/rule_form/src/create_rule_form.tsx b/packages/response-ops/rule_form/src/create_rule_form.tsx\r\nindex 2f5e0472dcd..564744b96ec 100644\r\n--- a/packages/response-ops/rule_form/src/create_rule_form.tsx\r\n+++ b/packages/response-ops/rule_form/src/create_rule_form.tsx\r\n@@ -31,6 +31,7 @@ import {\r\n parseRuleCircuitBreakerErrorMessage,\r\n } from './utils';\r\n import { RULE_CREATE_SUCCESS_TEXT, RULE_CREATE_ERROR_TEXT } from './translations';\r\n+import { RuleFlyout } from './rule_flyout';\r\n \r\n export interface CreateRuleFormProps {\r\n ruleTypeId: string;\r\n@@ -199,7 +200,7 @@ export const CreateRuleForm = (props: CreateRuleFormProps) => {\r\n }),\r\n }}\r\n >\r\n- <RulePage isEdit={false} isSaving={isSaving} onCancel={onCancel} onSave={onSave} />\r\n+ <RuleFlyout isEdit={false} isSaving={isSaving} onCancel={onCancel} onSave={onSave} />\r\n </RuleFormStateProvider>\r\n </div>\r\n );\r\ndiff --git a/packages/response-ops/rule_form/src/edit_rule_form.tsx b/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\nindex 392447114ed..41aecd7245a 100644\r\n--- a/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\n+++ b/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\n@@ -26,6 +26,7 @@ import {\r\n import { RULE_EDIT_ERROR_TEXT, RULE_EDIT_SUCCESS_TEXT } from './translations';\r\n import { getAvailableRuleTypes, parseRuleCircuitBreakerErrorMessage } from './utils';\r\n import { DEFAULT_VALID_CONSUMERS, getDefaultFormData } from './constants';\r\n+import { RuleFlyout } from './rule_flyout';\r\n \r\n export interface EditRuleFormProps {\r\n id: string;\r\n@@ -193,7 +194,7 @@ export const EditRuleForm = (props: EditRuleFormProps) => {\r\n showMustacheAutocompleteSwitch,\r\n }}\r\n >\r\n- <RulePage isEdit={true} isSaving={isSaving} onSave={onSave} onCancel={onCancel} />\r\n+ <RuleFlyout isEdit={true} isSaving={isSaving} onSave={onSave} onCancel={onCancel} />\r\n </RuleFormStateProvider>\r\n </div>\r\n );\r\n```\r\n\r\n</details>\r\n\r\n### Still Todo\r\n\r\n1. Replace all instances of the v1 rule flyout with this new one (it's\r\nused heavily in solutions, not in Stack Management)\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8004e3e70ad63b938d724eafd561533eeb225cd9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesManagement","backport:version","v8.18.0"],"title":"[Response Ops] [Rule Form] Add Show Request and Add Action screens to flyout","number":206154,"url":"https://github.com/elastic/kibana/pull/206154","mergeCommit":{"message":"[Response Ops] [Rule Form] Add Show Request and Add Action screens to flyout (#206154)\n\n## Summary\r\n\r\nPart of #195211\r\n\r\n- Adds Show Request screen to the new rule form flyout\r\n\r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"585\" alt=\"Screenshot 2025-01-10 at 1 30 15 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/72500b0d-d959-4d17-944e-a7dc0894fb98\"\r\n/>\r\n</details>\r\n\r\n- Renders the action connectors UI within the flyout instead of opening\r\na modal\r\n \r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"505\" alt=\"Screenshot 2025-01-10 at 1 28 38 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/b5b464c0-7359-43ab-bea1-93d2981a5794\"\r\n/>\r\n</details>\r\n\r\n- Duplicates the dropdown filter design from the flyout UI within the\r\naction connectors modal when displayed on a smaller screen\r\n\r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"809\" alt=\"Screenshot 2025-01-10 at 1 30 28 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/5ef28458-1b6d-4a29-961d-fbcc1640e706\"\r\n/>\r\n</details>\r\n\r\n### Implementation notes\r\n\r\nIn order to get the action connectors UI to render the same way in both\r\na modal and the flyout, without duplicating a large amount of code, I\r\nhad to introduce a little bit of complexity. Within the Rule Page, it's\r\nas simple as opening the UI inside a modal, but the flyout cannot open a\r\nsecond flyout; it has to know when and how to completely replace its own\r\ncontents.\r\n\r\n- The bulk of the action connectors UI is now moved to\r\n`<RuleActionsConnectorsBody>`. `<RuleActionsConnectorsModal>` and\r\n`<RuleFlyoutSelectConnector>` act as wrappers for this component.\r\n- The `<RuleActions>` step no longer handles rendering the connector UI,\r\nbecause it's not at a high enough level to know if it's in the\r\n`<RulePage>` or the `<RuleFlyout>`. Instead, it simply sends a signal up\r\nthe context hierarchy to `setIsConnectorsScreenVisible`.\r\n- A new context called `RuleFormScreenContext` keeps track of\r\n`isConnectorsScreenVisible`, a state for whether or not the action\r\nconnectors \"screen\" is open, regardless of whether that screen is\r\ndisplayed in a modal or a flyout.\r\n- The Rule Page uses `isConnectorsScreenVisible` to determine whether to\r\nrender the modal. This works the same way as it used to, but handled by\r\nthe `<RulePage>` instead of the `<RuleActions>` component.\r\n- The Rule Flyout uses `isConnectorsScreenVisible` to determine whether\r\nto continue to render `<RuleFlyoutBody>` or to completely replace its\r\ncontents with `<RuleFlyoutSelectConnector>`\r\n\r\nFor consistency, this PR also moves the Show Request modal/flyout screen\r\ninto the same system.\r\n\r\n### Testing\r\n\r\nTo test the new flyout, edit\r\n`packages/response-ops/rule_form/src/create_rule_form.tsx` and\r\n`packages/response-ops/rule_form/src/edit_rule_form.tsx` so that they\r\nrender `<RuleFlyout>` instead of `<RulePage>`.\r\n\r\n<details>\r\n<summary><strong>Use this diff block</strong></summary>\r\n\r\n```diff\r\ndiff --git a/packages/response-ops/rule_form/src/create_rule_form.tsx b/packages/response-ops/rule_form/src/create_rule_form.tsx\r\nindex 2f5e0472dcd..564744b96ec 100644\r\n--- a/packages/response-ops/rule_form/src/create_rule_form.tsx\r\n+++ b/packages/response-ops/rule_form/src/create_rule_form.tsx\r\n@@ -31,6 +31,7 @@ import {\r\n parseRuleCircuitBreakerErrorMessage,\r\n } from './utils';\r\n import { RULE_CREATE_SUCCESS_TEXT, RULE_CREATE_ERROR_TEXT } from './translations';\r\n+import { RuleFlyout } from './rule_flyout';\r\n \r\n export interface CreateRuleFormProps {\r\n ruleTypeId: string;\r\n@@ -199,7 +200,7 @@ export const CreateRuleForm = (props: CreateRuleFormProps) => {\r\n }),\r\n }}\r\n >\r\n- <RulePage isEdit={false} isSaving={isSaving} onCancel={onCancel} onSave={onSave} />\r\n+ <RuleFlyout isEdit={false} isSaving={isSaving} onCancel={onCancel} onSave={onSave} />\r\n </RuleFormStateProvider>\r\n </div>\r\n );\r\ndiff --git a/packages/response-ops/rule_form/src/edit_rule_form.tsx b/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\nindex 392447114ed..41aecd7245a 100644\r\n--- a/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\n+++ b/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\n@@ -26,6 +26,7 @@ import {\r\n import { RULE_EDIT_ERROR_TEXT, RULE_EDIT_SUCCESS_TEXT } from './translations';\r\n import { getAvailableRuleTypes, parseRuleCircuitBreakerErrorMessage } from './utils';\r\n import { DEFAULT_VALID_CONSUMERS, getDefaultFormData } from './constants';\r\n+import { RuleFlyout } from './rule_flyout';\r\n \r\n export interface EditRuleFormProps {\r\n id: string;\r\n@@ -193,7 +194,7 @@ export const EditRuleForm = (props: EditRuleFormProps) => {\r\n showMustacheAutocompleteSwitch,\r\n }}\r\n >\r\n- <RulePage isEdit={true} isSaving={isSaving} onSave={onSave} onCancel={onCancel} />\r\n+ <RuleFlyout isEdit={true} isSaving={isSaving} onSave={onSave} onCancel={onCancel} />\r\n </RuleFormStateProvider>\r\n </div>\r\n );\r\n```\r\n\r\n</details>\r\n\r\n### Still Todo\r\n\r\n1. Replace all instances of the v1 rule flyout with this new one (it's\r\nused heavily in solutions, not in Stack Management)\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8004e3e70ad63b938d724eafd561533eeb225cd9"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206154","number":206154,"mergeCommit":{"message":"[Response Ops] [Rule Form] Add Show Request and Add Action screens to flyout (#206154)\n\n## Summary\r\n\r\nPart of #195211\r\n\r\n- Adds Show Request screen to the new rule form flyout\r\n\r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"585\" alt=\"Screenshot 2025-01-10 at 1 30 15 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/72500b0d-d959-4d17-944e-a7dc0894fb98\"\r\n/>\r\n</details>\r\n\r\n- Renders the action connectors UI within the flyout instead of opening\r\na modal\r\n \r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"505\" alt=\"Screenshot 2025-01-10 at 1 28 38 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/b5b464c0-7359-43ab-bea1-93d2981a5794\"\r\n/>\r\n</details>\r\n\r\n- Duplicates the dropdown filter design from the flyout UI within the\r\naction connectors modal when displayed on a smaller screen\r\n\r\n<details>\r\n<summary>Screenshot</summary>\r\n<img width=\"809\" alt=\"Screenshot 2025-01-10 at 1 30 28 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/5ef28458-1b6d-4a29-961d-fbcc1640e706\"\r\n/>\r\n</details>\r\n\r\n### Implementation notes\r\n\r\nIn order to get the action connectors UI to render the same way in both\r\na modal and the flyout, without duplicating a large amount of code, I\r\nhad to introduce a little bit of complexity. Within the Rule Page, it's\r\nas simple as opening the UI inside a modal, but the flyout cannot open a\r\nsecond flyout; it has to know when and how to completely replace its own\r\ncontents.\r\n\r\n- The bulk of the action connectors UI is now moved to\r\n`<RuleActionsConnectorsBody>`. `<RuleActionsConnectorsModal>` and\r\n`<RuleFlyoutSelectConnector>` act as wrappers for this component.\r\n- The `<RuleActions>` step no longer handles rendering the connector UI,\r\nbecause it's not at a high enough level to know if it's in the\r\n`<RulePage>` or the `<RuleFlyout>`. Instead, it simply sends a signal up\r\nthe context hierarchy to `setIsConnectorsScreenVisible`.\r\n- A new context called `RuleFormScreenContext` keeps track of\r\n`isConnectorsScreenVisible`, a state for whether or not the action\r\nconnectors \"screen\" is open, regardless of whether that screen is\r\ndisplayed in a modal or a flyout.\r\n- The Rule Page uses `isConnectorsScreenVisible` to determine whether to\r\nrender the modal. This works the same way as it used to, but handled by\r\nthe `<RulePage>` instead of the `<RuleActions>` component.\r\n- The Rule Flyout uses `isConnectorsScreenVisible` to determine whether\r\nto continue to render `<RuleFlyoutBody>` or to completely replace its\r\ncontents with `<RuleFlyoutSelectConnector>`\r\n\r\nFor consistency, this PR also moves the Show Request modal/flyout screen\r\ninto the same system.\r\n\r\n### Testing\r\n\r\nTo test the new flyout, edit\r\n`packages/response-ops/rule_form/src/create_rule_form.tsx` and\r\n`packages/response-ops/rule_form/src/edit_rule_form.tsx` so that they\r\nrender `<RuleFlyout>` instead of `<RulePage>`.\r\n\r\n<details>\r\n<summary><strong>Use this diff block</strong></summary>\r\n\r\n```diff\r\ndiff --git a/packages/response-ops/rule_form/src/create_rule_form.tsx b/packages/response-ops/rule_form/src/create_rule_form.tsx\r\nindex 2f5e0472dcd..564744b96ec 100644\r\n--- a/packages/response-ops/rule_form/src/create_rule_form.tsx\r\n+++ b/packages/response-ops/rule_form/src/create_rule_form.tsx\r\n@@ -31,6 +31,7 @@ import {\r\n parseRuleCircuitBreakerErrorMessage,\r\n } from './utils';\r\n import { RULE_CREATE_SUCCESS_TEXT, RULE_CREATE_ERROR_TEXT } from './translations';\r\n+import { RuleFlyout } from './rule_flyout';\r\n \r\n export interface CreateRuleFormProps {\r\n ruleTypeId: string;\r\n@@ -199,7 +200,7 @@ export const CreateRuleForm = (props: CreateRuleFormProps) => {\r\n }),\r\n }}\r\n >\r\n- <RulePage isEdit={false} isSaving={isSaving} onCancel={onCancel} onSave={onSave} />\r\n+ <RuleFlyout isEdit={false} isSaving={isSaving} onCancel={onCancel} onSave={onSave} />\r\n </RuleFormStateProvider>\r\n </div>\r\n );\r\ndiff --git a/packages/response-ops/rule_form/src/edit_rule_form.tsx b/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\nindex 392447114ed..41aecd7245a 100644\r\n--- a/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\n+++ b/packages/response-ops/rule_form/src/edit_rule_form.tsx\r\n@@ -26,6 +26,7 @@ import {\r\n import { RULE_EDIT_ERROR_TEXT, RULE_EDIT_SUCCESS_TEXT } from './translations';\r\n import { getAvailableRuleTypes, parseRuleCircuitBreakerErrorMessage } from './utils';\r\n import { DEFAULT_VALID_CONSUMERS, getDefaultFormData } from './constants';\r\n+import { RuleFlyout } from './rule_flyout';\r\n \r\n export interface EditRuleFormProps {\r\n id: string;\r\n@@ -193,7 +194,7 @@ export const EditRuleForm = (props: EditRuleFormProps) => {\r\n showMustacheAutocompleteSwitch,\r\n }}\r\n >\r\n- <RulePage isEdit={true} isSaving={isSaving} onSave={onSave} onCancel={onCancel} />\r\n+ <RuleFlyout isEdit={true} isSaving={isSaving} onSave={onSave} onCancel={onCancel} />\r\n </RuleFormStateProvider>\r\n </div>\r\n );\r\n```\r\n\r\n</details>\r\n\r\n### Still Todo\r\n\r\n1. Replace all instances of the v1 rule flyout with this new one (it's\r\nused heavily in solutions, not in Stack Management)\r\n\r\n### Checklist\r\n\r\n- [x] Any text added follows [EUI's writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\r\nsentence case text and includes [i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"8004e3e70ad63b938d724eafd561533eeb225cd9"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Zacqary Adam Xeper <Zacqary@users.noreply.github.com> |
||
Tiago Costa
|
14b57223c4
|
skip flaky suite (#204381) | ||
|
Tiago Costa
|
d13cefd7c7
|
skip flaky suite (#205953) | ||
Nikita Indik
|
e69e783724
|
[8.x] [Security Solution] Show deprecated bulk endpoints in Upgrade Assistant (#207091) (#207882)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] Show deprecated bulk endpoints in Upgrade Assistant (#207091)](https://github.com/elastic/kibana/pull/207091) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Nikita Indik","email":"nikita.indik@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:36:24Z","message":"[Security Solution] Show deprecated bulk endpoints in Upgrade Assistant (#207091)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/193184**\n\n## Summary\nWe are going to remove our deprecated [bulk action\nendpoints](https://github.com/elastic/kibana/issues/193184) in v9.0.0.\nThey are already unavailable in `main`.\n\nThis PR makes deprecated bulk endpoints visible in Upgrade Assistant.\nAlso, it adds an upgrade guide to the documentation to help users\ntransition to supported endpoints.\n\n⚠️ This PR temporarily adds the deprecated endpoints back to\n`register_routes.ts`. This is needed to make merging changes easier.\nI'll open up a follow up PR for `main` that will delete these endpoints\nfrom `9.0`. Will do it once this PR is merged.\n\n## Screenshots\n**Deprecated endpoints visible in Upgrade Assistant table**\n<img width=\"1276\" alt=\"Schermafbeelding 2025-01-21 om 11 27 53\"\nsrc=\"https://github.com/user-attachments/assets/909c7a20-31d9-46bb-89ec-b409550074e4\"\n/>\n\n**Clicking on a table item opens a flyout with more info**\n<table>\n <tr>\n <td>\n<img width=\"1270\" alt=\"patch_update\"\nsrc=\"https://github.com/user-attachments/assets/8e99459d-1ea1-40c4-936c-23074c02cd6f\"\n/>\n </td>\n <td>\n<img width=\"1270\" alt=\"post_create\"\nsrc=\"https://github.com/user-attachments/assets/6e734e97-4cf4-4d96-9f8d-51efeb3977ad\"\n/>\n </td>\n </tr>\n <tr>\n <td>\n<img width=\"1270\" alt=\"put_update\"\nsrc=\"https://github.com/user-attachments/assets/d5b08e16-bf49-475d-81a9-fe5654483e1d\"\n/>\n </td>\n <td>\n<img width=\"1271\" alt=\"post_delete\"\nsrc=\"https://github.com/user-attachments/assets/ccb74552-50a4-4bdb-b04e-06857caa8f38\"\n/>\n </td>\n </tr>\n</table>\n\n**Clicking on \"Learn more\" in the flyout takes you to the [upgrade\nguide](https://kibana_bk_207091.docs-preview.app.elstc.co/guide/en/kibana/master/breaking-changes-summary.html#breaking-207091)**\n<img width=\"731\" alt=\"upgrade_notes\"\nsrc=\"https://github.com/user-attachments/assets/b8b471ea-98c7-4b07-91db-b1630c382554\"\n/>\n\n\n## Testing\nOnce you send a request to one of the deprecated endpoints it should\nshow up in Upgrade Assistant at\n`<basePath>/app/management/stack/upgrade_assistant/kibana_deprecations`.\nPlease refer to [this\nticket](https://github.com/elastic/kibana/issues/193184) for the list of\ndeprecated endpoints.\n\nWork started on: 16-Jan-2025","sha":"33145379e57825f022dffa8405ded308d5eba8d0","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Detections and Resp","Team: SecuritySolution","Feature:Rule Management","Team:Detection Rule Management","ui-copy","ci:cloud-deploy","ci:project-deploy-security","backport:version","v8.18.0"],"title":"[Security Solution] Show deprecated bulk endpoints in Upgrade Assistant","number":207091,"url":"https://github.com/elastic/kibana/pull/207091","mergeCommit":{"message":"[Security Solution] Show deprecated bulk endpoints in Upgrade Assistant (#207091)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/193184**\n\n## Summary\nWe are going to remove our deprecated [bulk action\nendpoints](https://github.com/elastic/kibana/issues/193184) in v9.0.0.\nThey are already unavailable in `main`.\n\nThis PR makes deprecated bulk endpoints visible in Upgrade Assistant.\nAlso, it adds an upgrade guide to the documentation to help users\ntransition to supported endpoints.\n\n⚠️ This PR temporarily adds the deprecated endpoints back to\n`register_routes.ts`. This is needed to make merging changes easier.\nI'll open up a follow up PR for `main` that will delete these endpoints\nfrom `9.0`. Will do it once this PR is merged.\n\n## Screenshots\n**Deprecated endpoints visible in Upgrade Assistant table**\n<img width=\"1276\" alt=\"Schermafbeelding 2025-01-21 om 11 27 53\"\nsrc=\"https://github.com/user-attachments/assets/909c7a20-31d9-46bb-89ec-b409550074e4\"\n/>\n\n**Clicking on a table item opens a flyout with more info**\n<table>\n <tr>\n <td>\n<img width=\"1270\" alt=\"patch_update\"\nsrc=\"https://github.com/user-attachments/assets/8e99459d-1ea1-40c4-936c-23074c02cd6f\"\n/>\n </td>\n <td>\n<img width=\"1270\" alt=\"post_create\"\nsrc=\"https://github.com/user-attachments/assets/6e734e97-4cf4-4d96-9f8d-51efeb3977ad\"\n/>\n </td>\n </tr>\n <tr>\n <td>\n<img width=\"1270\" alt=\"put_update\"\nsrc=\"https://github.com/user-attachments/assets/d5b08e16-bf49-475d-81a9-fe5654483e1d\"\n/>\n </td>\n <td>\n<img width=\"1271\" alt=\"post_delete\"\nsrc=\"https://github.com/user-attachments/assets/ccb74552-50a4-4bdb-b04e-06857caa8f38\"\n/>\n </td>\n </tr>\n</table>\n\n**Clicking on \"Learn more\" in the flyout takes you to the [upgrade\nguide](https://kibana_bk_207091.docs-preview.app.elstc.co/guide/en/kibana/master/breaking-changes-summary.html#breaking-207091)**\n<img width=\"731\" alt=\"upgrade_notes\"\nsrc=\"https://github.com/user-attachments/assets/b8b471ea-98c7-4b07-91db-b1630c382554\"\n/>\n\n\n## Testing\nOnce you send a request to one of the deprecated endpoints it should\nshow up in Upgrade Assistant at\n`<basePath>/app/management/stack/upgrade_assistant/kibana_deprecations`.\nPlease refer to [this\nticket](https://github.com/elastic/kibana/issues/193184) for the list of\ndeprecated endpoints.\n\nWork started on: 16-Jan-2025","sha":"33145379e57825f022dffa8405ded308d5eba8d0"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207091","number":207091,"mergeCommit":{"message":"[Security Solution] Show deprecated bulk endpoints in Upgrade Assistant (#207091)\n\n**Partially addresses: https://github.com/elastic/kibana/issues/193184**\n\n## Summary\nWe are going to remove our deprecated [bulk action\nendpoints](https://github.com/elastic/kibana/issues/193184) in v9.0.0.\nThey are already unavailable in `main`.\n\nThis PR makes deprecated bulk endpoints visible in Upgrade Assistant.\nAlso, it adds an upgrade guide to the documentation to help users\ntransition to supported endpoints.\n\n⚠️ This PR temporarily adds the deprecated endpoints back to\n`register_routes.ts`. This is needed to make merging changes easier.\nI'll open up a follow up PR for `main` that will delete these endpoints\nfrom `9.0`. Will do it once this PR is merged.\n\n## Screenshots\n**Deprecated endpoints visible in Upgrade Assistant table**\n<img width=\"1276\" alt=\"Schermafbeelding 2025-01-21 om 11 27 53\"\nsrc=\"https://github.com/user-attachments/assets/909c7a20-31d9-46bb-89ec-b409550074e4\"\n/>\n\n**Clicking on a table item opens a flyout with more info**\n<table>\n <tr>\n <td>\n<img width=\"1270\" alt=\"patch_update\"\nsrc=\"https://github.com/user-attachments/assets/8e99459d-1ea1-40c4-936c-23074c02cd6f\"\n/>\n </td>\n <td>\n<img width=\"1270\" alt=\"post_create\"\nsrc=\"https://github.com/user-attachments/assets/6e734e97-4cf4-4d96-9f8d-51efeb3977ad\"\n/>\n </td>\n </tr>\n <tr>\n <td>\n<img width=\"1270\" alt=\"put_update\"\nsrc=\"https://github.com/user-attachments/assets/d5b08e16-bf49-475d-81a9-fe5654483e1d\"\n/>\n </td>\n <td>\n<img width=\"1271\" alt=\"post_delete\"\nsrc=\"https://github.com/user-attachments/assets/ccb74552-50a4-4bdb-b04e-06857caa8f38\"\n/>\n </td>\n </tr>\n</table>\n\n**Clicking on \"Learn more\" in the flyout takes you to the [upgrade\nguide](https://kibana_bk_207091.docs-preview.app.elstc.co/guide/en/kibana/master/breaking-changes-summary.html#breaking-207091)**\n<img width=\"731\" alt=\"upgrade_notes\"\nsrc=\"https://github.com/user-attachments/assets/b8b471ea-98c7-4b07-91db-b1630c382554\"\n/>\n\n\n## Testing\nOnce you send a request to one of the deprecated endpoints it should\nshow up in Upgrade Assistant at\n`<basePath>/app/management/stack/upgrade_assistant/kibana_deprecations`.\nPlease refer to [this\nticket](https://github.com/elastic/kibana/issues/193184) for the list of\ndeprecated endpoints.\n\nWork started on: 16-Jan-2025","sha":"33145379e57825f022dffa8405ded308d5eba8d0"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Joe Reuter
|
e87c6e662f
|
[8.x] 🌊 Fix MKI tests (#207397) (#207900)
# Backport This will backport the following commits from `main` to `8.x`: - [🌊 Fix MKI tests (#207397)](https://github.com/elastic/kibana/pull/207397) |
||
|
Kibana Machine
|
fc9b6d2055
|
[8.x] [ResponseOps] Fix editing alerts filter for multi-consumer rule types on serverless (#206848) (#207898)
# Backport This will backport the following commits from `main` to `8.x`: - [[ResponseOps] Fix editing alerts filter for multi-consumer rule types on serverless (#206848)](https://github.com/elastic/kibana/pull/206848) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Zacqary Adam Xeper","email":"Zacqary@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-22T17:53:31Z","message":"[ResponseOps] Fix editing alerts filter for multi-consumer rule types on serverless (#206848)\n\n## Summary\r\n\r\nFixes #206845\r\n\r\nRemoves a check to see if a rule has a valid consumer before allowing\r\nalerts filters to be edited in the rule form. This was breaking editing\r\nrules on serverless.\r\n\r\nWith all relevant rule types having added alerts-as-data functionality,\r\nthis check is no longer necessary.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d6b6fdc9f97a888710f3bc8673c8b182fcb14919","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:ResponseOps","v9.0.0","Feature:Alerting/RulesManagement","backport:version","v8.18.0"],"title":"[ResponseOps] Fix editing alerts filter for multi-consumer rule types on serverless","number":206848,"url":"https://github.com/elastic/kibana/pull/206848","mergeCommit":{"message":"[ResponseOps] Fix editing alerts filter for multi-consumer rule types on serverless (#206848)\n\n## Summary\r\n\r\nFixes #206845\r\n\r\nRemoves a check to see if a rule has a valid consumer before allowing\r\nalerts filters to be edited in the rule form. This was breaking editing\r\nrules on serverless.\r\n\r\nWith all relevant rule types having added alerts-as-data functionality,\r\nthis check is no longer necessary.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d6b6fdc9f97a888710f3bc8673c8b182fcb14919"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206848","number":206848,"mergeCommit":{"message":"[ResponseOps] Fix editing alerts filter for multi-consumer rule types on serverless (#206848)\n\n## Summary\r\n\r\nFixes #206845\r\n\r\nRemoves a check to see if a rule has a valid consumer before allowing\r\nalerts filters to be edited in the rule form. This was breaking editing\r\nrules on serverless.\r\n\r\nWith all relevant rule types having added alerts-as-data functionality,\r\nthis check is no longer necessary.\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"d6b6fdc9f97a888710f3bc8673c8b182fcb14919"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Zacqary Adam Xeper <Zacqary@users.noreply.github.com> |
||
|
Kibana Machine
|
19b8dc9ad2
|
[8.x] [Security Solution] [Security Assistant] Fixes Security Assistant accessibility (a11y) issues (#207122) (#207895)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] [Security Assistant] Fixes Security Assistant accessibility (a11y) issues (#207122)](https://github.com/elastic/kibana/pull/207122) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Andrew Macri","email":"andrew.macri@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T18:06:54Z","message":"[Security Solution] [Security Assistant] Fixes Security Assistant accessibility (a11y) issues (#207122)\n\n### [Security Solution] [Security Assistant] Fixes Security Assistant accessibility (a11y) issues\r\n\r\nThis PR fixes the following Security Assistant accessibility (a11y) issues:\r\n\r\n- <https://github.com/elastic/kibana/issues/206348> - _The ai assistant settings and actions button is announced wrong_\r\n- <https://github.com/elastic/kibana/issues/206362> - _Close button on View in AI assistant is missing discernible text_\r\n- <https://github.com/elastic/kibana/issues/206875> - _Anonymization button doesn't get announced and doesn't have enough context in the tooltip about when it gets enabled_\r\n\r\n### Details\r\n\r\n#### [206348](https://github.com/elastic/kibana/issues/206348) - The ai assistant settings and actions button is announced wrong\r\n\r\nThis issue was resolved by adding an `aria-label` to the assistant settings context menu.\r\n\r\nThis fix was desk tested using Voiceover, as illustrated by the following screenshots:\r\n\r\n**Before:**\r\n\r\n (#207894)
# Backport This will backport the following commits from `main` to `8.x`: - [Upgrade Node.js to 20.18.2 (#207431)](https://github.com/elastic/kibana/pull/207431) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T18:00:14Z","message":"Upgrade Node.js to 20.18.2 (#207431)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"89b763a4996afcf380fb68f345ca6da3f08669ba","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","Team:Fleet","v9.0.0","backport:all-open"],"title":"Upgrade Node.js to 20.18.2","number":207431,"url":"https://github.com/elastic/kibana/pull/207431","mergeCommit":{"message":"Upgrade Node.js to 20.18.2 (#207431)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"89b763a4996afcf380fb68f345ca6da3f08669ba"}},"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/207431","number":207431,"mergeCommit":{"message":"Upgrade Node.js to 20.18.2 (#207431)\n\nhttps://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md","sha":"89b763a4996afcf380fb68f345ca6da3f08669ba"}}]}] BACKPORT--> Co-authored-by: Jon <jon@elastic.co> |
||
elastic-renovate-prod[bot]
|
850785ac50
|
Update ftr (8.x) (#206328)
This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [@types/selenium-webdriver](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/selenium-webdriver) ([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/selenium-webdriver)) | devDependencies | patch | [`^4.1.27` -> `^4.1.28`](https://renovatebot.com/diffs/npm/@types%2fselenium-webdriver/4.1.27/4.1.28) | | [chromedriver](https://togithub.com/giggio/node-chromedriver) | devDependencies | major | [`^131.0.1` -> `^132.0.0`](https://renovatebot.com/diffs/npm/chromedriver/131.0.1/132.0.0) | --- ### Release Notes <details> <summary>giggio/node-chromedriver (chromedriver)</summary> ### [`v132.0.0`](https://togithub.com/giggio/node-chromedriver/compare/131.0.5...132.0.0) [Compare Source](https://togithub.com/giggio/node-chromedriver/compare/131.0.5...132.0.0) ### [`v131.0.5`](https://togithub.com/giggio/node-chromedriver/compare/131.0.4...131.0.5) [Compare Source](https://togithub.com/giggio/node-chromedriver/compare/131.0.4...131.0.5) ### [`v131.0.4`](https://togithub.com/giggio/node-chromedriver/compare/131.0.3...131.0.4) [Compare Source](https://togithub.com/giggio/node-chromedriver/compare/131.0.3...131.0.4) ### [`v131.0.3`](https://togithub.com/giggio/node-chromedriver/compare/131.0.2...131.0.3) [Compare Source](https://togithub.com/giggio/node-chromedriver/compare/131.0.2...131.0.3) ### [`v131.0.2`](https://togithub.com/giggio/node-chromedriver/compare/131.0.1...131.0.2) [Compare Source](https://togithub.com/giggio/node-chromedriver/compare/131.0.1...131.0.2) </details> --- ### 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. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://togithub.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://togithub.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MjUuMSIsInVwZGF0ZWRJblZlciI6IjM3LjQyNS4xIiwidGFyZ2V0QnJhbmNoIjoiOC54IiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
550bd4d0a9
|
[8.x] [inference] openAI: fallback to manual token count when not provided in response (#207722) (#207887)
# Backport This will backport the following commits from `main` to `8.x`: - [[inference] openAI: fallback to manual token count when not provided in response (#207722)](https://github.com/elastic/kibana/pull/207722) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pierre Gayvallet","email":"pierre.gayvallet@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T17:07:05Z","message":"[inference] openAI: fallback to manual token count when not provided in response (#207722)\n\n## Summary\r\n\r\nFix https://github.com/elastic/kibana/issues/207719\r\n\r\nFor openAI providers not emitting token usage metadata for the stream\r\nAPI, manually count tokens, so that a tokenCount event is always\r\nemitted.","sha":"c087c984ff469ccb543a9dbc9a1630198afc7930","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0"],"title":"[inference] openAI: fallback to manual token count when not provided in response","number":207722,"url":"https://github.com/elastic/kibana/pull/207722","mergeCommit":{"message":"[inference] openAI: fallback to manual token count when not provided in response (#207722)\n\n## Summary\r\n\r\nFix https://github.com/elastic/kibana/issues/207719\r\n\r\nFor openAI providers not emitting token usage metadata for the stream\r\nAPI, manually count tokens, so that a tokenCount event is always\r\nemitted.","sha":"c087c984ff469ccb543a9dbc9a1630198afc7930"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207722","number":207722,"mergeCommit":{"message":"[inference] openAI: fallback to manual token count when not provided in response (#207722)\n\n## Summary\r\n\r\nFix https://github.com/elastic/kibana/issues/207719\r\n\r\nFor openAI providers not emitting token usage metadata for the stream\r\nAPI, manually count tokens, so that a tokenCount event is always\r\nemitted.","sha":"c087c984ff469ccb543a9dbc9a1630198afc7930"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pierre Gayvallet <pierre.gayvallet@elastic.co> |
||
|
Kibana Machine
|
d1f40db313
|
[8.x] [Fleet] Remove deprecated ML job property from test fixtures (#207857) (#207886)
# Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] Remove deprecated ML job property from test fixtures (#207857)](https://github.com/elastic/kibana/pull/207857) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kyle Pollich","email":"kyle.pollich@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T17:03:55Z","message":"[Fleet] Remove deprecated ML job property from test fixtures (#207857)\n\n## Summary\r\n\r\nReplace `estimated_heap_memory_usage_bytes` property with `expected\r\nmodel_size_bytes` per deprecation warning. I unzipped the fixture\r\narchives, replaced the property, and rezipped them.\r\n\r\n## To test\r\n\r\nAdd the following to your `serverArgs` block in\r\n`x-pack/test/fleet_api_integration/config.base.ts`\r\n\r\n```\r\n{\r\n name: 'elasticsearch.debug',\r\n level: 'debug',\r\n appenders: ['default'],\r\n},\r\n```\r\n\r\nRun the EPM FTR tests e.g. \r\n\r\n```\r\nFLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/fleet_api_integration/config.epm.ts \r\n\r\n# in another terminal session\r\nFLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/fleet_api_integration/config.epm.ts --grep \"Assets tagging\"\r\n```\r\n\r\nCheck that the deprecation notice does not appear in the\r\n`elasticsearch.debug` logs in your console\r\n\r\n```\r\nx-pack/test/fleet_api_integration/apis/epm/bulk_get_assets.ts: Deprecated field estimated_heap_memory_usage_bytes used, expected model_size_bytes instead\r\n```","sha":"4073aff617e1fa2fa09f9414df0e398d47159b41","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor"],"title":"[Fleet] Remove deprecated ML job property from test fixtures","number":207857,"url":"https://github.com/elastic/kibana/pull/207857","mergeCommit":{"message":"[Fleet] Remove deprecated ML job property from test fixtures (#207857)\n\n## Summary\r\n\r\nReplace `estimated_heap_memory_usage_bytes` property with `expected\r\nmodel_size_bytes` per deprecation warning. I unzipped the fixture\r\narchives, replaced the property, and rezipped them.\r\n\r\n## To test\r\n\r\nAdd the following to your `serverArgs` block in\r\n`x-pack/test/fleet_api_integration/config.base.ts`\r\n\r\n```\r\n{\r\n name: 'elasticsearch.debug',\r\n level: 'debug',\r\n appenders: ['default'],\r\n},\r\n```\r\n\r\nRun the EPM FTR tests e.g. \r\n\r\n```\r\nFLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/fleet_api_integration/config.epm.ts \r\n\r\n# in another terminal session\r\nFLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/fleet_api_integration/config.epm.ts --grep \"Assets tagging\"\r\n```\r\n\r\nCheck that the deprecation notice does not appear in the\r\n`elasticsearch.debug` logs in your console\r\n\r\n```\r\nx-pack/test/fleet_api_integration/apis/epm/bulk_get_assets.ts: Deprecated field estimated_heap_memory_usage_bytes used, expected model_size_bytes instead\r\n```","sha":"4073aff617e1fa2fa09f9414df0e398d47159b41"}},"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/207857","number":207857,"mergeCommit":{"message":"[Fleet] Remove deprecated ML job property from test fixtures (#207857)\n\n## Summary\r\n\r\nReplace `estimated_heap_memory_usage_bytes` property with `expected\r\nmodel_size_bytes` per deprecation warning. I unzipped the fixture\r\narchives, replaced the property, and rezipped them.\r\n\r\n## To test\r\n\r\nAdd the following to your `serverArgs` block in\r\n`x-pack/test/fleet_api_integration/config.base.ts`\r\n\r\n```\r\n{\r\n name: 'elasticsearch.debug',\r\n level: 'debug',\r\n appenders: ['default'],\r\n},\r\n```\r\n\r\nRun the EPM FTR tests e.g. \r\n\r\n```\r\nFLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:server --config x-pack/test/fleet_api_integration/config.epm.ts \r\n\r\n# in another terminal session\r\nFLEET_PACKAGE_REGISTRY_PORT=12345 yarn test:ftr:runner --config x-pack/test/fleet_api_integration/config.epm.ts --grep \"Assets tagging\"\r\n```\r\n\r\nCheck that the deprecation notice does not appear in the\r\n`elasticsearch.debug` logs in your console\r\n\r\n```\r\nx-pack/test/fleet_api_integration/apis/epm/bulk_get_assets.ts: Deprecated field estimated_heap_memory_usage_bytes used, expected model_size_bytes instead\r\n```","sha":"4073aff617e1fa2fa09f9414df0e398d47159b41"}}]}] BACKPORT--> Co-authored-by: Kyle Pollich <kyle.pollich@elastic.co> |
||
Nathan Reese
|
c39e129298
|
[8.x] [embeddable] make presentation interface names consistent (#205279) (#207881)
# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- 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-01-22T16:46:01Z","message":"[embeddable] make presentation interface names consistent (#205279)\n\nPR cleans up presentation interface names for consistentency\r\n* adds `# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT suffix to all observables. For example, `dataLoading` =>\r\n`dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT \r\n* removes `Panel` naming convention from interface names since an api\r\nmay not be a panel, an api may be a dashboard. For example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to Reviewers\r\nPay special attention to any place where your application creates an\r\nuntyped API. In the example below, there is no typescript violation when\r\nthe parent returns `dataLoading` instead of `dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`. Please check for\r\ninstances like these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() => {\r\n dataLoading: new BehaviorSubject()\r\n }}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Embedding","Team:Presentation","release_note:skip","Feature:Drilldowns","v9.0.0","Team:obs-ux-infra_services","Team:obs-ux-management","project:embeddableRebuild","backport:version","v8.18.0"],"title":"[embeddable] make presentation interface names consistent","number":205279,"url":"https://github.com/elastic/kibana/pull/205279","mergeCommit":{"message":"[embeddable] make presentation interface names consistent (#205279)\n\nPR cleans up presentation interface names for consistentency\r\n* adds `# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT suffix to all observables. For example, `dataLoading` =>\r\n`dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT \r\n* removes `Panel` naming convention from interface names since an api\r\nmay not be a panel, an api may be a dashboard. For example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to Reviewers\r\nPay special attention to any place where your application creates an\r\nuntyped API. In the example below, there is no typescript violation when\r\nthe parent returns `dataLoading` instead of `dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`. Please check for\r\ninstances like these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() => {\r\n dataLoading: new BehaviorSubject()\r\n }}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205279","number":205279,"mergeCommit":{"message":"[embeddable] make presentation interface names consistent (#205279)\n\nPR cleans up presentation interface names for consistentency\r\n* adds `# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT suffix to all observables. For example, `dataLoading` =>\r\n`dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT \r\n* removes `Panel` naming convention from interface names since an api\r\nmay not be a panel, an api may be a dashboard. For example,\r\n`PublisesPanelTitle` => `PublishesTitle`\r\n\r\n#### Note to Reviewers\r\nPay special attention to any place where your application creates an\r\nuntyped API. In the example below, there is no typescript violation when\r\nthe parent returns `dataLoading` instead of `dataLoading# Backport This will backport the following commits from `main` to `8.x`: - [[embeddable] make presentation interface names consistent (#205279)](https://github.com/elastic/kibana/pull/205279) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT since the\r\nparent is not typed as `PublishesDataLoading`. Please check for\r\ninstances like these.\r\n\r\n```\r\n<ReactEmbeddableRenderer\r\n getParentApi={() => {\r\n dataLoading: new BehaviorSubject()\r\n }}\r\n/>\r\n```\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"05916056cdc84c0f59392046aa4ffc7d16e083f9"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
f47f4da383
|
[8.x] Refactor models (#206930) (#207855)
# Backport This will backport the following commits from `main` to `8.x`: - [Refactor models (#206930)](https://github.com/elastic/kibana/pull/206930) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dario Gieselaar","email":"dario.gieselaar@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T15:03:08Z","message":"Refactor models (#206930)\n\nRefactors models to make it more clear what our data model is internally\nand what our API responses are. Also some small changes to make it more\nelasticsearch-y:\n\n- isSchema variants now are based on specific type narrowing instead of\nfrom any > type, as the latter only gives runtime safety, but does not\nadd much in terms of type safety\n- validation is now entirely encapsulated in the type, removed\nadditional checks such as `isCompleteCondition`\n- the stored document puts all stream properties top level (currently\nonly `ingest`, instead of `stream.ingest`)\n- `condition` is renamed to `if`, and required everywhere\n- `always` and `never` conditions were added\n- `grok` and `dissect` processors are now similar to ES, where the\ncondition is a part of the processor config\n- `GET /api/streams/{id}` returns `{ stream: ..., dashboards: ..., ...\n}` instead of `{ ingest: ...., dashboards: ..., ... }`\n- `PUT /api/streams/{id}` now requires `dashboards`, and `stream` is a\ntop-level property\n- `PUT /api/streams/{id}/_ingest` was added to allow consumers to only\nupdate the stream, and not its assets\n- there are some legacy definitions (in `legacy.ts`) to minimize the\namount of changes in the UI, this still needs to happen at some point\nbut not in this PR\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8d4a70c5e5a0ad9fd985d71d2f107bc29b330a92","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","Feature:Streams"],"title":"Refactor models","number":206930,"url":"https://github.com/elastic/kibana/pull/206930","mergeCommit":{"message":"Refactor models (#206930)\n\nRefactors models to make it more clear what our data model is internally\nand what our API responses are. Also some small changes to make it more\nelasticsearch-y:\n\n- isSchema variants now are based on specific type narrowing instead of\nfrom any > type, as the latter only gives runtime safety, but does not\nadd much in terms of type safety\n- validation is now entirely encapsulated in the type, removed\nadditional checks such as `isCompleteCondition`\n- the stored document puts all stream properties top level (currently\nonly `ingest`, instead of `stream.ingest`)\n- `condition` is renamed to `if`, and required everywhere\n- `always` and `never` conditions were added\n- `grok` and `dissect` processors are now similar to ES, where the\ncondition is a part of the processor config\n- `GET /api/streams/{id}` returns `{ stream: ..., dashboards: ..., ...\n}` instead of `{ ingest: ...., dashboards: ..., ... }`\n- `PUT /api/streams/{id}` now requires `dashboards`, and `stream` is a\ntop-level property\n- `PUT /api/streams/{id}/_ingest` was added to allow consumers to only\nupdate the stream, and not its assets\n- there are some legacy definitions (in `legacy.ts`) to minimize the\namount of changes in the UI, this still needs to happen at some point\nbut not in this PR\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8d4a70c5e5a0ad9fd985d71d2f107bc29b330a92"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206930","number":206930,"mergeCommit":{"message":"Refactor models (#206930)\n\nRefactors models to make it more clear what our data model is internally\nand what our API responses are. Also some small changes to make it more\nelasticsearch-y:\n\n- isSchema variants now are based on specific type narrowing instead of\nfrom any > type, as the latter only gives runtime safety, but does not\nadd much in terms of type safety\n- validation is now entirely encapsulated in the type, removed\nadditional checks such as `isCompleteCondition`\n- the stored document puts all stream properties top level (currently\nonly `ingest`, instead of `stream.ingest`)\n- `condition` is renamed to `if`, and required everywhere\n- `always` and `never` conditions were added\n- `grok` and `dissect` processors are now similar to ES, where the\ncondition is a part of the processor config\n- `GET /api/streams/{id}` returns `{ stream: ..., dashboards: ..., ...\n}` instead of `{ ingest: ...., dashboards: ..., ... }`\n- `PUT /api/streams/{id}` now requires `dashboards`, and `stream` is a\ntop-level property\n- `PUT /api/streams/{id}/_ingest` was added to allow consumers to only\nupdate the stream, and not its assets\n- there are some legacy definitions (in `legacy.ts`) to minimize the\namount of changes in the UI, this still needs to happen at some point\nbut not in this PR\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"8d4a70c5e5a0ad9fd985d71d2f107bc29b330a92"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dario Gieselaar <dario.gieselaar@elastic.co> |
||
|
Kibana Machine
|
c41692ac68
|
[8.x] [Fleet] Fix migrating enrollment api keys for space awareness (#207847) (#207875)
# Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] Fix migrating enrollment api keys for space awareness (#207847)](https://github.com/elastic/kibana/pull/207847) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:24:51Z","message":"[Fleet] Fix migrating enrollment api keys for space awareness (#207847)","sha":"0d32932f6bbbd70554f662e41e0b3a468ed709ff","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor"],"title":"[Fleet] Fix migrating enrollment api keys for space awareness","number":207847,"url":"https://github.com/elastic/kibana/pull/207847","mergeCommit":{"message":"[Fleet] Fix migrating enrollment api keys for space awareness (#207847)","sha":"0d32932f6bbbd70554f662e41e0b3a468ed709ff"}},"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/207847","number":207847,"mergeCommit":{"message":"[Fleet] Fix migrating enrollment api keys for space awareness (#207847)","sha":"0d32932f6bbbd70554f662e41e0b3a468ed709ff"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
06af0cf9a3
|
[8.x] Fixed an error with missing uids in the cases detail page (#207228) (#207873)
# Backport This will backport the following commits from `main` to `8.x`: - [Fixed an error with missing uids in the cases detail page (#207228)](https://github.com/elastic/kibana/pull/207228) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Antonio","email":"antonio.coelho@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:15:43Z","message":"Fixed an error with missing uids in the cases detail page (#207228)\n\nFixes #206801\r\n\r\n## Summary\r\n\r\nWhen opening the case detail page we retrieve user profile info for the\r\ndifferent case user actions.\r\n\r\nIf the uid stored in ES is an empty string for any of these user\r\nactions, we get an error that looks like this:\r\n\r\n\r\n\r\n\r\n### Steps to reproduce/test (thanks @jcger )\r\n\r\n1. Create a user with the `system_indices_superuser` role\r\n2. Create a case and assign a user to it\r\n3. Get the ID of the assignment user action from the case above\r\n```\r\nGET .kibana_alerting_cases/_search\r\n{\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"type\": \"cases-user-actions\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"cases-user-actions.type\": \"assignees\"\r\n }\r\n },\r\n {\r\n \"nested\": {\r\n \"path\": \"references\",\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"references.type\": \"cases\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"references.id\": \"<case_id>\"\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n4. Manually set the `uid` of the assignee to `\"\"`\r\n```\r\nPOST .kibana_alerting_cases/_update/<cases-user-actions-id>\r\n{\r\n \"script\": {\r\n \"source\": \"\"\"\r\n ctx._source[\"cases-user-actions\"].payload.assignees[0].uid = \"\";\r\n \"\"\"\r\n }\r\n}\r\n```\r\n\r\nAfter this PR the popup should **not** appear anymore.","sha":"d8e5cbf67f2bae859a18f956c22205b78d3da5aa","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","v9.0.0","Feature:Cases","backport:prev-minor"],"title":"Fixed an error with missing uids in the cases detail page","number":207228,"url":"https://github.com/elastic/kibana/pull/207228","mergeCommit":{"message":"Fixed an error with missing uids in the cases detail page (#207228)\n\nFixes #206801\r\n\r\n## Summary\r\n\r\nWhen opening the case detail page we retrieve user profile info for the\r\ndifferent case user actions.\r\n\r\nIf the uid stored in ES is an empty string for any of these user\r\nactions, we get an error that looks like this:\r\n\r\n\r\n\r\n\r\n### Steps to reproduce/test (thanks @jcger )\r\n\r\n1. Create a user with the `system_indices_superuser` role\r\n2. Create a case and assign a user to it\r\n3. Get the ID of the assignment user action from the case above\r\n```\r\nGET .kibana_alerting_cases/_search\r\n{\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"type\": \"cases-user-actions\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"cases-user-actions.type\": \"assignees\"\r\n }\r\n },\r\n {\r\n \"nested\": {\r\n \"path\": \"references\",\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"references.type\": \"cases\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"references.id\": \"<case_id>\"\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n4. Manually set the `uid` of the assignee to `\"\"`\r\n```\r\nPOST .kibana_alerting_cases/_update/<cases-user-actions-id>\r\n{\r\n \"script\": {\r\n \"source\": \"\"\"\r\n ctx._source[\"cases-user-actions\"].payload.assignees[0].uid = \"\";\r\n \"\"\"\r\n }\r\n}\r\n```\r\n\r\nAfter this PR the popup should **not** appear anymore.","sha":"d8e5cbf67f2bae859a18f956c22205b78d3da5aa"}},"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/207228","number":207228,"mergeCommit":{"message":"Fixed an error with missing uids in the cases detail page (#207228)\n\nFixes #206801\r\n\r\n## Summary\r\n\r\nWhen opening the case detail page we retrieve user profile info for the\r\ndifferent case user actions.\r\n\r\nIf the uid stored in ES is an empty string for any of these user\r\nactions, we get an error that looks like this:\r\n\r\n\r\n\r\n\r\n### Steps to reproduce/test (thanks @jcger )\r\n\r\n1. Create a user with the `system_indices_superuser` role\r\n2. Create a case and assign a user to it\r\n3. Get the ID of the assignment user action from the case above\r\n```\r\nGET .kibana_alerting_cases/_search\r\n{\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"type\": \"cases-user-actions\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"cases-user-actions.type\": \"assignees\"\r\n }\r\n },\r\n {\r\n \"nested\": {\r\n \"path\": \"references\",\r\n \"query\": {\r\n \"bool\": {\r\n \"filter\": [\r\n {\r\n \"term\": {\r\n \"references.type\": \"cases\"\r\n }\r\n },\r\n {\r\n \"term\": {\r\n \"references.id\": \"<case_id>\"\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n }\r\n }\r\n ]\r\n }\r\n }\r\n}\r\n```\r\n4. Manually set the `uid` of the assignee to `\"\"`\r\n```\r\nPOST .kibana_alerting_cases/_update/<cases-user-actions-id>\r\n{\r\n \"script\": {\r\n \"source\": \"\"\"\r\n ctx._source[\"cases-user-actions\"].payload.assignees[0].uid = \"\";\r\n \"\"\"\r\n }\r\n}\r\n```\r\n\r\nAfter this PR the popup should **not** appear anymore.","sha":"d8e5cbf67f2bae859a18f956c22205b78d3da5aa"}}]}] BACKPORT--> Co-authored-by: Antonio <antonio.coelho@elastic.co> |
||
|
Kibana Machine
|
0d8230b67e
|
[8.x] [Data] Take into account failure-store selector (#207438) (#207871)
# Backport This will backport the following commits from `main` to `8.x`: - [[Data] Take into account failure-store selector (#207438)](https://github.com/elastic/kibana/pull/207438) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Thomas Neirynck","email":"thomas@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:09:57Z","message":"[Data] Take into account failure-store selector (#207438)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/205109\r\n\r\nUpdate CCS check so it doesn't validate failure-store delimiters.\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]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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: Lukas Olson <olson.lukas@gmail.com>","sha":"27a26fae4b5a4a554365a497413345bc0c078f89","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:DataDiscovery","backport:prev-minor","ci:cloud-deploy","v8.18.0"],"title":"[Data] Take into account failure-store selector","number":207438,"url":"https://github.com/elastic/kibana/pull/207438","mergeCommit":{"message":"[Data] Take into account failure-store selector (#207438)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/205109\r\n\r\nUpdate CCS check so it doesn't validate failure-store delimiters.\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]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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: Lukas Olson <olson.lukas@gmail.com>","sha":"27a26fae4b5a4a554365a497413345bc0c078f89"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207438","number":207438,"mergeCommit":{"message":"[Data] Take into account failure-store selector (#207438)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/205109\r\n\r\nUpdate CCS check so it doesn't validate failure-store delimiters.\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]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas added for features that require explanation or tutorials\r\n- [x] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [x] 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- [x] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [ ] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\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: Lukas Olson <olson.lukas@gmail.com>","sha":"27a26fae4b5a4a554365a497413345bc0c078f89"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Thomas Neirynck <thomas@elastic.co> |
||
|
Kibana Machine
|
1a517b4e9e
|
[8.x] [SIEM migrations] Fix duplicated translations issue (#207845) (#207870)
# Backport This will backport the following commits from `main` to `8.x`: - [[SIEM migrations] Fix duplicated translations issue (#207845)](https://github.com/elastic/kibana/pull/207845) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T16:08:03Z","message":"[SIEM migrations] Fix duplicated translations issue (#207845)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nThis PR fixes the duplicated translations issue introduced in\r\nhttps://github.com/elastic/kibana/pull/207242\r\n\r\n> [!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental flag enabled\r\nto work.","sha":"cde76c1e2dca941fee581c54aeafc5f617c9bfcf","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","Team: SecuritySolution","backport:prev-minor"],"title":"[SIEM migrations] Fix duplicated translations issue","number":207845,"url":"https://github.com/elastic/kibana/pull/207845","mergeCommit":{"message":"[SIEM migrations] Fix duplicated translations issue (#207845)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nThis PR fixes the duplicated translations issue introduced in\r\nhttps://github.com/elastic/kibana/pull/207242\r\n\r\n> [!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental flag enabled\r\nto work.","sha":"cde76c1e2dca941fee581c54aeafc5f617c9bfcf"}},"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/207845","number":207845,"mergeCommit":{"message":"[SIEM migrations] Fix duplicated translations issue (#207845)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nThis PR fixes the duplicated translations issue introduced in\r\nhttps://github.com/elastic/kibana/pull/207242\r\n\r\n> [!NOTE] \r\n> This feature needs `siemMigrationsEnabled` experimental flag enabled\r\nto work.","sha":"cde76c1e2dca941fee581c54aeafc5f617c9bfcf"}}]}] BACKPORT--> Co-authored-by: Ievgen Sorokopud <ievgen.sorokopud@elastic.co> |
||
|
Kibana Machine
|
0d22f08c4b
|
[8.x] [Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694) (#207866)
# Backport This will backport the following commits from `main` to `8.x`: - [[Observability Onboarding] Update values.yml file URL for the OTel K8s flow (#205694)](https://github.com/elastic/kibana/pull/205694) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/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":["8.x"],"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,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Giorgos Bamparopoulos <georgios.bamparopoulos@elastic.co> |
||
wajihaparvez
|
e3be22a6be
|
[Docs] Add known issue about UA deprecation warning (#207512)
## Summary Adding #206400 as a known issue to the 8.17 release notes. Previews: [8.17.0](https://kibana_bk_207512.docs-preview.app.elstc.co/guide/en/kibana/8.x/release-notes-8.17.0.html#known-issues-8.17.0) and [8.17.1](https://kibana_bk_207512.docs-preview.app.elstc.co/guide/en/kibana/8.x/release-notes-8.17.1.html#known-issues-8.17.1). Closes: [#619](https://github.com/orgs/elastic/projects/1232/views/54pane=issue&itemId=94636712&issue=elastic%7Cplatform-docs-team%7C619) |
||
Alex Szabo
|
6bb93b1dc1
|
[ci] Skip failing storybook config (#207876)
## Summary A follow-up on https://github.com/elastic/kibana/pull/207846 - another suite needs to be skipped. Related to: https://github.com/elastic/kibana/issues/207227 Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
|
Kibana Machine
|
bc65a482f2
|
[8.x] [Fleet] Fix UI error when agent goes to orphaned state (#207746) (#207836)
# Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] Fix UI error when agent goes to orphaned state (#207746)](https://github.com/elastic/kibana/pull/207746) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Julia Bardi","email":"90178898+juliaElastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-22T14:20:03Z","message":"[Fleet] Fix UI error when agent goes to orphaned state (#207746)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/207017\r\n\r\nIt seems that when the orphaned agent service is restarted, it briefly\r\nhas a component state string, instead of array, that's why the error.\r\nThe fix checks that the components is an array before calling map.\r\n\r\nTo verify:\r\n1. Enroll an agent to an agent policy with endpoint integration.\r\n2. Stop agent service so that agent gets into orphaned state.\r\n3. Now restart the service and observe that the error\r\n`_hit$_source4.components.map is not a function` no longer appears.\r\n\r\n<img width=\"1531\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c9a957d7-a0d3-4831-90f9-a57479193ee0\"\r\n/>\r\n<img width=\"1530\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c0aa62f0-708b-463e-9184-01d8641c8f21\"\r\n/>","sha":"9800147681323f95f5e951328f9f56a399796350","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","v9.0.0","backport:prev-minor"],"title":"[Fleet] Fix UI error when agent goes to orphaned state","number":207746,"url":"https://github.com/elastic/kibana/pull/207746","mergeCommit":{"message":"[Fleet] Fix UI error when agent goes to orphaned state (#207746)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/207017\r\n\r\nIt seems that when the orphaned agent service is restarted, it briefly\r\nhas a component state string, instead of array, that's why the error.\r\nThe fix checks that the components is an array before calling map.\r\n\r\nTo verify:\r\n1. Enroll an agent to an agent policy with endpoint integration.\r\n2. Stop agent service so that agent gets into orphaned state.\r\n3. Now restart the service and observe that the error\r\n`_hit$_source4.components.map is not a function` no longer appears.\r\n\r\n<img width=\"1531\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c9a957d7-a0d3-4831-90f9-a57479193ee0\"\r\n/>\r\n<img width=\"1530\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c0aa62f0-708b-463e-9184-01d8641c8f21\"\r\n/>","sha":"9800147681323f95f5e951328f9f56a399796350"}},"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/207746","number":207746,"mergeCommit":{"message":"[Fleet] Fix UI error when agent goes to orphaned state (#207746)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/207017\r\n\r\nIt seems that when the orphaned agent service is restarted, it briefly\r\nhas a component state string, instead of array, that's why the error.\r\nThe fix checks that the components is an array before calling map.\r\n\r\nTo verify:\r\n1. Enroll an agent to an agent policy with endpoint integration.\r\n2. Stop agent service so that agent gets into orphaned state.\r\n3. Now restart the service and observe that the error\r\n`_hit$_source4.components.map is not a function` no longer appears.\r\n\r\n<img width=\"1531\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c9a957d7-a0d3-4831-90f9-a57479193ee0\"\r\n/>\r\n<img width=\"1530\" alt=\"image\"\r\nsrc=\"https://github.com/user-attachments/assets/c0aa62f0-708b-463e-9184-01d8641c8f21\"\r\n/>","sha":"9800147681323f95f5e951328f9f56a399796350"}}]}] BACKPORT--> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
elastic-vault-github-plugin-prod[bot]
|
a46d990629
|
[8.x] Sync bundled packages with Package Storage (#207414)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2084 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
Jean-Louis Leysens
|
12fe799166
|
[8.x] [Http] Router refactor (#205502) (#207828)
# Backport This will backport the following commits from `main` to `8.x`: - [[Http] Router refactor (#205502)](https://github.com/elastic/kibana/pull/205502) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jean-Louis Leysens","email":"jeanlouis.leysens@elastic.co"},"sourceCommit":{"committedDate":"2025-01-15T15:10:46Z","message":"[Http] Router refactor (#205502)","sha":"ca77772d2ad5db6bb1c7b9412845e59d7a59d3ac","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:http","Team:Core","release_note:skip","backport missing","v9.0.0","backport:version","v8.18.0"],"title":"[Http] Router refactor","number":205502,"url":"https://github.com/elastic/kibana/pull/205502","mergeCommit":{"message":"[Http] Router refactor (#205502)","sha":"ca77772d2ad5db6bb1c7b9412845e59d7a59d3ac"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205502","number":205502,"mergeCommit":{"message":"[Http] Router refactor (#205502)","sha":"ca77772d2ad5db6bb1c7b9412845e59d7a59d3ac"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
a14c51c4c4
|
[8.x] [Authz] Explicitly added superuser privileges for _invalidate route (#207366) (#207790)
# Backport This will backport the following commits from `main` to `8.x`: - [[Authz] Explicitly added superuser privileges for _invalidate route (#207366)](https://github.com/elastic/kibana/pull/207366) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-22T13:12:32Z","message":"[Authz] Explicitly added superuser privileges for _invalidate route (#207366)\n\n## Summary\r\n\r\nThere was no `sessionManagement` privilege registered, so the route was\r\navailable only for superusers or users with equivalent privileges.\r\nExplicitly added `superuser` privileges for\r\n`/api/security/session/_invalidate` route.\r\n\r\n\r\n### Checklist\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\r\n__Related: https://github.com/elastic/kibana/issues/198716__","sha":"8f8ed8716f7262fb7e9a53ed810bfa610568bc98","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","Feature:Security/Authorization","v9.0.0","backport:prev-minor"],"title":"[Authz] Explicitly added superuser privileges for _invalidate route","number":207366,"url":"https://github.com/elastic/kibana/pull/207366","mergeCommit":{"message":"[Authz] Explicitly added superuser privileges for _invalidate route (#207366)\n\n## Summary\r\n\r\nThere was no `sessionManagement` privilege registered, so the route was\r\navailable only for superusers or users with equivalent privileges.\r\nExplicitly added `superuser` privileges for\r\n`/api/security/session/_invalidate` route.\r\n\r\n\r\n### Checklist\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\r\n__Related: https://github.com/elastic/kibana/issues/198716__","sha":"8f8ed8716f7262fb7e9a53ed810bfa610568bc98"}},"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/207366","number":207366,"mergeCommit":{"message":"[Authz] Explicitly added superuser privileges for _invalidate route (#207366)\n\n## Summary\r\n\r\nThere was no `sessionManagement` privilege registered, so the route was\r\navailable only for superusers or users with equivalent privileges.\r\nExplicitly added `superuser` privileges for\r\n`/api/security/session/_invalidate` route.\r\n\r\n\r\n### Checklist\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\r\n__Related: https://github.com/elastic/kibana/issues/198716__","sha":"8f8ed8716f7262fb7e9a53ed810bfa610568bc98"}}]}] BACKPORT--> Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com> |
||
|
Kibana Machine
|
486355032f
|
[8.x] Fix test and remove skip MKI tag (#207574) (#207793)
# Backport This will backport the following commits from `main` to `8.x`: - [Fix test and remove skip MKI tag (#207574)](https://github.com/elastic/kibana/pull/207574) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Kevin Delemme","email":"kevin.delemme@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T13:18:04Z","message":"Fix test and remove skip MKI tag (#207574)\n\nRelated to https://github.com/elastic/kibana/issues/207354\n\n## Summary\n\nFix test and unskip on MKI","sha":"2481edcc28e49c6d659019e3b09d6508ee350a2a","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Team:obs-ux-management"],"title":"Fix test and remove skip MKI tag","number":207574,"url":"https://github.com/elastic/kibana/pull/207574","mergeCommit":{"message":"Fix test and remove skip MKI tag (#207574)\n\nRelated to https://github.com/elastic/kibana/issues/207354\n\n## Summary\n\nFix test and unskip on MKI","sha":"2481edcc28e49c6d659019e3b09d6508ee350a2a"}},"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/207574","number":207574,"mergeCommit":{"message":"Fix test and remove skip MKI tag (#207574)\n\nRelated to https://github.com/elastic/kibana/issues/207354\n\n## Summary\n\nFix test and unskip on MKI","sha":"2481edcc28e49c6d659019e3b09d6508ee350a2a"}}]}] BACKPORT--> Co-authored-by: Kevin Delemme <kevin.delemme@elastic.co> |
||
|
Kibana Machine
|
db4e49c6f8
|
[8.x] [Fleet] Do not reassign actions space (#207381) (#207796)
# Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] Do not reassign actions space (#207381)](https://github.com/elastic/kibana/pull/207381) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Nicolas Chaulet","email":"nicolas.chaulet@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T13:24:20Z","message":"[Fleet] Do not reassign actions space (#207381)","sha":"24bab86aefcab7dcc0e83543d547031a8557023d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:prev-minor"],"title":"[Fleet] Do not reassign actions space","number":207381,"url":"https://github.com/elastic/kibana/pull/207381","mergeCommit":{"message":"[Fleet] Do not reassign actions space (#207381)","sha":"24bab86aefcab7dcc0e83543d547031a8557023d"}},"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/207381","number":207381,"mergeCommit":{"message":"[Fleet] Do not reassign actions space (#207381)","sha":"24bab86aefcab7dcc0e83543d547031a8557023d"}}]}] BACKPORT--> Co-authored-by: Nicolas Chaulet <nicolas.chaulet@elastic.co> |
||
|
Kibana Machine
|
515be292e8
|
[8.x] [Rules migration] Implement workflow tour - Setup Guide (#11384) (#207242) (#207782)
# Backport This will backport the following commits from `main` to `8.x`: - [[Rules migration] Implement workflow tour - Setup Guide (#11384) (#207242)](https://github.com/elastic/kibana/pull/207242) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Ievgen Sorokopud","email":"ievgen.sorokopud@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T13:01:49Z","message":"[Rules migration] Implement workflow tour - Setup Guide (#11384) (#207242)\n\n## Summary\r\n\r\n[Internal link](https://github.com/elastic/security-team/issues/10820)\r\nto the feature details\r\n\r\nThis PR adds the SIEM Migration setup tour guide on the main landing\r\npage. [Figma\r\nlink]( |
||
|
Kibana Machine
|
bc5eff0ba1
|
[8.x] fix(NA): skip security solution storybook (#207225) (#207846)
# Backport This will backport the following commits from `main` to `8.x`: - [fix(NA): skip security solution storybook (#207225)](https://github.com/elastic/kibana/pull/207225) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-01-20T16:21:37Z","message":"fix(NA): skip security solution storybook (#207225)\n\nThe Security Solution storybook started to fail so we are skipping it\r\nfor now to unblock the pipelines.","sha":"c06d42fac790a4813fa1b01d46930889596db130","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","v9.0.0","backport:prev-minor"],"title":"fix(NA): skip security solution storybook","number":207225,"url":"https://github.com/elastic/kibana/pull/207225","mergeCommit":{"message":"fix(NA): skip security solution storybook (#207225)\n\nThe Security Solution storybook started to fail so we are skipping it\r\nfor now to unblock the pipelines.","sha":"c06d42fac790a4813fa1b01d46930889596db130"}},"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/207225","number":207225,"mergeCommit":{"message":"fix(NA): skip security solution storybook (#207225)\n\nThe Security Solution storybook started to fail so we are skipping it\r\nfor now to unblock the pipelines.","sha":"c06d42fac790a4813fa1b01d46930889596db130"}}]}] BACKPORT--> Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
|
Kibana Machine
|
0a7b073150
|
[8.x] [Sessions] Reindexing the .kibana_security_session_1 index to the 8.x format. (#204097) (#207784)
# Backport This will backport the following commits from `main` to `8.x`: - [[Sessions] Reindexing the .kibana_security_session_1 index to the 8.x format. (#204097)](https://github.com/elastic/kibana/pull/204097) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Sid","email":"siddharthmantri1@gmail.com"},"sourceCommit":{"committedDate":"2025-01-22T13:03:42Z","message":"[Sessions] Reindexing the .kibana_security_session_1 index to the 8.x format. (#204097)\n\nCloses https://github.com/elastic/kibana/issues/200603\r\n\r\n\r\n## Summary\r\n\r\nReindexes the Kibana Security session system index to the 8.x format to\r\nsupport 9.0 readiness.\r\n\r\n### Release note\r\nCreates Kibana Security session index to only if the\r\n`kibana_security_session_1` index or the reindexed version do not exist.\r\n\r\n### Notes\r\n\r\n\r\n### How to test\r\n\r\nFor this test, you'll need at least 3 copies of Kibana cloned locally.\r\nOne each on 7.17, 8.x and main - ensuring you've run `yarn kbn\r\nbootstrap` on each of them.\r\n\r\n\r\nStep 0. Verify on the PR branch\r\n-----\r\n- Start ES as `yarn es snapshot --license=trial`\r\n- Start kibana `yarn start --no-base-path`\r\n- Login to kibana in a private browsing window\r\n- Navigate to dev tools and run\r\n```\r\nGET .kibana_security_session/_alias\r\n```\r\n- You should see \r\n```\r\n{\r\n \".kibana_security_session_1\": {\r\n \"aliases\": {\r\n \".kibana_security_session\": {\r\n \"is_write_index\": true,\r\n \"is_hidden\": true\r\n }\r\n }\r\n }\r\n}\r\n```\r\nThis indicates that there were no aliases/index present and the new\r\nindex was created.\r\n\r\nStep 1. On 7.17\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata`\r\n- Run kibana\r\n- Login with the `elastic` user\r\n- Navigate to dev tools and run the following query\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- You should see your current session being returned as the result for\r\nthis query\r\n- You can now shut down ES and kibana.\r\n\r\n\r\nStep 2. On 8.x\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata` <--- point to the same folder as the previous run\r\n- Run kibana, open a private browser window and login.\r\n- Navigate to Kibana upgrade assistant and Migrate system indices and\r\nwait for it to run.\r\n- Now in Dev tools, run the same query. You should see two sessions. \r\n- One with the idleSessionTimeout returned as null and the other one\r\ncontaining a value - indicating one was created on 7.x and the other in\r\n8.x\r\n- Make a backup of the data folder `cp -r /tmp/esdata /tmp/esdatabkp`\r\n\r\nStep 3(OPTIONAL). On main (without the changes in this PR)\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata`\r\n- This should throw an error \r\n\r\n\r\nStep 4. On 8.x\r\n-----\r\n- First use the backup for the path `cp -r /tmp/esdatabkp /tmp/esdata2`\r\n- Start ES only (do not run Kibana yet) by pointing to the copy: `yarn\r\nes snapshot --license=trial -E path.data=/tmp/esdata2`\r\n- ES should start up and you need to delete 1 index and 2 datastreams\r\nusing the ES APIs and any method you prefer. For your convenience, you\r\ncan use the same script as mine:\r\n```ts\r\nimport axios from 'axios';\r\n\r\nconst clearIndexAndDatastream = async () => {\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/.kibana-event-log-7.17.28-000001\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted index:\", JSON.stringify(res.data));\r\n }\r\n\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/_data_stream/ilm-history-5\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted ds1:\", JSON.stringify(res.data));\r\n }\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/_data_stream/.logs-deprecation.elasticsearch-default\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted ds2:\", JSON.stringify(res.data));\r\n }\r\n};\r\n\r\nclearIndexAndDatastream();\r\n```\r\nYou should see the result as:\r\n\r\n```\r\ndeleted index: {\"acknowledged\":true}\r\ndeleted ds1: {\"acknowledged\":true}\r\ndeleted ds2: {\"acknowledged\":true}\r\n```\r\n- Now login to Kibana in a private browsing window and navigate to\r\nUpgrade assistant and run the migration.\r\n- Navigating to devtools and running the same query as above will show\r\nyou three results. One with no idleTimeout and 2 with timeouts (One on\r\n7.x and two on 8.x format respectively)\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- You can now shut ES and kibana at this point. \r\n\r\nStep 5. On the branch of this PR\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata2`\r\n- Run Kibana and login using a private window. \r\n- Navigating to dev tools and run:\r\n```\r\nGET .kibana_security_session/_alias\r\n```\r\nTo show a result as:\r\n```\r\n{\r\n \".kibana_security_session_1-reindexed-for-9\": {\r\n \"aliases\": {\r\n \".kibana_security_session\": {\r\n \"is_hidden\": true\r\n },\r\n \".kibana_security_session_1\": {\r\n \"is_hidden\": true\r\n }\r\n }\r\n }\r\n}\r\n```\r\nThis indicates that no new index was created and we are using the\r\nreindexed version from 8.x.\r\n\r\n- You should also run the query to check for sessions:\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- This should return 4 sessions in the results\r\n\r\nThis confirms that the session was re-indexed correctly using the right\r\naliases.\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"26350ff3ba6e422c419f75cc44ae22ce3da53d9f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Security","v9.0.0","Feature:Security/Session Management","backport:prev-minor"],"title":"[Sessions] Reindexing the .kibana_security_session_1 index to the 8.x format.","number":204097,"url":"https://github.com/elastic/kibana/pull/204097","mergeCommit":{"message":"[Sessions] Reindexing the .kibana_security_session_1 index to the 8.x format. (#204097)\n\nCloses https://github.com/elastic/kibana/issues/200603\r\n\r\n\r\n## Summary\r\n\r\nReindexes the Kibana Security session system index to the 8.x format to\r\nsupport 9.0 readiness.\r\n\r\n### Release note\r\nCreates Kibana Security session index to only if the\r\n`kibana_security_session_1` index or the reindexed version do not exist.\r\n\r\n### Notes\r\n\r\n\r\n### How to test\r\n\r\nFor this test, you'll need at least 3 copies of Kibana cloned locally.\r\nOne each on 7.17, 8.x and main - ensuring you've run `yarn kbn\r\nbootstrap` on each of them.\r\n\r\n\r\nStep 0. Verify on the PR branch\r\n-----\r\n- Start ES as `yarn es snapshot --license=trial`\r\n- Start kibana `yarn start --no-base-path`\r\n- Login to kibana in a private browsing window\r\n- Navigate to dev tools and run\r\n```\r\nGET .kibana_security_session/_alias\r\n```\r\n- You should see \r\n```\r\n{\r\n \".kibana_security_session_1\": {\r\n \"aliases\": {\r\n \".kibana_security_session\": {\r\n \"is_write_index\": true,\r\n \"is_hidden\": true\r\n }\r\n }\r\n }\r\n}\r\n```\r\nThis indicates that there were no aliases/index present and the new\r\nindex was created.\r\n\r\nStep 1. On 7.17\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata`\r\n- Run kibana\r\n- Login with the `elastic` user\r\n- Navigate to dev tools and run the following query\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- You should see your current session being returned as the result for\r\nthis query\r\n- You can now shut down ES and kibana.\r\n\r\n\r\nStep 2. On 8.x\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata` <--- point to the same folder as the previous run\r\n- Run kibana, open a private browser window and login.\r\n- Navigate to Kibana upgrade assistant and Migrate system indices and\r\nwait for it to run.\r\n- Now in Dev tools, run the same query. You should see two sessions. \r\n- One with the idleSessionTimeout returned as null and the other one\r\ncontaining a value - indicating one was created on 7.x and the other in\r\n8.x\r\n- Make a backup of the data folder `cp -r /tmp/esdata /tmp/esdatabkp`\r\n\r\nStep 3(OPTIONAL). On main (without the changes in this PR)\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata`\r\n- This should throw an error \r\n\r\n\r\nStep 4. On 8.x\r\n-----\r\n- First use the backup for the path `cp -r /tmp/esdatabkp /tmp/esdata2`\r\n- Start ES only (do not run Kibana yet) by pointing to the copy: `yarn\r\nes snapshot --license=trial -E path.data=/tmp/esdata2`\r\n- ES should start up and you need to delete 1 index and 2 datastreams\r\nusing the ES APIs and any method you prefer. For your convenience, you\r\ncan use the same script as mine:\r\n```ts\r\nimport axios from 'axios';\r\n\r\nconst clearIndexAndDatastream = async () => {\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/.kibana-event-log-7.17.28-000001\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted index:\", JSON.stringify(res.data));\r\n }\r\n\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/_data_stream/ilm-history-5\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted ds1:\", JSON.stringify(res.data));\r\n }\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/_data_stream/.logs-deprecation.elasticsearch-default\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted ds2:\", JSON.stringify(res.data));\r\n }\r\n};\r\n\r\nclearIndexAndDatastream();\r\n```\r\nYou should see the result as:\r\n\r\n```\r\ndeleted index: {\"acknowledged\":true}\r\ndeleted ds1: {\"acknowledged\":true}\r\ndeleted ds2: {\"acknowledged\":true}\r\n```\r\n- Now login to Kibana in a private browsing window and navigate to\r\nUpgrade assistant and run the migration.\r\n- Navigating to devtools and running the same query as above will show\r\nyou three results. One with no idleTimeout and 2 with timeouts (One on\r\n7.x and two on 8.x format respectively)\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- You can now shut ES and kibana at this point. \r\n\r\nStep 5. On the branch of this PR\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata2`\r\n- Run Kibana and login using a private window. \r\n- Navigating to dev tools and run:\r\n```\r\nGET .kibana_security_session/_alias\r\n```\r\nTo show a result as:\r\n```\r\n{\r\n \".kibana_security_session_1-reindexed-for-9\": {\r\n \"aliases\": {\r\n \".kibana_security_session\": {\r\n \"is_hidden\": true\r\n },\r\n \".kibana_security_session_1\": {\r\n \"is_hidden\": true\r\n }\r\n }\r\n }\r\n}\r\n```\r\nThis indicates that no new index was created and we are using the\r\nreindexed version from 8.x.\r\n\r\n- You should also run the query to check for sessions:\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- This should return 4 sessions in the results\r\n\r\nThis confirms that the session was re-indexed correctly using the right\r\naliases.\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"26350ff3ba6e422c419f75cc44ae22ce3da53d9f"}},"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/204097","number":204097,"mergeCommit":{"message":"[Sessions] Reindexing the .kibana_security_session_1 index to the 8.x format. (#204097)\n\nCloses https://github.com/elastic/kibana/issues/200603\r\n\r\n\r\n## Summary\r\n\r\nReindexes the Kibana Security session system index to the 8.x format to\r\nsupport 9.0 readiness.\r\n\r\n### Release note\r\nCreates Kibana Security session index to only if the\r\n`kibana_security_session_1` index or the reindexed version do not exist.\r\n\r\n### Notes\r\n\r\n\r\n### How to test\r\n\r\nFor this test, you'll need at least 3 copies of Kibana cloned locally.\r\nOne each on 7.17, 8.x and main - ensuring you've run `yarn kbn\r\nbootstrap` on each of them.\r\n\r\n\r\nStep 0. Verify on the PR branch\r\n-----\r\n- Start ES as `yarn es snapshot --license=trial`\r\n- Start kibana `yarn start --no-base-path`\r\n- Login to kibana in a private browsing window\r\n- Navigate to dev tools and run\r\n```\r\nGET .kibana_security_session/_alias\r\n```\r\n- You should see \r\n```\r\n{\r\n \".kibana_security_session_1\": {\r\n \"aliases\": {\r\n \".kibana_security_session\": {\r\n \"is_write_index\": true,\r\n \"is_hidden\": true\r\n }\r\n }\r\n }\r\n}\r\n```\r\nThis indicates that there were no aliases/index present and the new\r\nindex was created.\r\n\r\nStep 1. On 7.17\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata`\r\n- Run kibana\r\n- Login with the `elastic` user\r\n- Navigate to dev tools and run the following query\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- You should see your current session being returned as the result for\r\nthis query\r\n- You can now shut down ES and kibana.\r\n\r\n\r\nStep 2. On 8.x\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata` <--- point to the same folder as the previous run\r\n- Run kibana, open a private browser window and login.\r\n- Navigate to Kibana upgrade assistant and Migrate system indices and\r\nwait for it to run.\r\n- Now in Dev tools, run the same query. You should see two sessions. \r\n- One with the idleSessionTimeout returned as null and the other one\r\ncontaining a value - indicating one was created on 7.x and the other in\r\n8.x\r\n- Make a backup of the data folder `cp -r /tmp/esdata /tmp/esdatabkp`\r\n\r\nStep 3(OPTIONAL). On main (without the changes in this PR)\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata`\r\n- This should throw an error \r\n\r\n\r\nStep 4. On 8.x\r\n-----\r\n- First use the backup for the path `cp -r /tmp/esdatabkp /tmp/esdata2`\r\n- Start ES only (do not run Kibana yet) by pointing to the copy: `yarn\r\nes snapshot --license=trial -E path.data=/tmp/esdata2`\r\n- ES should start up and you need to delete 1 index and 2 datastreams\r\nusing the ES APIs and any method you prefer. For your convenience, you\r\ncan use the same script as mine:\r\n```ts\r\nimport axios from 'axios';\r\n\r\nconst clearIndexAndDatastream = async () => {\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/.kibana-event-log-7.17.28-000001\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted index:\", JSON.stringify(res.data));\r\n }\r\n\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/_data_stream/ilm-history-5\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted ds1:\", JSON.stringify(res.data));\r\n }\r\n {\r\n const res = await axios.delete(\r\n \"http://localhost:9200/_data_stream/.logs-deprecation.elasticsearch-default\",\r\n {\r\n headers: {\r\n Authorization: \"Basic ZWxhc3RpYzpjaGFuZ2VtZQ==\",\r\n accept: \"*/*\",\r\n \"Content-Type\": \"application/json\",\r\n \"Kbn-Xsrf\": \"true\",\r\n },\r\n }\r\n );\r\n console.log(\"deleted ds2:\", JSON.stringify(res.data));\r\n }\r\n};\r\n\r\nclearIndexAndDatastream();\r\n```\r\nYou should see the result as:\r\n\r\n```\r\ndeleted index: {\"acknowledged\":true}\r\ndeleted ds1: {\"acknowledged\":true}\r\ndeleted ds2: {\"acknowledged\":true}\r\n```\r\n- Now login to Kibana in a private browsing window and navigate to\r\nUpgrade assistant and run the migration.\r\n- Navigating to devtools and running the same query as above will show\r\nyou three results. One with no idleTimeout and 2 with timeouts (One on\r\n7.x and two on 8.x format respectively)\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- You can now shut ES and kibana at this point. \r\n\r\nStep 5. On the branch of this PR\r\n-----\r\n- Run ES with `yarn es snapshot --license=trial -E\r\npath.data=/tmp/esdata2`\r\n- Run Kibana and login using a private window. \r\n- Navigating to dev tools and run:\r\n```\r\nGET .kibana_security_session/_alias\r\n```\r\nTo show a result as:\r\n```\r\n{\r\n \".kibana_security_session_1-reindexed-for-9\": {\r\n \"aliases\": {\r\n \".kibana_security_session\": {\r\n \"is_hidden\": true\r\n },\r\n \".kibana_security_session_1\": {\r\n \"is_hidden\": true\r\n }\r\n }\r\n }\r\n}\r\n```\r\nThis indicates that no new index was created and we are using the\r\nreindexed version from 8.x.\r\n\r\n- You should also run the query to check for sessions:\r\n```\r\nGET .kibana_security_session_1/_search\r\n{\r\n \"query\": {\r\n \"match_all\": {}\r\n }\r\n}\r\n```\r\n- This should return 4 sessions in the results\r\n\r\nThis confirms that the session was re-indexed correctly using the right\r\naliases.\r\n\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [ ] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [ ] [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- [ ] ...\r\n\r\n---------\r\n\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"26350ff3ba6e422c419f75cc44ae22ce3da53d9f"}}]}] BACKPORT--> Co-authored-by: Sid <siddharthmantri1@gmail.com> |
||
|
Kibana Machine
|
aa0efce325
|
[8.x] Increase timeout for KB status endpoint test (#207715) (#207772)
# Backport This will backport the following commits from `main` to `8.x`: - [Increase timeout for KB status endpoint test (#207715)](https://github.com/elastic/kibana/pull/207715) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Søren Louv-Jansen","email":"soren.louv@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T12:42:40Z","message":"Increase timeout for KB status endpoint test (#207715)\n\nCloses https://github.com/elastic/kibana/issues/207733\n\nAddresses build failures like\nhttps://buildkite.com/elastic/appex-qa-serverless-kibana-ftr-tests/builds/4033\nby increasing the timeout from 2 min to 5 min\n\nThis is the test that was failing\n> 1) Serverless Observability - Deployment-agnostic API integration\ntests\n--\n | │ observability AI Assistant\n | │ /internal/observability_ai_assistant/kb/status\n | │ \"before each\" hook for \"returns correct status after knowledge\nbase is setup\":\n | │\n | │ Error: retry.try reached timeout 120000 ms\n | │ Error: expected false to equal true\n | │ at Assertion.assert (expect.js💯11)\n | │ at Assertion.apply (expect.js:227:8)\n | │ at Assertion.be (expect.js:69:22)\n | │ at helpers.ts:64:31\n | │ at processTicksAndRejections\n(node:internal/process/task_queues:95:5)\n | │ at runAttempt (retry_for_success.ts:30:15)\n | │ at retryForSuccess (retry_for_success.ts:103:21)\n | │ at RetryService.try (retry.ts:52:12)\n | │ at waitForKnowledgeBaseReady (helpers.ts:58:3)\n | │ at Context.<anonymous> (knowledge_base_status.spec.ts:31:7)\n | │ at Object.apply (wrap_function.js:74:16)\n | │ at onFailure (retry_for_success.ts:18:9)\n | │ at retryForSuccess (retry_for_success.ts:86:7)\n | │ at RetryService.try (retry.ts:52:12)\n | │ at waitForKnowledgeBaseReady (helpers.ts:58:3)\n | │ at Context.<anonymous> (knowledge_base_status.spec.ts:31:7)\n | │ at Object.apply (wrap_function.js:74:16)","sha":"422b092e5164f82e1a57087e4a61cf54e5fa8994","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor"],"title":"Increase timeout for KB status endpoint test","number":207715,"url":"https://github.com/elastic/kibana/pull/207715","mergeCommit":{"message":"Increase timeout for KB status endpoint test (#207715)\n\nCloses https://github.com/elastic/kibana/issues/207733\n\nAddresses build failures like\nhttps://buildkite.com/elastic/appex-qa-serverless-kibana-ftr-tests/builds/4033\nby increasing the timeout from 2 min to 5 min\n\nThis is the test that was failing\n> 1) Serverless Observability - Deployment-agnostic API integration\ntests\n--\n | │ observability AI Assistant\n | │ /internal/observability_ai_assistant/kb/status\n | │ \"before each\" hook for \"returns correct status after knowledge\nbase is setup\":\n | │\n | │ Error: retry.try reached timeout 120000 ms\n | │ Error: expected false to equal true\n | │ at Assertion.assert (expect.js💯11)\n | │ at Assertion.apply (expect.js:227:8)\n | │ at Assertion.be (expect.js:69:22)\n | │ at helpers.ts:64:31\n | │ at processTicksAndRejections\n(node:internal/process/task_queues:95:5)\n | │ at runAttempt (retry_for_success.ts:30:15)\n | │ at retryForSuccess (retry_for_success.ts:103:21)\n | │ at RetryService.try (retry.ts:52:12)\n | │ at waitForKnowledgeBaseReady (helpers.ts:58:3)\n | │ at Context.<anonymous> (knowledge_base_status.spec.ts:31:7)\n | │ at Object.apply (wrap_function.js:74:16)\n | │ at onFailure (retry_for_success.ts:18:9)\n | │ at retryForSuccess (retry_for_success.ts:86:7)\n | │ at RetryService.try (retry.ts:52:12)\n | │ at waitForKnowledgeBaseReady (helpers.ts:58:3)\n | │ at Context.<anonymous> (knowledge_base_status.spec.ts:31:7)\n | │ at Object.apply (wrap_function.js:74:16)","sha":"422b092e5164f82e1a57087e4a61cf54e5fa8994"}},"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/207715","number":207715,"mergeCommit":{"message":"Increase timeout for KB status endpoint test (#207715)\n\nCloses https://github.com/elastic/kibana/issues/207733\n\nAddresses build failures like\nhttps://buildkite.com/elastic/appex-qa-serverless-kibana-ftr-tests/builds/4033\nby increasing the timeout from 2 min to 5 min\n\nThis is the test that was failing\n> 1) Serverless Observability - Deployment-agnostic API integration\ntests\n--\n | │ observability AI Assistant\n | │ /internal/observability_ai_assistant/kb/status\n | │ \"before each\" hook for \"returns correct status after knowledge\nbase is setup\":\n | │\n | │ Error: retry.try reached timeout 120000 ms\n | │ Error: expected false to equal true\n | │ at Assertion.assert (expect.js💯11)\n | │ at Assertion.apply (expect.js:227:8)\n | │ at Assertion.be (expect.js:69:22)\n | │ at helpers.ts:64:31\n | │ at processTicksAndRejections\n(node:internal/process/task_queues:95:5)\n | │ at runAttempt (retry_for_success.ts:30:15)\n | │ at retryForSuccess (retry_for_success.ts:103:21)\n | │ at RetryService.try (retry.ts:52:12)\n | │ at waitForKnowledgeBaseReady (helpers.ts:58:3)\n | │ at Context.<anonymous> (knowledge_base_status.spec.ts:31:7)\n | │ at Object.apply (wrap_function.js:74:16)\n | │ at onFailure (retry_for_success.ts:18:9)\n | │ at retryForSuccess (retry_for_success.ts:86:7)\n | │ at RetryService.try (retry.ts:52:12)\n | │ at waitForKnowledgeBaseReady (helpers.ts:58:3)\n | │ at Context.<anonymous> (knowledge_base_status.spec.ts:31:7)\n | │ at Object.apply (wrap_function.js:74:16)","sha":"422b092e5164f82e1a57087e4a61cf54e5fa8994"}}]}] BACKPORT--> Co-authored-by: Søren Louv-Jansen <soren.louv@elastic.co> |
||
Amir Ben Nun
|
747e766250
|
[8.x] [Fleet] Send Agentless API resources (#206042) (#207701)
# Backport This will backport the following commits from `main` to `8.x`: - [[Fleet] Send Agentless API resources (#206042)](https://github.com/elastic/kibana/pull/206042) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Amir Ben Nun","email":"34831306+amirbenun@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-19T10:52:10Z","message":"[Fleet] Send Agentless API resources (#206042)\n\n## Summary\n\nConclude agentless policy resources and send them to the Agentless API\non the creation request.\n- Resolves: https://github.com/elastic/kibana/issues/203371","sha":"fec5d743984b384d48ceb077e1f840cb98b5a16e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Team:Fleet","v9.0.0","Team:Cloud Security","backport:prev-minor","ci:project-deploy-security"],"title":"[Fleet] Send Agentless API resources","number":206042,"url":"https://github.com/elastic/kibana/pull/206042","mergeCommit":{"message":"[Fleet] Send Agentless API resources (#206042)\n\n## Summary\n\nConclude agentless policy resources and send them to the Agentless API\non the creation request.\n- Resolves: https://github.com/elastic/kibana/issues/203371","sha":"fec5d743984b384d48ceb077e1f840cb98b5a16e"}},"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/206042","number":206042,"mergeCommit":{"message":"[Fleet] Send Agentless API resources (#206042)\n\n## Summary\n\nConclude agentless policy resources and send them to the Agentless API\non the creation request.\n- Resolves: https://github.com/elastic/kibana/issues/203371","sha":"fec5d743984b384d48ceb077e1f840cb98b5a16e"}}]}] BACKPORT--> --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> |
||
|
Kibana Machine
|
3fd9c4d886
|
[8.x] [ES|QL] `STATS` command field `WHERE` expression support (#206593) (#207740)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES|QL] `STATS` command field `WHERE` expression support (#206593)](https://github.com/elastic/kibana/pull/206593) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Vadim Kibana","email":"82822460+vadimkibana@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-22T11:32:02Z","message":"[ES|QL] `STATS` command field `WHERE` expression support (#206593)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/195363\r\n\r\nAdds support for ` ... WHERE ... ` expressions inside `STATS` command.\r\nLike\r\n\r\n```\r\nFROM index | STATS a WHERE b\r\n```\r\n\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"36efc592137d646f4666a4a52e8d95ee42909b3f","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","v9.0.0","backport:prev-minor","Feature:ES|QL","Team:ESQL","v8.18.0"],"title":"[ES|QL] `STATS` command field `WHERE` expression support","number":206593,"url":"https://github.com/elastic/kibana/pull/206593","mergeCommit":{"message":"[ES|QL] `STATS` command field `WHERE` expression support (#206593)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/195363\r\n\r\nAdds support for ` ... WHERE ... ` expressions inside `STATS` command.\r\nLike\r\n\r\n```\r\nFROM index | STATS a WHERE b\r\n```\r\n\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"36efc592137d646f4666a4a52e8d95ee42909b3f"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206593","number":206593,"mergeCommit":{"message":"[ES|QL] `STATS` command field `WHERE` expression support (#206593)\n\n## Summary\r\n\r\nCloses https://github.com/elastic/kibana/issues/195363\r\n\r\nAdds support for ` ... WHERE ... ` expressions inside `STATS` command.\r\nLike\r\n\r\n```\r\nFROM index | STATS a WHERE b\r\n```\r\n\r\n\r\n### Checklist\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\r\n---------\r\n\r\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>","sha":"36efc592137d646f4666a4a52e8d95ee42909b3f"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Vadim Kibana <82822460+vadimkibana@users.noreply.github.com> |
||
|
Kibana Machine
|
656bf4afce
|
[8.x] [Inventory v2][APM] Remove redundant synthtrace scenario (#207716) (#207742)
# Backport This will backport the following commits from `main` to `8.x`: - [[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)](https://github.com/elastic/kibana/pull/207716) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"jennypavlova","email":"dzheni.pavlova@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T11:38:15Z","message":"[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)\n\n## Summary\r\n\r\nAs discussed in\r\nhttps://github.com/elastic/kibana/pull/207305#discussion_r1924280917 we\r\ncan use `simple_logs` scenario for the same case instead of the new\r\n`logs_only` so this PR removes it.","sha":"10519c2d4a62a113bd1edbdf3f6079fd9e8bbc58","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-infra_services"],"title":"[Inventory v2][APM] Remove redundant synthtrace scenario","number":207716,"url":"https://github.com/elastic/kibana/pull/207716","mergeCommit":{"message":"[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)\n\n## Summary\r\n\r\nAs discussed in\r\nhttps://github.com/elastic/kibana/pull/207305#discussion_r1924280917 we\r\ncan use `simple_logs` scenario for the same case instead of the new\r\n`logs_only` so this PR removes it.","sha":"10519c2d4a62a113bd1edbdf3f6079fd9e8bbc58"}},"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/207716","number":207716,"mergeCommit":{"message":"[Inventory v2][APM] Remove redundant synthtrace scenario (#207716)\n\n## Summary\r\n\r\nAs discussed in\r\nhttps://github.com/elastic/kibana/pull/207305#discussion_r1924280917 we\r\ncan use `simple_logs` scenario for the same case instead of the new\r\n`logs_only` so this PR removes it.","sha":"10519c2d4a62a113bd1edbdf3f6079fd9e8bbc58"}}]}] BACKPORT--> Co-authored-by: jennypavlova <dzheni.pavlova@elastic.co> |
||
Jeramy Soucy
|
cebdb9b2ce
|
[8.x] Update platform security modules (main) (#206227) (#207315)
# Backport This will backport the following commits from `main` to `8.x`: - [Update platform security modules (main) (#206227)](https://github.com/elastic/kibana/pull/206227) <!--- 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-01-17T15:46:36Z","message":"Update platform security modules (main) (#206227)\n\n### Manual update 2025-01-14:\nuuid v11 contains breaking changes. uuid will be bumped to v10 instead.\n\n### This PR contains the following updates:\n\n| Package | Type | Update | Change | Pending |\n|---|---|---|---|---|\n|\n[@types/js-yaml](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/js-yaml)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/js-yaml))\n| devDependencies | patch | [`^4.0.5` ->\n`^4.0.9`](https://renovatebot.com/diffs/npm/@types%2fjs-yaml/4.0.5/4.0.9)\n| |\n|\n[@types/lodash](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/lodash)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/lodash))\n| devDependencies | patch | [`^4.17.13` ->\n`^4.17.14`](https://renovatebot.com/diffs/npm/@types%2flodash/4.17.13/4.17.14)\n| |\n|\n[@types/object-hash](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/object-hash)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/object-hash))\n| devDependencies | major | [`^1.3.0` ->\n`^3.0.6`](https://renovatebot.com/diffs/npm/@types%2fobject-hash/1.3.0/3.0.6)\n| |\n|\n[@types/uuid](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/uuid)\n([source](https://togithub.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/uuid))\n| devDependencies | major | [`^9.0.0` ->\n`^10.0.0`](https://renovatebot.com/diffs/npm/@types%2fuuid/9.0.0/10.0.0)\n| |\n| [dependency-cruiser](https://togithub.com/sverweij/dependency-cruiser)\n| devDependencies | minor | [`^16.4.2` ->\n`^16.8.0`](https://renovatebot.com/diffs/npm/dependency-cruiser/16.4.2/16.8.0)\n| `16.9.0` |\n| [fast-deep-equal](https://togithub.com/epoberezkin/fast-deep-equal) |\ndependencies | patch | [`^3.1.1` ->\n`^3.1.3`](https://renovatebot.com/diffs/npm/fast-deep-equal/3.1.3/3.1.3)\n| |\n| [minimist](https://togithub.com/minimistjs/minimist) | devDependencies\n| patch | [`^1.2.6` ->\n`^1.2.8`](https://renovatebot.com/diffs/npm/minimist/1.2.8/1.2.8) | |\n| [object-hash](https://togithub.com/puleos/object-hash) | dependencies\n| major | [`^1.3.1` ->\n`^3.0.0`](https://renovatebot.com/diffs/npm/object-hash/1.3.1/3.0.0) | |\n| [uuid](https://togithub.com/uuidjs/uuid) | dependencies | major |\n[~~`9.0.0` ->\n`11.0.3`~~](https://renovatebot.com/diffs/npm/uuid/9.0.0/11.0.3)`9.0.0`\n-> `10.0.0` | ~~`11.0.5` (+1)~~ |\n\n---\n\n### Release Notes\n\n<details>\n<summary>sverweij/dependency-cruiser (dependency-cruiser)</summary>\n\n###\n[`v16.8.0`](https://togithub.com/sverweij/dependency-cruiser/releases/tag/v16.8.0)\n\n[Compare\nSource](https://togithub.com/sverweij/dependency-cruiser/compare/v16.7.0...v16.8.0)\n\n#### ✨ features\n\n-\n[`dd81580`]( |
||
|
Kibana Machine
|
8e5484c3e4
|
[8.x] [ML] Update JSON schemas for code editors (#207706) (#207723)
# Backport This will backport the following commits from `main` to `8.x`: - [[ML] Update JSON schemas for code editors (#207706)](https://github.com/elastic/kibana/pull/207706) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Dima Arnautov","email":"dmitrii.arnautov@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T10:36:31Z","message":"[ML] Update JSON schemas for code editors (#207706)\n\n## Summary\r\n\r\n- Updates the default path to the openapi file \r\n- Updates JSON schemas for ML and Transform code editors with the latest\r\nchanges from elasticsearch-specification","sha":"ab2379f1f7c4563a5f3c119033bcff5397bab0f6","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement",":ml","Feature:Anomaly Detection","Feature:Transforms","v9.0.0","Team:ML","backport:version","v8.18.0"],"title":"[ML] Update JSON schemas for code editors ","number":207706,"url":"https://github.com/elastic/kibana/pull/207706","mergeCommit":{"message":"[ML] Update JSON schemas for code editors (#207706)\n\n## Summary\r\n\r\n- Updates the default path to the openapi file \r\n- Updates JSON schemas for ML and Transform code editors with the latest\r\nchanges from elasticsearch-specification","sha":"ab2379f1f7c4563a5f3c119033bcff5397bab0f6"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207706","number":207706,"mergeCommit":{"message":"[ML] Update JSON schemas for code editors (#207706)\n\n## Summary\r\n\r\n- Updates the default path to the openapi file \r\n- Updates JSON schemas for ML and Transform code editors with the latest\r\nchanges from elasticsearch-specification","sha":"ab2379f1f7c4563a5f3c119033bcff5397bab0f6"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co> |
||
|
Kibana Machine
|
62501098b3
|
[8.x] fix: [Security:Rules:SharedExceptionList] The toggle button for linking a rule on add rule exception panel is missing discernible text (#205600) (#207700)
# Backport This will backport the following commits from `main` to `8.x`: - [fix: [Security:Rules:SharedExceptionList] The toggle button for linking a rule on add rule exception panel is missing discernible text (#205600)](https://github.com/elastic/kibana/pull/205600) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-01-22T08:23:13Z","message":"fix: [Security:Rules:SharedExceptionList] The toggle button for linking a rule on add rule exception panel is missing discernible text (#205600)\n\nCloses: #204667\r\n\r\n## Summary\r\nThe toggle button for linking to a rule on Add rule exception panel is\r\nmissing discernible text\r\n**Preconditions**\r\nSecurity -> Rules->Shared exceptions ->Add rule exception panel is open\r\n\r\n## Changes made: \r\n1. Added 'label' attribute for **EuiSwitch**\r\n\r\n### Screen\r\n\r\n\r\n","sha":"a878c98ecc312ff7192698cde6afd38060c124b8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","v9.0.0","Team: SecuritySolution","backport:prev-minor"],"title":"fix: [Security:Rules:SharedExceptionList] The toggle button for linking a rule on add rule exception panel is missing discernible text","number":205600,"url":"https://github.com/elastic/kibana/pull/205600","mergeCommit":{"message":"fix: [Security:Rules:SharedExceptionList] The toggle button for linking a rule on add rule exception panel is missing discernible text (#205600)\n\nCloses: #204667\r\n\r\n## Summary\r\nThe toggle button for linking to a rule on Add rule exception panel is\r\nmissing discernible text\r\n**Preconditions**\r\nSecurity -> Rules->Shared exceptions ->Add rule exception panel is open\r\n\r\n## Changes made: \r\n1. Added 'label' attribute for **EuiSwitch**\r\n\r\n### Screen\r\n\r\n\r\n","sha":"a878c98ecc312ff7192698cde6afd38060c124b8"}},"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/205600","number":205600,"mergeCommit":{"message":"fix: [Security:Rules:SharedExceptionList] The toggle button for linking a rule on add rule exception panel is missing discernible text (#205600)\n\nCloses: #204667\r\n\r\n## Summary\r\nThe toggle button for linking to a rule on Add rule exception panel is\r\nmissing discernible text\r\n**Preconditions**\r\nSecurity -> Rules->Shared exceptions ->Add rule exception panel is open\r\n\r\n## Changes made: \r\n1. Added 'label' attribute for **EuiSwitch**\r\n\r\n### Screen\r\n\r\n\r\n","sha":"a878c98ecc312ff7192698cde6afd38060c124b8"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
Jan Monschke
|
8e02172e2e
|
[8.x] [SecuritySolution] Breaking out timeline & note privileges (#201780) (#207367)
# Backport This will backport the following commits from `main` to `8.x`: - [[SecuritySolution] Breaking out timeline & note privileges (#201780)](https://github.com/elastic/kibana/pull/201780) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jan Monschke","email":"jan.monschke@elastic.co"},"sourceCommit":{"committedDate":"2025-01-20T13:09:16Z","message":"[SecuritySolution] Breaking out timeline & note privileges (#201780)\n\n## Summary\n\nEpic: https://github.com/elastic/security-team/issues/7998\n\nIn this PR we're breaking out the `timeline` and `notes` features into\ntheir own feature privilege definition. Previously, access to both\nfeatures was granted implicitly through the `siem` feature. However, we\nfound that this level of access control is not sufficient for all\nclients who wanted a more fine-grained way to grant access to parts of\nsecurity solution.\n\nIn order to break out `timeline` and `notes` from `siem`, we had to\ndeprecate it feature privilege definition for. That is why you'll find\nplenty of changes of `siem` to `siemV2` in this PR. We're making use of\nthe feature privilege's `replacedBy` functionality, allowing for a\nseamless migration of deprecated roles.\n\nThis means that roles that previously granted `siem.all` are now granted\n`siemV2.all`, `timeline.all` and `notes.all` (same for `*.read`).\nExisting users are not impacted and should all still have the correct\naccess. We added tests to make sure this is working as expected.\n\nAlongside the `ui` privileges, this PR also adds dedicated API tags.\nThose tags haven been added to the new and previous version of the\nprivilege definitions to allow for a clean migration:\n\n```mermaid\nflowchart LR\n subgraph v1\n A(siem) --> Y(all)\n A --> X(read)\n Y -->|api| W(timeline_write / timeline_read / notes_read / notes_write)\n X -->|api| V(timeline_read /notes_read)\n end\n\n subgraph v2\n A-->|replacedBy| C[siemV2]\n A-->|replacedBy| E[timeline]\n A-->|replacedBy| G[notes]\n \n\n E --> L(all)\n E --> M(read)\n L -->|api| N(timeline_write / timeline_read)\n M -->|api| P(timeline_read)\n\n G --> Q(all)\n G --> I(read)\n\n Q -->|api| R(notes_write / notes_read)\n I -->|api| S(notes_read)\n end\n```\n\n### Visual changes\n\n#### Hidden/disabled elements\n\nMost of the changes are happening \"under\" the hood and are only\nexpressed in case a user has a role with `timeline.none` or\n`notes.none`. This would hide and/or disable elements that would usually\nallow them to interact with either timeline or the notes feature (within\ntimeline or the event flyout currently).\n\nAs an example, this is how the hover actions look for a user with and\nwithout timeline access:\n\n| With timeline access | Without timeline access |\n| --- | --- |\n| <img width=\"616\" alt=\"Screenshot 2024-12-18 at 17 22 49\"\nsrc=\"https://github.com/user-attachments/assets/a767fbb5-49c8-422a-817e-23e7fe1f0042\"\n/> | <img width=\"724\" alt=\"Screenshot 2024-12-18 at 17 23 29\"\nsrc=\"https://github.com/user-attachments/assets/3490306a-d1c3-41aa-af5b-05a1dd804b47\"\n/> |\n\n#### Roles\n\nAnother visible change of this PR is the addition of `Timeline` and\n`Notes` in the edit-role screen:\n\n| Before | After |\n| ------- | ------ |\n| <img width=\"746\" alt=\"Screenshot 2024-12-12 at 16 31 43\"\nsrc=\"https://github.com/user-attachments/assets/20a80dd4-c214-48a5-8c6e-3dc19c0cbc43\"\n/> | <img width=\"738\" alt=\"Screenshot 2024-12-12 at 16 32 53\"\nsrc=\"https://github.com/user-attachments/assets/afb1eab4-1729-4c4e-9f51-fddabc32b1dd\"\n/> |\n\nWe made sure that for migrated roles that hard `security.all` selected,\nthis screen correctly shows `security.all`, `timeline.all` and\n`notes.all` after the privilege migration.\n\n#### Timeline toast\n\nThere are tons of places in security solution where `Investigate / Add\nto timeline` are shown. We did our best to disable all of these actions\nbut there is no guarantee that this PR catches all the places where we\nlink to timeline (actions). One layer of extra protection is that the\nAPI endpoints don't give access to timelines to users without the\ncorrect privileges. Another one is a Redux middleware that makes sure\ntimelines cannot be shown in missed cases. The following toast will be\nshown instead of the timeline:\n\n<img width=\"354\" alt=\"Screenshot 2024-12-19 at 10 34 23\"\nsrc=\"https://github.com/user-attachments/assets/1304005e-2753-4268-b6e7-bd7e22d8a1e3\"\n/>\n\n### Changes to predefined security roles\n\nAll predefined security roles have been updated to grant the new\nprivileges (in ESS and serverless). In accordance with the migration,\nall roles with `siem.all` have been assigned `siemV2.all`,\n`timeline.all` and `notes.all` (and `*.read` respectively).\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: PhilippeOberti <philippe.oberti@elastic.co>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"1b167d9dc23a9e0e8e47992a37563ca89ccf3c7d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Fleet","v9.0.0","release_note:feature","Team:Threat Hunting:Investigations","backport:prev-minor","ci:cloud-deploy","ci:project-persist-deployment","v8.18.0"],"title":"[SecuritySolution] Breaking out timeline & note privileges","number":201780,"url":"https://github.com/elastic/kibana/pull/201780","mergeCommit":{"message":"[SecuritySolution] Breaking out timeline & note privileges (#201780)\n\n## Summary\n\nEpic: https://github.com/elastic/security-team/issues/7998\n\nIn this PR we're breaking out the `timeline` and `notes` features into\ntheir own feature privilege definition. Previously, access to both\nfeatures was granted implicitly through the `siem` feature. However, we\nfound that this level of access control is not sufficient for all\nclients who wanted a more fine-grained way to grant access to parts of\nsecurity solution.\n\nIn order to break out `timeline` and `notes` from `siem`, we had to\ndeprecate it feature privilege definition for. That is why you'll find\nplenty of changes of `siem` to `siemV2` in this PR. We're making use of\nthe feature privilege's `replacedBy` functionality, allowing for a\nseamless migration of deprecated roles.\n\nThis means that roles that previously granted `siem.all` are now granted\n`siemV2.all`, `timeline.all` and `notes.all` (same for `*.read`).\nExisting users are not impacted and should all still have the correct\naccess. We added tests to make sure this is working as expected.\n\nAlongside the `ui` privileges, this PR also adds dedicated API tags.\nThose tags haven been added to the new and previous version of the\nprivilege definitions to allow for a clean migration:\n\n```mermaid\nflowchart LR\n subgraph v1\n A(siem) --> Y(all)\n A --> X(read)\n Y -->|api| W(timeline_write / timeline_read / notes_read / notes_write)\n X -->|api| V(timeline_read /notes_read)\n end\n\n subgraph v2\n A-->|replacedBy| C[siemV2]\n A-->|replacedBy| E[timeline]\n A-->|replacedBy| G[notes]\n \n\n E --> L(all)\n E --> M(read)\n L -->|api| N(timeline_write / timeline_read)\n M -->|api| P(timeline_read)\n\n G --> Q(all)\n G --> I(read)\n\n Q -->|api| R(notes_write / notes_read)\n I -->|api| S(notes_read)\n end\n```\n\n### Visual changes\n\n#### Hidden/disabled elements\n\nMost of the changes are happening \"under\" the hood and are only\nexpressed in case a user has a role with `timeline.none` or\n`notes.none`. This would hide and/or disable elements that would usually\nallow them to interact with either timeline or the notes feature (within\ntimeline or the event flyout currently).\n\nAs an example, this is how the hover actions look for a user with and\nwithout timeline access:\n\n| With timeline access | Without timeline access |\n| --- | --- |\n| <img width=\"616\" alt=\"Screenshot 2024-12-18 at 17 22 49\"\nsrc=\"https://github.com/user-attachments/assets/a767fbb5-49c8-422a-817e-23e7fe1f0042\"\n/> | <img width=\"724\" alt=\"Screenshot 2024-12-18 at 17 23 29\"\nsrc=\"https://github.com/user-attachments/assets/3490306a-d1c3-41aa-af5b-05a1dd804b47\"\n/> |\n\n#### Roles\n\nAnother visible change of this PR is the addition of `Timeline` and\n`Notes` in the edit-role screen:\n\n| Before | After |\n| ------- | ------ |\n| <img width=\"746\" alt=\"Screenshot 2024-12-12 at 16 31 43\"\nsrc=\"https://github.com/user-attachments/assets/20a80dd4-c214-48a5-8c6e-3dc19c0cbc43\"\n/> | <img width=\"738\" alt=\"Screenshot 2024-12-12 at 16 32 53\"\nsrc=\"https://github.com/user-attachments/assets/afb1eab4-1729-4c4e-9f51-fddabc32b1dd\"\n/> |\n\nWe made sure that for migrated roles that hard `security.all` selected,\nthis screen correctly shows `security.all`, `timeline.all` and\n`notes.all` after the privilege migration.\n\n#### Timeline toast\n\nThere are tons of places in security solution where `Investigate / Add\nto timeline` are shown. We did our best to disable all of these actions\nbut there is no guarantee that this PR catches all the places where we\nlink to timeline (actions). One layer of extra protection is that the\nAPI endpoints don't give access to timelines to users without the\ncorrect privileges. Another one is a Redux middleware that makes sure\ntimelines cannot be shown in missed cases. The following toast will be\nshown instead of the timeline:\n\n<img width=\"354\" alt=\"Screenshot 2024-12-19 at 10 34 23\"\nsrc=\"https://github.com/user-attachments/assets/1304005e-2753-4268-b6e7-bd7e22d8a1e3\"\n/>\n\n### Changes to predefined security roles\n\nAll predefined security roles have been updated to grant the new\nprivileges (in ESS and serverless). In accordance with the migration,\nall roles with `siem.all` have been assigned `siemV2.all`,\n`timeline.all` and `notes.all` (and `*.read` respectively).\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: PhilippeOberti <philippe.oberti@elastic.co>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"1b167d9dc23a9e0e8e47992a37563ca89ccf3c7d"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/201780","number":201780,"mergeCommit":{"message":"[SecuritySolution] Breaking out timeline & note privileges (#201780)\n\n## Summary\n\nEpic: https://github.com/elastic/security-team/issues/7998\n\nIn this PR we're breaking out the `timeline` and `notes` features into\ntheir own feature privilege definition. Previously, access to both\nfeatures was granted implicitly through the `siem` feature. However, we\nfound that this level of access control is not sufficient for all\nclients who wanted a more fine-grained way to grant access to parts of\nsecurity solution.\n\nIn order to break out `timeline` and `notes` from `siem`, we had to\ndeprecate it feature privilege definition for. That is why you'll find\nplenty of changes of `siem` to `siemV2` in this PR. We're making use of\nthe feature privilege's `replacedBy` functionality, allowing for a\nseamless migration of deprecated roles.\n\nThis means that roles that previously granted `siem.all` are now granted\n`siemV2.all`, `timeline.all` and `notes.all` (same for `*.read`).\nExisting users are not impacted and should all still have the correct\naccess. We added tests to make sure this is working as expected.\n\nAlongside the `ui` privileges, this PR also adds dedicated API tags.\nThose tags haven been added to the new and previous version of the\nprivilege definitions to allow for a clean migration:\n\n```mermaid\nflowchart LR\n subgraph v1\n A(siem) --> Y(all)\n A --> X(read)\n Y -->|api| W(timeline_write / timeline_read / notes_read / notes_write)\n X -->|api| V(timeline_read /notes_read)\n end\n\n subgraph v2\n A-->|replacedBy| C[siemV2]\n A-->|replacedBy| E[timeline]\n A-->|replacedBy| G[notes]\n \n\n E --> L(all)\n E --> M(read)\n L -->|api| N(timeline_write / timeline_read)\n M -->|api| P(timeline_read)\n\n G --> Q(all)\n G --> I(read)\n\n Q -->|api| R(notes_write / notes_read)\n I -->|api| S(notes_read)\n end\n```\n\n### Visual changes\n\n#### Hidden/disabled elements\n\nMost of the changes are happening \"under\" the hood and are only\nexpressed in case a user has a role with `timeline.none` or\n`notes.none`. This would hide and/or disable elements that would usually\nallow them to interact with either timeline or the notes feature (within\ntimeline or the event flyout currently).\n\nAs an example, this is how the hover actions look for a user with and\nwithout timeline access:\n\n| With timeline access | Without timeline access |\n| --- | --- |\n| <img width=\"616\" alt=\"Screenshot 2024-12-18 at 17 22 49\"\nsrc=\"https://github.com/user-attachments/assets/a767fbb5-49c8-422a-817e-23e7fe1f0042\"\n/> | <img width=\"724\" alt=\"Screenshot 2024-12-18 at 17 23 29\"\nsrc=\"https://github.com/user-attachments/assets/3490306a-d1c3-41aa-af5b-05a1dd804b47\"\n/> |\n\n#### Roles\n\nAnother visible change of this PR is the addition of `Timeline` and\n`Notes` in the edit-role screen:\n\n| Before | After |\n| ------- | ------ |\n| <img width=\"746\" alt=\"Screenshot 2024-12-12 at 16 31 43\"\nsrc=\"https://github.com/user-attachments/assets/20a80dd4-c214-48a5-8c6e-3dc19c0cbc43\"\n/> | <img width=\"738\" alt=\"Screenshot 2024-12-12 at 16 32 53\"\nsrc=\"https://github.com/user-attachments/assets/afb1eab4-1729-4c4e-9f51-fddabc32b1dd\"\n/> |\n\nWe made sure that for migrated roles that hard `security.all` selected,\nthis screen correctly shows `security.all`, `timeline.all` and\n`notes.all` after the privilege migration.\n\n#### Timeline toast\n\nThere are tons of places in security solution where `Investigate / Add\nto timeline` are shown. We did our best to disable all of these actions\nbut there is no guarantee that this PR catches all the places where we\nlink to timeline (actions). One layer of extra protection is that the\nAPI endpoints don't give access to timelines to users without the\ncorrect privileges. Another one is a Redux middleware that makes sure\ntimelines cannot be shown in missed cases. The following toast will be\nshown instead of the timeline:\n\n<img width=\"354\" alt=\"Screenshot 2024-12-19 at 10 34 23\"\nsrc=\"https://github.com/user-attachments/assets/1304005e-2753-4268-b6e7-bd7e22d8a1e3\"\n/>\n\n### Changes to predefined security roles\n\nAll predefined security roles have been updated to grant the new\nprivileges (in ESS and serverless). In accordance with the migration,\nall roles with `siem.all` have been assigned `siemV2.all`,\n`timeline.all` and `notes.all` (and `*.read` respectively).\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: PhilippeOberti <philippe.oberti@elastic.co>\nCo-authored-by: Steph Milovic <stephanie.milovic@elastic.co>","sha":"1b167d9dc23a9e0e8e47992a37563ca89ccf3c7d"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
Pablo Machado
|
f9bed85a13
|
[8.x] [SecuritySolution] Add service enrichment to detection engine (#206582) (#207708)
# Backport This will backport the following commits from `main` to `8.x`: - [[SecuritySolution] Add service enrichment to detection engine (#206582)](https://github.com/elastic/kibana/pull/206582) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-01-21T16:54:20Z","message":"[SecuritySolution] Add service enrichment to detection engine (#206582)\n\n## Summary\n\n* Add alert enrichment for `service.asset.criticality`,\n`service.risk.calculated_level` and `service.risk.calculated_score_norm`\nfields\n\n* Add `Service Risk Level` and `Service Criticality` columns to the\nalerts table\n\n\n\n\n### How to test?\n* Enable the flag `serviceEntityStoreEnabled `\n* Start an empty kibana instance\n* Add data using the document generator with the `yarn start\nentity-store` command.\n * Add a seed when prompted\n* Assign asset criticality for the service entity you are testing with\n* Ensure the service entity you are testing with has a risk score. \n * You can run the engine from the Risk score page if needed.\n* Add more data using the same seed\n* Force the created rule to run so it generates new alerts\n* Check if the alerts created for the new batch of data have the new\nfield populated.\n\n### How does enrichment work?\nWhen alerts are created, the current asset criticality and risk score\nare fetched and merged into the alert document. These values won't get\nupdated if the risk score or asset changes.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"888dd240bdcaa93340767083653521a44c115845","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","Feature:Detection Rules","release_note:feature","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0"],"title":"[SecuritySolution] Add service enrichment to detection engine","number":206582,"url":"https://github.com/elastic/kibana/pull/206582","mergeCommit":{"message":"[SecuritySolution] Add service enrichment to detection engine (#206582)\n\n## Summary\n\n* Add alert enrichment for `service.asset.criticality`,\n`service.risk.calculated_level` and `service.risk.calculated_score_norm`\nfields\n\n* Add `Service Risk Level` and `Service Criticality` columns to the\nalerts table\n\n\n\n\n### How to test?\n* Enable the flag `serviceEntityStoreEnabled `\n* Start an empty kibana instance\n* Add data using the document generator with the `yarn start\nentity-store` command.\n * Add a seed when prompted\n* Assign asset criticality for the service entity you are testing with\n* Ensure the service entity you are testing with has a risk score. \n * You can run the engine from the Risk score page if needed.\n* Add more data using the same seed\n* Force the created rule to run so it generates new alerts\n* Check if the alerts created for the new batch of data have the new\nfield populated.\n\n### How does enrichment work?\nWhen alerts are created, the current asset criticality and risk score\nare fetched and merged into the alert document. These values won't get\nupdated if the risk score or asset changes.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"888dd240bdcaa93340767083653521a44c115845"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206582","number":206582,"mergeCommit":{"message":"[SecuritySolution] Add service enrichment to detection engine (#206582)\n\n## Summary\n\n* Add alert enrichment for `service.asset.criticality`,\n`service.risk.calculated_level` and `service.risk.calculated_score_norm`\nfields\n\n* Add `Service Risk Level` and `Service Criticality` columns to the\nalerts table\n\n\n\n\n### How to test?\n* Enable the flag `serviceEntityStoreEnabled `\n* Start an empty kibana instance\n* Add data using the document generator with the `yarn start\nentity-store` command.\n * Add a seed when prompted\n* Assign asset criticality for the service entity you are testing with\n* Ensure the service entity you are testing with has a risk score. \n * You can run the engine from the Risk score page if needed.\n* Add more data using the same seed\n* Force the created rule to run so it generates new alerts\n* Check if the alerts created for the new batch of data have the new\nfield populated.\n\n### How does enrichment work?\nWhen alerts are created, the current asset criticality and risk score\nare fetched and merged into the alert document. These values won't get\nupdated if the risk score or asset changes.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"888dd240bdcaa93340767083653521a44c115845"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
c864f54c1a
|
[8.x] Update dependency elastic-apm-node to ^4.11.0 (main) (#207313) (#207705)
# Backport This will backport the following commits from `main` to `8.x`: - [Update dependency elastic-apm-node to ^4.11.0 (main) (#207313)](https://github.com/elastic/kibana/pull/207313) <!--- 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-01-22T08:48:20Z","message":"Update dependency elastic-apm-node to ^4.11.0 (main) (#207313)","sha":"fc72ba9ec9ac53f1c3acbc9321323b4b465dfa5d","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","v9.0.0","backport:prev-minor"],"title":"Update dependency elastic-apm-node to ^4.11.0 (main)","number":207313,"url":"https://github.com/elastic/kibana/pull/207313","mergeCommit":{"message":"Update dependency elastic-apm-node to ^4.11.0 (main) (#207313)","sha":"fc72ba9ec9ac53f1c3acbc9321323b4b465dfa5d"}},"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/207313","number":207313,"mergeCommit":{"message":"Update dependency elastic-apm-node to ^4.11.0 (main) (#207313)","sha":"fc72ba9ec9ac53f1c3acbc9321323b4b465dfa5d"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Jean-Louis Leysens
|
4ca8cef44b
|
Fix 8.x 9 forward compat tests part ii (#207407)
## Summary Follow up from https://github.com/elastic/kibana/pull/206624 aimed at fixing failing compat tests: https://buildkite.com/elastic/kibana-es-forward-compatibility-testing-9-dot-0/builds?branch=8.x ### Core * Fixed jest integration tests, generated new archives * Skipped the UA tests for 8.x -> 9 if ES >8, I assume these tests only make sense if ES is on v8 ### Security solution ES|QL * Made the `metadata [...` test only run when ES is v8 ### Kibana management * Made the unfreeze test only run when ES is v8 |
||
|
Kibana Machine
|
7a48da7ba1
|
[8.x] [ES `body` removal] `@elastic/stack-monitoring` (#204865) (#207703)
# Backport This will backport the following commits from `main` to `8.x`: - [[ES `body` removal] `@elastic/stack-monitoring` (#204865)](https://github.com/elastic/kibana/pull/204865) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alejandro Fernández Haro","email":"alejandro.haro@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T08:25:21Z","message":"[ES `body` removal] `@elastic/stack-monitoring` (#204865)","sha":"ca26eaa718ead4c5ba75177e183adb5ad8d9c287","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Monitoring","release_note:skip","Feature:Stack Monitoring","v9.0.0","backport:prev-minor"],"title":"[ES `body` removal] `@elastic/stack-monitoring`","number":204865,"url":"https://github.com/elastic/kibana/pull/204865","mergeCommit":{"message":"[ES `body` removal] `@elastic/stack-monitoring` (#204865)","sha":"ca26eaa718ead4c5ba75177e183adb5ad8d9c287"}},"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/204865","number":204865,"mergeCommit":{"message":"[ES `body` removal] `@elastic/stack-monitoring` (#204865)","sha":"ca26eaa718ead4c5ba75177e183adb5ad8d9c287"}}]}] BACKPORT--> Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co> |
||
|
Kibana Machine
|
1885eff54c
|
[8.x] fix: [Security:Explore:Users page]Add new timeline or template button dialog cannot be closed (#207232) (#207702)
# Backport This will backport the following commits from `main` to `8.x`: - [fix: [Security:Explore:Users page]Add new timeline or template button dialog cannot be closed (#207232)](https://github.com/elastic/kibana/pull/207232) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Alexey Antonov","email":"alexwizp@gmail.com"},"sourceCommit":{"committedDate":"2025-01-22T08:22:55Z","message":"fix: [Security:Explore:Users page]Add new timeline or template button dialog cannot be closed (#207232)\n\nCloses: #205377\r\n\r\n**Description**\r\nUsers don't get stuck on elements, dialogs can be closed by pressing\r\nEsc.\r\n\r\n**Preconditions**\r\nSecurity -> Explore -> Users page.\r\n\r\n**Steps to reproduce**\r\n\r\n1.Navigate to Add new timeline or template button.\r\n2.Press Enter.\r\n3.Press Esc.\r\n4.Press Tab few times.\r\n5.Observe page.\r\n\r\n\r\n**Changes made:**\r\n1. Fixed typo, method should be called","sha":"e2c138bca119015715e26ac519f2eb75b98e1541","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Project:Accessibility","release_note:skip","v9.0.0","backport:prev-minor"],"title":"fix: [Security:Explore:Users page]Add new timeline or template button dialog cannot be closed","number":207232,"url":"https://github.com/elastic/kibana/pull/207232","mergeCommit":{"message":"fix: [Security:Explore:Users page]Add new timeline or template button dialog cannot be closed (#207232)\n\nCloses: #205377\r\n\r\n**Description**\r\nUsers don't get stuck on elements, dialogs can be closed by pressing\r\nEsc.\r\n\r\n**Preconditions**\r\nSecurity -> Explore -> Users page.\r\n\r\n**Steps to reproduce**\r\n\r\n1.Navigate to Add new timeline or template button.\r\n2.Press Enter.\r\n3.Press Esc.\r\n4.Press Tab few times.\r\n5.Observe page.\r\n\r\n\r\n**Changes made:**\r\n1. Fixed typo, method should be called","sha":"e2c138bca119015715e26ac519f2eb75b98e1541"}},"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/207232","number":207232,"mergeCommit":{"message":"fix: [Security:Explore:Users page]Add new timeline or template button dialog cannot be closed (#207232)\n\nCloses: #205377\r\n\r\n**Description**\r\nUsers don't get stuck on elements, dialogs can be closed by pressing\r\nEsc.\r\n\r\n**Preconditions**\r\nSecurity -> Explore -> Users page.\r\n\r\n**Steps to reproduce**\r\n\r\n1.Navigate to Add new timeline or template button.\r\n2.Press Enter.\r\n3.Press Esc.\r\n4.Press Tab few times.\r\n5.Observe page.\r\n\r\n\r\n**Changes made:**\r\n1. Fixed typo, method should be called","sha":"e2c138bca119015715e26ac519f2eb75b98e1541"}}]}] BACKPORT--> Co-authored-by: Alexey Antonov <alexwizp@gmail.com> |
||
|
Kibana Machine
|
04c7f8c937
|
[8.x] [Lens][Embeddable] Remove unused cruft from by-reference panels when saving in a dashboard (#206740) (#207699)
# Backport This will backport the following commits from `main` to `8.x`: - [[Lens][Embeddable] Remove unused cruft from by-reference panels when saving in a dashboard (#206740)](https://github.com/elastic/kibana/pull/206740) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Marco Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-01-22T08:07:59Z","message":"[Lens][Embeddable] Remove unused cruft from by-reference panels when saving in a dashboard (#206740)\n\n## Summary\r\n\r\nFixes #206596 \r\n\r\nThis PR fixes a bug that made dashboard save extra (unused) state within\r\nthe dashboard saved object when a panel is by-references.\r\nLuckily this has only the side effect of using more storage than usual,\r\nas the Lens SO initializer would use fresh state from the Content\r\nManagement to load, but it would be great to be as lean as possible\r\nhere.\r\n\r\n### Checklist\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","sha":"b0b44bbd22f7be4e651f4003bea7f3adc5c9f2a8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","v9.0.0","backport:prev-minor","Feature:Embeddables"],"title":"[Lens][Embeddable] Remove unused cruft from by-reference panels when saving in a dashboard","number":206740,"url":"https://github.com/elastic/kibana/pull/206740","mergeCommit":{"message":"[Lens][Embeddable] Remove unused cruft from by-reference panels when saving in a dashboard (#206740)\n\n## Summary\r\n\r\nFixes #206596 \r\n\r\nThis PR fixes a bug that made dashboard save extra (unused) state within\r\nthe dashboard saved object when a panel is by-references.\r\nLuckily this has only the side effect of using more storage than usual,\r\nas the Lens SO initializer would use fresh state from the Content\r\nManagement to load, but it would be great to be as lean as possible\r\nhere.\r\n\r\n### Checklist\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","sha":"b0b44bbd22f7be4e651f4003bea7f3adc5c9f2a8"}},"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/206740","number":206740,"mergeCommit":{"message":"[Lens][Embeddable] Remove unused cruft from by-reference panels when saving in a dashboard (#206740)\n\n## Summary\r\n\r\nFixes #206596 \r\n\r\nThis PR fixes a bug that made dashboard save extra (unused) state within\r\nthe dashboard saved object when a panel is by-references.\r\nLuckily this has only the side effect of using more storage than usual,\r\nas the Lens SO initializer would use fresh state from the Content\r\nManagement to load, but it would be great to be as lean as possible\r\nhere.\r\n\r\n### Checklist\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","sha":"b0b44bbd22f7be4e651f4003bea7f3adc5c9f2a8"}}]}] BACKPORT--> Co-authored-by: Marco Liberati <dej611@users.noreply.github.com> |
||
|
Kibana Machine
|
db7e3e1b59
|
[8.x] [inference] surface error message from connector (#207393) (#207693)
# Backport This will backport the following commits from `main` to `8.x`: - [[inference] surface error message from connector (#207393)](https://github.com/elastic/kibana/pull/207393) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Pierre Gayvallet","email":"pierre.gayvallet@elastic.co"},"sourceCommit":{"committedDate":"2025-01-22T07:23:16Z","message":"[inference] surface error message from connector (#207393)\n\n## Summary\r\n\r\nIn case of error during the connector's execution, the inference\r\nadapters were not properly propagating the error message. This PR\r\naddresses it.\r\n\r\n### Before\r\n\r\n<img width=\"368\" alt=\"Screenshot 2025-01-21 at 14 05 30\"\r\nsrc=\"https://github.com/user-attachments/assets/65cce33d-cdca-442e-bf31-9bf09c4c6800\"\r\n/>\r\n\r\n### After\r\n\r\n<img width=\"738\" alt=\"Screenshot 2025-01-21 at 14 04 44\"\r\nsrc=\"https://github.com/user-attachments/assets/7d4fdee8-5989-47a1-8e56-21621f9b79fc\"\r\n/>","sha":"52be83272471a7fb87ed95c45bbab33e9a33757b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","Team:AI Infra","v8.18.0"],"title":"[inference] surface error message from connector","number":207393,"url":"https://github.com/elastic/kibana/pull/207393","mergeCommit":{"message":"[inference] surface error message from connector (#207393)\n\n## Summary\r\n\r\nIn case of error during the connector's execution, the inference\r\nadapters were not properly propagating the error message. This PR\r\naddresses it.\r\n\r\n### Before\r\n\r\n<img width=\"368\" alt=\"Screenshot 2025-01-21 at 14 05 30\"\r\nsrc=\"https://github.com/user-attachments/assets/65cce33d-cdca-442e-bf31-9bf09c4c6800\"\r\n/>\r\n\r\n### After\r\n\r\n<img width=\"738\" alt=\"Screenshot 2025-01-21 at 14 04 44\"\r\nsrc=\"https://github.com/user-attachments/assets/7d4fdee8-5989-47a1-8e56-21621f9b79fc\"\r\n/>","sha":"52be83272471a7fb87ed95c45bbab33e9a33757b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/207393","number":207393,"mergeCommit":{"message":"[inference] surface error message from connector (#207393)\n\n## Summary\r\n\r\nIn case of error during the connector's execution, the inference\r\nadapters were not properly propagating the error message. This PR\r\naddresses it.\r\n\r\n### Before\r\n\r\n<img width=\"368\" alt=\"Screenshot 2025-01-21 at 14 05 30\"\r\nsrc=\"https://github.com/user-attachments/assets/65cce33d-cdca-442e-bf31-9bf09c4c6800\"\r\n/>\r\n\r\n### After\r\n\r\n<img width=\"738\" alt=\"Screenshot 2025-01-21 at 14 04 44\"\r\nsrc=\"https://github.com/user-attachments/assets/7d4fdee8-5989-47a1-8e56-21621f9b79fc\"\r\n/>","sha":"52be83272471a7fb87ed95c45bbab33e9a33757b"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pierre Gayvallet <pierre.gayvallet@elastic.co> |
||
David Sánchez
|
8c09c9a0e4
|
[8.x] [Security Solution] [EDR Workflows] Adds upgrade notes for management deprecated apis (#206903) (#207403)
# Backport This will backport the following commits from `main` to `8.x`: - [[Security Solution] [EDR Workflows] Adds upgrade notes for management deprecated apis (#206903)](https://github.com/elastic/kibana/pull/206903) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2025-01-21T14:56:03Z","message":"[Security Solution] [EDR Workflows] Adds upgrade notes for management deprecated apis (#206903)\n\n## Summary\r\n\r\nIt adds upgrade notes and create docs link for Endpoint management\r\ndeprecated apis in 9.0.\r\n\r\nThis pr is for main (9.0) and 8.x (8.18) and will follow up with this\r\none on 8.x branch: https://github.com/elastic/kibana/pull/206904 in\r\norder to add these notes to the Upgrade Assistant for these deprecated\r\napi's\r\n\r\nThe Api routes were already removed in this pr (only in main):\r\nhttps://github.com/elastic/kibana/pull/199598\r\n\r\n---------\r\n\r\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"adb6cded6ab778b59378f5be78a8ed563470b5aa","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:deprecation","v9.0.0","Team:Defend Workflows","backport:version","v8.18.0"],"title":"[Security Solution] [EDR Workflows] Adds upgrade notes for management deprecated apis","number":206903,"url":"https://github.com/elastic/kibana/pull/206903","mergeCommit":{"message":"[Security Solution] [EDR Workflows] Adds upgrade notes for management deprecated apis (#206903)\n\n## Summary\r\n\r\nIt adds upgrade notes and create docs link for Endpoint management\r\ndeprecated apis in 9.0.\r\n\r\nThis pr is for main (9.0) and 8.x (8.18) and will follow up with this\r\none on 8.x branch: https://github.com/elastic/kibana/pull/206904 in\r\norder to add these notes to the Upgrade Assistant for these deprecated\r\napi's\r\n\r\nThe Api routes were already removed in this pr (only in main):\r\nhttps://github.com/elastic/kibana/pull/199598\r\n\r\n---------\r\n\r\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"adb6cded6ab778b59378f5be78a8ed563470b5aa"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/206903","number":206903,"mergeCommit":{"message":"[Security Solution] [EDR Workflows] Adds upgrade notes for management deprecated apis (#206903)\n\n## Summary\r\n\r\nIt adds upgrade notes and create docs link for Endpoint management\r\ndeprecated apis in 9.0.\r\n\r\nThis pr is for main (9.0) and 8.x (8.18) and will follow up with this\r\none on 8.x branch: https://github.com/elastic/kibana/pull/206904 in\r\norder to add these notes to the Upgrade Assistant for these deprecated\r\napi's\r\n\r\nThe Api routes were already removed in this pr (only in main):\r\nhttps://github.com/elastic/kibana/pull/199598\r\n\r\n---------\r\n\r\nCo-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>\r\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"adb6cded6ab778b59378f5be78a8ed563470b5aa"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
5db5189398
|
[8.x] [search profiler] Move profile button inline with index field (#202253) (#207648)
# Backport This will backport the following commits from `main` to `8.x`: - [[search profiler] Move profile button inline with index field (#202253)](https://github.com/elastic/kibana/pull/202253) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Matthew Kime","email":"matt@mattki.me"},"sourceCommit":{"committedDate":"2025-01-22T04:01:43Z","message":"[search profiler] Move profile button inline with index field (#202253)\n\n## Summary\r\n\r\nAt smaller window sizes, the `Profile` button disappears beneath the\r\ncode editor. Lets move it to the top and shrink it.\r\n\r\n<img width=\"1051\" alt=\"Screenshot 2024-11-30 at 11 47 27 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\">","sha":"c12c88d243840d498b767a5f9b29f2748d4b2ff3","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Kibana Management","release_note:skip","Feature:Search Profiler","v9.0.0","backport:prev-major"],"title":"[search profiler] Move profile button inline with index field","number":202253,"url":"https://github.com/elastic/kibana/pull/202253","mergeCommit":{"message":"[search profiler] Move profile button inline with index field (#202253)\n\n## Summary\r\n\r\nAt smaller window sizes, the `Profile` button disappears beneath the\r\ncode editor. Lets move it to the top and shrink it.\r\n\r\n<img width=\"1051\" alt=\"Screenshot 2024-11-30 at 11 47 27 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\">","sha":"c12c88d243840d498b767a5f9b29f2748d4b2ff3"}},"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/202253","number":202253,"mergeCommit":{"message":"[search profiler] Move profile button inline with index field (#202253)\n\n## Summary\r\n\r\nAt smaller window sizes, the `Profile` button disappears beneath the\r\ncode editor. Lets move it to the top and shrink it.\r\n\r\n<img width=\"1051\" alt=\"Screenshot 2024-11-30 at 11 47 27 PM\"\r\nsrc=\"https://github.com/user-attachments/assets/1d8b99cd-1b07-43cc-8d75-597b37f74e59\">","sha":"c12c88d243840d498b767a5f9b29f2748d4b2ff3"}}]}] BACKPORT--> Co-authored-by: Matthew Kime <matt@mattki.me> |
||
seanrathier
|
3f654766d6
|
[8.x] [Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965) (#206985)
# Backport This will backport the following commits from `main` to `8.x`: - [[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)](https://github.com/elastic/kibana/pull/205965) <!--- Backport version: 9.6.4 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"seanrathier","email":"sean.rathier@gmail.com"},"sourceCommit":{"committedDate":"2025-01-15T17:07:02Z","message":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)","sha":"c30212f9c0d091bd2564592ac21a6ef2f30368c8","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","Team:Cloud Security","backport:prev-minor","ci:project-deploy-security"],"title":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology.","number":205965,"url":"https://github.com/elastic/kibana/pull/205965","mergeCommit":{"message":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)","sha":"c30212f9c0d091bd2564592ac21a6ef2f30368c8"}},"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/205965","number":205965,"mergeCommit":{"message":"[Cloud Security] Default CSPM integration to use Agentless as the setup technology. (#205965)","sha":"c30212f9c0d091bd2564592ac21a6ef2f30368c8"}}]}] BACKPORT--> |