Commit graph

63338 commits

Author SHA1 Message Date
Kibana Machine
f6af110dd0
[8.8] [Security Solution][Endpoint][Response Actions] Set default start/end dates for response actions history page (#158407) (#158593)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution][Endpoint][Response Actions] Set default start/end
dates for response actions history page
(#158407)](https://github.com/elastic/kibana/pull/158407)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Ashokaditya","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-26T17:21:47Z","message":"[Security
Solution][Endpoint][Response Actions] Set default start/end dates for
response actions history page (#158407)\n\n## Summary\r\n\r\nFixes a bug
on the response actions history page where even though the\r\ndate range
filter shows `Last 24 hours` the table actually shows all\r\nactions
log.\r\n\r\nfixes elastic/kibana/issues/157676\r\n\r\n### Checklist\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":"b2355a9d333bf606b3df5ad5903db584d74291aa","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Defend
Workflows","OLM
Sprint","v8.9.0","v8.8.1"],"number":158407,"url":"https://github.com/elastic/kibana/pull/158407","mergeCommit":{"message":"[Security
Solution][Endpoint][Response Actions] Set default start/end dates for
response actions history page (#158407)\n\n## Summary\r\n\r\nFixes a bug
on the response actions history page where even though the\r\ndate range
filter shows `Last 24 hours` the table actually shows all\r\nactions
log.\r\n\r\nfixes elastic/kibana/issues/157676\r\n\r\n### Checklist\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":"b2355a9d333bf606b3df5ad5903db584d74291aa"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158407","number":158407,"mergeCommit":{"message":"[Security
Solution][Endpoint][Response Actions] Set default start/end dates for
response actions history page (#158407)\n\n## Summary\r\n\r\nFixes a bug
on the response actions history page where even though the\r\ndate range
filter shows `Last 24 hours` the table actually shows all\r\nactions
log.\r\n\r\nfixes elastic/kibana/issues/157676\r\n\r\n### Checklist\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":"b2355a9d333bf606b3df5ad5903db584d74291aa"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Ashokaditya <1849116+ashokaditya@users.noreply.github.com>
2023-05-30 07:21:19 -07:00
Ashokaditya
0665fb4f62
[8.8] [Security Solutions][Endpoint][Response Actions] File operations cypress tests (#156604) (#158187)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solutions][Endpoint][Response Actions] File operations
cypress tests (#156604)](https://github.com/elastic/kibana/pull/156604)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Ashokaditya","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-22T13:30:40Z","message":"[Security
Solutions][Endpoint][Response Actions] File operations cypress tests
(#156604)\n\n## Summary\r\n\r\nAdds e2e tests for `get-file` and
`execute` response actions.\r\n\r\n~- [ ] Test response actions fail
without signing~\r\n- [x] Ensure other endpoint tests are not using the
same endpoint for\r\ntests\r\n \r\n### Checklist\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":"9b50ae9546565793808c4ac710b790edacc584a2","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","OLM
Sprint","v8.8.0","v8.9.0"],"number":156604,"url":"https://github.com/elastic/kibana/pull/156604","mergeCommit":{"message":"[Security
Solutions][Endpoint][Response Actions] File operations cypress tests
(#156604)\n\n## Summary\r\n\r\nAdds e2e tests for `get-file` and
`execute` response actions.\r\n\r\n~- [ ] Test response actions fail
without signing~\r\n- [x] Ensure other endpoint tests are not using the
same endpoint for\r\ntests\r\n \r\n### Checklist\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":"9b50ae9546565793808c4ac710b790edacc584a2"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/156604","number":156604,"mergeCommit":{"message":"[Security
Solutions][Endpoint][Response Actions] File operations cypress tests
(#156604)\n\n## Summary\r\n\r\nAdds e2e tests for `get-file` and
`execute` response actions.\r\n\r\n~- [ ] Test response actions fail
without signing~\r\n- [x] Ensure other endpoint tests are not using the
same endpoint for\r\ntests\r\n \r\n### Checklist\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":"9b50ae9546565793808c4ac710b790edacc584a2"}}]}]
BACKPORT-->
2023-05-30 03:11:39 -07:00
Kibana Machine
a1590a7eed
[8.8] [Discover] Fix grid theme (#158231) (#158643)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Discover] Fix grid theme
(#158231)](https://github.com/elastic/kibana/pull/158231)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Julia
Rechkunova","email":"julia.rechkunova@elastic.co"},"sourceCommit":{"committedDate":"2023-05-30T05:31:25Z","message":"[Discover]
Fix grid theme (#158231)\n\nAddresses
https://github.com/elastic/kibana/issues/158201\r\n\r\n##
Summary\r\n\r\nThis PR fixes grid row selection in dark
mode.\r\n\r\nBefore:\r\n<img width=\"300\" alt=\"Screenshot 2023-05-23
at 09 53
11\"\r\nsrc=\"e447ebb5-ca75-4778-84a7-ec654aca3709\">\r\n\r\nAfter:\r\n<img
width=\"300\" alt=\"Screenshot 2023-05-23 at 09 52
44\"\r\nsrc=\"86f7ccd0-a306-426b-9fcb-91d9131a7da6\">\r\n\r\nFor
testing:\r\nEnable dark mode on User Profile
page.","sha":"e928b519f31c73e45305c1524430d978081ee0ea","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:fix","Team:DataDiscovery","backport:prev-minor","v8.9.0"],"number":158231,"url":"https://github.com/elastic/kibana/pull/158231","mergeCommit":{"message":"[Discover]
Fix grid theme (#158231)\n\nAddresses
https://github.com/elastic/kibana/issues/158201\r\n\r\n##
Summary\r\n\r\nThis PR fixes grid row selection in dark
mode.\r\n\r\nBefore:\r\n<img width=\"300\" alt=\"Screenshot 2023-05-23
at 09 53
11\"\r\nsrc=\"e447ebb5-ca75-4778-84a7-ec654aca3709\">\r\n\r\nAfter:\r\n<img
width=\"300\" alt=\"Screenshot 2023-05-23 at 09 52
44\"\r\nsrc=\"86f7ccd0-a306-426b-9fcb-91d9131a7da6\">\r\n\r\nFor
testing:\r\nEnable dark mode on User Profile
page.","sha":"e928b519f31c73e45305c1524430d978081ee0ea"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158231","number":158231,"mergeCommit":{"message":"[Discover]
Fix grid theme (#158231)\n\nAddresses
https://github.com/elastic/kibana/issues/158201\r\n\r\n##
Summary\r\n\r\nThis PR fixes grid row selection in dark
mode.\r\n\r\nBefore:\r\n<img width=\"300\" alt=\"Screenshot 2023-05-23
at 09 53
11\"\r\nsrc=\"e447ebb5-ca75-4778-84a7-ec654aca3709\">\r\n\r\nAfter:\r\n<img
width=\"300\" alt=\"Screenshot 2023-05-23 at 09 52
44\"\r\nsrc=\"86f7ccd0-a306-426b-9fcb-91d9131a7da6\">\r\n\r\nFor
testing:\r\nEnable dark mode on User Profile
page.","sha":"e928b519f31c73e45305c1524430d978081ee0ea"}}]}] BACKPORT-->

Co-authored-by: Julia Rechkunova <julia.rechkunova@elastic.co>
2023-05-29 23:42:41 -07:00
Konrad Szwarc
f97c2cc0cd
[8.8] [Defend Workflows][E2E]Get file command from response console (#156159) (#158542)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Defend Workflows][E2E]Get file command from response console
(#156159)](https://github.com/elastic/kibana/pull/156159)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Konrad
Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2023-05-16T17:55:57Z","message":"[Defend
Workflows][E2E]Get file command from response console (#156159)\n\nThis
PR tackles `get-file` command issued from response console. Two\r\ntests
are
included:\r\n1.\r\n`x-pack/plugins/security_solution/public/management/cypress/e2e/mocked_data/response_console.cy.ts`\r\nmocked
data\r\n2.\r\n`x-pack/plugins/security_solution/public/management/cypress/e2e/endpoint/response_console.cy.ts`\r\nreal
endpoint\r\n\r\n---------\r\n\r\nCo-authored-by: Patryk Kopycinski
<contact@patrykkopycinski.com>","sha":"cf6f350ed21eb86053e54005a5d59b1ff64a2d0d","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","v8.8.0","v8.9.0"],"number":156159,"url":"https://github.com/elastic/kibana/pull/156159","mergeCommit":{"message":"[Defend
Workflows][E2E]Get file command from response console (#156159)\n\nThis
PR tackles `get-file` command issued from response console. Two\r\ntests
are
included:\r\n1.\r\n`x-pack/plugins/security_solution/public/management/cypress/e2e/mocked_data/response_console.cy.ts`\r\nmocked
data\r\n2.\r\n`x-pack/plugins/security_solution/public/management/cypress/e2e/endpoint/response_console.cy.ts`\r\nreal
endpoint\r\n\r\n---------\r\n\r\nCo-authored-by: Patryk Kopycinski
<contact@patrykkopycinski.com>","sha":"cf6f350ed21eb86053e54005a5d59b1ff64a2d0d"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/156159","number":156159,"mergeCommit":{"message":"[Defend
Workflows][E2E]Get file command from response console (#156159)\n\nThis
PR tackles `get-file` command issued from response console. Two\r\ntests
are
included:\r\n1.\r\n`x-pack/plugins/security_solution/public/management/cypress/e2e/mocked_data/response_console.cy.ts`\r\nmocked
data\r\n2.\r\n`x-pack/plugins/security_solution/public/management/cypress/e2e/endpoint/response_console.cy.ts`\r\nreal
endpoint\r\n\r\n---------\r\n\r\nCo-authored-by: Patryk Kopycinski
<contact@patrykkopycinski.com>","sha":"cf6f350ed21eb86053e54005a5d59b1ff64a2d0d"}}]}]
BACKPORT-->

Co-authored-by: Ashokaditya <1849116+ashokaditya@users.noreply.github.com>
2023-05-26 13:39:28 -07:00
Kibana Machine
a47810d7c8
[8.8] [Windows] Fix string comparison in bat scripts for default dir. (#158517) (#158595)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Windows] Fix string comparison in bat scripts for default dir.
(#158517)](https://github.com/elastic/kibana/pull/158517)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Brad
White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-26T16:26:56Z","message":"[Windows]
Fix string comparison in bat scripts for default dir. (#158517)\n\n##
Summary\r\n \r\nFixes #137477\r\n\r\nThe `node.options` file was not
being found if `KBN_PATH_CONF` was not\r\nset because the default
directory fallback condition was failing.\r\n\r\n`kibana.bat` before
fix, can see the flag I added in\r\n`config/node.options` is missing and
default options are
used:\r\n\r\n\r\n![broken](178f75a5-f3ec-4785-bd7c-aa609e43b786)\r\n\r\n\r\nThe
flag is correctly added after
fix:\r\n\r\n\r\n![fixed](f607a7b3-cc04-40ea-9608-db6466b0333f)\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7655cb9e9e1c6da0266abec65f5c1399983bb252","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","ci:build-all-platforms","backport:prev-MAJOR","v8.9.0"],"number":158517,"url":"https://github.com/elastic/kibana/pull/158517","mergeCommit":{"message":"[Windows]
Fix string comparison in bat scripts for default dir. (#158517)\n\n##
Summary\r\n \r\nFixes #137477\r\n\r\nThe `node.options` file was not
being found if `KBN_PATH_CONF` was not\r\nset because the default
directory fallback condition was failing.\r\n\r\n`kibana.bat` before
fix, can see the flag I added in\r\n`config/node.options` is missing and
default options are
used:\r\n\r\n\r\n![broken](178f75a5-f3ec-4785-bd7c-aa609e43b786)\r\n\r\n\r\nThe
flag is correctly added after
fix:\r\n\r\n\r\n![fixed](f607a7b3-cc04-40ea-9608-db6466b0333f)\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7655cb9e9e1c6da0266abec65f5c1399983bb252"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158517","number":158517,"mergeCommit":{"message":"[Windows]
Fix string comparison in bat scripts for default dir. (#158517)\n\n##
Summary\r\n \r\nFixes #137477\r\n\r\nThe `node.options` file was not
being found if `KBN_PATH_CONF` was not\r\nset because the default
directory fallback condition was failing.\r\n\r\n`kibana.bat` before
fix, can see the flag I added in\r\n`config/node.options` is missing and
default options are
used:\r\n\r\n\r\n![broken](178f75a5-f3ec-4785-bd7c-aa609e43b786)\r\n\r\n\r\nThe
flag is correctly added after
fix:\r\n\r\n\r\n![fixed](f607a7b3-cc04-40ea-9608-db6466b0333f)\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"7655cb9e9e1c6da0266abec65f5c1399983bb252"}}]}]
BACKPORT-->

Co-authored-by: Brad White <Ikuni17@users.noreply.github.com>
2023-05-26 12:08:26 -07:00
Kibana Machine
35f824ab1f skip failing test suite (#157776) 2023-05-26 14:43:08 -04:00
Kibana Machine
080c89ad61
[8.8] Update network filters. (#158353) (#158589)
# Backport

This will backport the following commits from `main` to `8.8`:
- [Update network filters.
(#158353)](https://github.com/elastic/kibana/pull/158353)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Pete
Hampton","email":"pjhampton@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-26T16:35:58Z","message":"Update
network filters. (#158353)\n\n## Summary\r\n\r\nUpdates the prebuilt
rule alerts filterlist to allow through some\r\nadditional network
fields.","sha":"7c5b99f65bcb91077370845e4d525bf854f72d12","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Telemetry","release_note:skip","Team:
SecuritySolution","v8.9.0","v8.8.1"],"number":158353,"url":"https://github.com/elastic/kibana/pull/158353","mergeCommit":{"message":"Update
network filters. (#158353)\n\n## Summary\r\n\r\nUpdates the prebuilt
rule alerts filterlist to allow through some\r\nadditional network
fields.","sha":"7c5b99f65bcb91077370845e4d525bf854f72d12"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158353","number":158353,"mergeCommit":{"message":"Update
network filters. (#158353)\n\n## Summary\r\n\r\nUpdates the prebuilt
rule alerts filterlist to allow through some\r\nadditional network
fields.","sha":"7c5b99f65bcb91077370845e4d525bf854f72d12"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Pete Hampton <pjhampton@users.noreply.github.com>
2023-05-26 11:25:21 -07:00
Kibana Machine
2b5725d558
[8.8] [Security Solution][Alerts] fix missing fields merge on alerts creation (#157142) (#158540)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution][Alerts] fix missing fields merge on alerts
creation (#157142)](https://github.com/elastic/kibana/pull/157142)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Vitalii
Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-26T09:11:16Z","message":"[Security
Solution][Alerts] fix missing fields merge on alerts creation
(#157142)\n\n## Summary\r\n\r\n- addresses
https://github.com/elastic/kibana/issues/152446\r\n- now, instead of
string path to merged field, array path is used in\r\nmerging utilities,
that allows to work with keys, which have `dot` in\r\nnames. For exampe,
instead of `a.b.c.d` - `['a', 'b.c', 'd']`\r\n- addresses
https://github.com/elastic/kibana/issues/153607, by cloning\r\nsource
document, used in tests\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Ievgen Sorokopud
<e40pud@gmail.com>\r\nCo-authored-by: Ryland Herrick
<ryalnd@gmail.com>","sha":"11fba5746fb44e829f76c1299f78f110a12cac25","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","backport:prev-minor","v8.8.0","v8.9.0","Team:Detection
Engine"],"number":157142,"url":"https://github.com/elastic/kibana/pull/157142","mergeCommit":{"message":"[Security
Solution][Alerts] fix missing fields merge on alerts creation
(#157142)\n\n## Summary\r\n\r\n- addresses
https://github.com/elastic/kibana/issues/152446\r\n- now, instead of
string path to merged field, array path is used in\r\nmerging utilities,
that allows to work with keys, which have `dot` in\r\nnames. For exampe,
instead of `a.b.c.d` - `['a', 'b.c', 'd']`\r\n- addresses
https://github.com/elastic/kibana/issues/153607, by cloning\r\nsource
document, used in tests\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Ievgen Sorokopud
<e40pud@gmail.com>\r\nCo-authored-by: Ryland Herrick
<ryalnd@gmail.com>","sha":"11fba5746fb44e829f76c1299f78f110a12cac25"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157142","number":157142,"mergeCommit":{"message":"[Security
Solution][Alerts] fix missing fields merge on alerts creation
(#157142)\n\n## Summary\r\n\r\n- addresses
https://github.com/elastic/kibana/issues/152446\r\n- now, instead of
string path to merged field, array path is used in\r\nmerging utilities,
that allows to work with keys, which have `dot` in\r\nnames. For exampe,
instead of `a.b.c.d` - `['a', 'b.c', 'd']`\r\n- addresses
https://github.com/elastic/kibana/issues/153607, by cloning\r\nsource
document, used in tests\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: Ievgen Sorokopud
<e40pud@gmail.com>\r\nCo-authored-by: Ryland Herrick
<ryalnd@gmail.com>","sha":"11fba5746fb44e829f76c1299f78f110a12cac25"}}]}]
BACKPORT-->

Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>
2023-05-26 10:13:46 -07:00
Ashokaditya
d5e06a0bc2
[8.8] [Security Solution] add doc signing tests (#156916) (#158573)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution] add doc signing tests
(#156916)](https://github.com/elastic/kibana/pull/156916)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Joey F.
Poon","email":"joey.poon@elastic.co"},"sourceCommit":{"committedDate":"2023-05-08T17:17:59Z","message":"[Security
Solution] add doc signing tests
(#156916)","sha":"6591da49df79f67f20c3739f6ae5c1d739e64e3e","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:skip","Team:Defend
Workflows","v8.9.0"],"number":156916,"url":"https://github.com/elastic/kibana/pull/156916","mergeCommit":{"message":"[Security
Solution] add doc signing tests
(#156916)","sha":"6591da49df79f67f20c3739f6ae5c1d739e64e3e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/156916","number":156916,"mergeCommit":{"message":"[Security
Solution] add doc signing tests
(#156916)","sha":"6591da49df79f67f20c3739f6ae5c1d739e64e3e"}}]}]
BACKPORT-->

Co-authored-by: Joey F. Poon <joey.poon@elastic.co>
2023-05-26 09:53:45 -07:00
Kibana Machine
2940ec9f31
[8.8] [ML] Disable delete action for deployed models (#158533) (#158572)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ML] Disable delete action for deployed models
(#158533)](https://github.com/elastic/kibana/pull/158533)

<!--- Backport version: 8.9.7 -->

### 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":"2023-05-26T15:17:38Z","message":"[ML]
Disable delete action for deployed models (#158533)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/157692.\r\n\r\nDisables delete
action for deployed models.\r\n\r\n<img width=\"1506\"
alt=\"image\"\r\nsrc=\"8e44dcca-789e-41c3-9dca-87034f84390b\">\r\n\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/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"59b1ba976720e69588ef2abad92b65fa523f6b9a","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Feature:3rd
Party
Models","Team:ML","v8.9.0","v8.8.1"],"number":158533,"url":"https://github.com/elastic/kibana/pull/158533","mergeCommit":{"message":"[ML]
Disable delete action for deployed models (#158533)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/157692.\r\n\r\nDisables delete
action for deployed models.\r\n\r\n<img width=\"1506\"
alt=\"image\"\r\nsrc=\"8e44dcca-789e-41c3-9dca-87034f84390b\">\r\n\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/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"59b1ba976720e69588ef2abad92b65fa523f6b9a"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158533","number":158533,"mergeCommit":{"message":"[ML]
Disable delete action for deployed models (#158533)\n\n##
Summary\r\n\r\nFixes
https://github.com/elastic/kibana/issues/157692.\r\n\r\nDisables delete
action for deployed models.\r\n\r\n<img width=\"1506\"
alt=\"image\"\r\nsrc=\"8e44dcca-789e-41c3-9dca-87034f84390b\">\r\n\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/packages/kbn-i18n/README.md)\r\n-
[x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"59b1ba976720e69588ef2abad92b65fa523f6b9a"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dima Arnautov <dmitrii.arnautov@elastic.co>
2023-05-26 09:34:28 -07:00
Kibana Machine
eabb7daf21
[8.8] [ML] Stabilize and reenable classification tests (#158555) (#158576)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ML] Stabilize and reenable classification tests
(#158555)](https://github.com/elastic/kibana/pull/158555)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Robert
Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T15:31:57Z","message":"[ML]
Stabilize and reenable classification tests (#158555)\n\n##
Summary\r\n\r\nThis PR stabilizes ML classification creation tests by
closing the\r\ndependent variable combo box earlier. It also reenables
the test suite.\r\n\r\n### Other changes\r\n\r\n- Remove the unused
parameter `testSubj` from\r\n`assertFieldStatContentByType` in the field
stats flyout service\r\n- Remove the unused parameter `fieldType` from
`assertTopValuesContent`\r\nin the field stats flyout
service","sha":"8d54e42bc9bda0d5f32c73a11e23e2a93db80605","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.9.0","v8.8.1"],"number":158555,"url":"https://github.com/elastic/kibana/pull/158555","mergeCommit":{"message":"[ML]
Stabilize and reenable classification tests (#158555)\n\n##
Summary\r\n\r\nThis PR stabilizes ML classification creation tests by
closing the\r\ndependent variable combo box earlier. It also reenables
the test suite.\r\n\r\n### Other changes\r\n\r\n- Remove the unused
parameter `testSubj` from\r\n`assertFieldStatContentByType` in the field
stats flyout service\r\n- Remove the unused parameter `fieldType` from
`assertTopValuesContent`\r\nin the field stats flyout
service","sha":"8d54e42bc9bda0d5f32c73a11e23e2a93db80605"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158555","number":158555,"mergeCommit":{"message":"[ML]
Stabilize and reenable classification tests (#158555)\n\n##
Summary\r\n\r\nThis PR stabilizes ML classification creation tests by
closing the\r\ndependent variable combo box earlier. It also reenables
the test suite.\r\n\r\n### Other changes\r\n\r\n- Remove the unused
parameter `testSubj` from\r\n`assertFieldStatContentByType` in the field
stats flyout service\r\n- Remove the unused parameter `fieldType` from
`assertTopValuesContent`\r\nin the field stats flyout
service","sha":"8d54e42bc9bda0d5f32c73a11e23e2a93db80605"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
2023-05-26 09:29:21 -07:00
Kibana Machine
ec17499aa8
[8.8] [ML] Stabilize and reenable notifications tests (#158546) (#158575)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ML] Stabilize and reenable notifications tests
(#158546)](https://github.com/elastic/kibana/pull/158546)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Robert
Oskamp","email":"robert.oskamp@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T15:31:10Z","message":"[ML]
Stabilize and reenable notifications tests (#158546)\n\n##
Summary\r\n\r\nThis PR stabilizes ML notifications tests by introducing
leniency when\r\nchecking for the notifications table in loading state.
It also reenables\r\nthe test suite.\r\n\r\n### Other
changes\r\n\r\nAfter the test cleanup was done, we still had a left-over
saved object.\r\nThis was caused by the test creating a job for `space1`
without actually\r\ncreating that space. In order to fix this, we now
let the test properly\r\ncreate and cleanup that
space.","sha":"dbf0a07a564630277780b432718705e7e20f5cb4","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","backport:prev-minor","v8.9.0","v8.8.1"],"number":158546,"url":"https://github.com/elastic/kibana/pull/158546","mergeCommit":{"message":"[ML]
Stabilize and reenable notifications tests (#158546)\n\n##
Summary\r\n\r\nThis PR stabilizes ML notifications tests by introducing
leniency when\r\nchecking for the notifications table in loading state.
It also reenables\r\nthe test suite.\r\n\r\n### Other
changes\r\n\r\nAfter the test cleanup was done, we still had a left-over
saved object.\r\nThis was caused by the test creating a job for `space1`
without actually\r\ncreating that space. In order to fix this, we now
let the test properly\r\ncreate and cleanup that
space.","sha":"dbf0a07a564630277780b432718705e7e20f5cb4"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158546","number":158546,"mergeCommit":{"message":"[ML]
Stabilize and reenable notifications tests (#158546)\n\n##
Summary\r\n\r\nThis PR stabilizes ML notifications tests by introducing
leniency when\r\nchecking for the notifications table in loading state.
It also reenables\r\nthe test suite.\r\n\r\n### Other
changes\r\n\r\nAfter the test cleanup was done, we still had a left-over
saved object.\r\nThis was caused by the test creating a job for `space1`
without actually\r\ncreating that space. In order to fix this, we now
let the test properly\r\ncreate and cleanup that
space.","sha":"dbf0a07a564630277780b432718705e7e20f5cb4"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
2023-05-26 09:28:54 -07:00
Kibana Machine
b7375b08d8
[8.8] [Security Solution][Endpoint][Response Actions] Fix table navigation when trays are expanded (#157777) (#158306)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution][Endpoint][Response Actions] Fix table navigation
when trays are expanded
(#157777)](https://github.com/elastic/kibana/pull/157777)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT
[{"author":{"name":"Ashokaditya","email":"1849116+ashokaditya@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-23T18:49:02Z","message":"[Security
Solution][Endpoint][Response Actions] Fix table navigation when trays
are expanded (#157777)\n\n## Summary\r\n\r\nFixes an issue where when an
action detail is shown via an expanded tray\r\nitem and the total number
of items goes beyond the first page on the\r\nresponse actions history
page/flyout, switching between pages while the\r\ntray is open breaks
the page.\r\n\r\n- [x] fix paging with trays expanded on a flyout \r\n-
[x] fix paging with trays expanded on a page\r\n- [x] ensure when the
page is loaded with `?withOutputs=` with action\r\nids from different
sets of pages, table paging doesn't break when paged,\r\nand trays show
open for the action ids in `?withOutputs=` URL param\r\n- tests:\r\n -
[x] page navigation flyout/page view\r\n - [x] page reload with URL
params (cypress)\r\n
\r\n**flyout**\r\n\r\n![response-logs-flyout](b68f6e5d-9d0e-456f-8b07-dea07526571b)\r\n\r\n*page
with URL load*\r\n- three actions are open on two different pages\r\n-
we re-load page 2 with two open trays and then navigate to page 1
to\r\nsee the third one open\r\n- also re-load page 1; we see the tray
open, then navigate to page 2 to\r\nsee the other two trays
open.\r\n\r\n![response-logs-page-reload](58896b2e-4078-42c0-ac6c-c34d5b1cd42b)\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":"9e01dc815f87ccb70f961852f6d7c014e3e43c0b","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","OLM
Sprint","v8.9.0","v8.8.1"],"number":157777,"url":"https://github.com/elastic/kibana/pull/157777","mergeCommit":{"message":"[Security
Solution][Endpoint][Response Actions] Fix table navigation when trays
are expanded (#157777)\n\n## Summary\r\n\r\nFixes an issue where when an
action detail is shown via an expanded tray\r\nitem and the total number
of items goes beyond the first page on the\r\nresponse actions history
page/flyout, switching between pages while the\r\ntray is open breaks
the page.\r\n\r\n- [x] fix paging with trays expanded on a flyout \r\n-
[x] fix paging with trays expanded on a page\r\n- [x] ensure when the
page is loaded with `?withOutputs=` with action\r\nids from different
sets of pages, table paging doesn't break when paged,\r\nand trays show
open for the action ids in `?withOutputs=` URL param\r\n- tests:\r\n -
[x] page navigation flyout/page view\r\n - [x] page reload with URL
params (cypress)\r\n
\r\n**flyout**\r\n\r\n![response-logs-flyout](b68f6e5d-9d0e-456f-8b07-dea07526571b)\r\n\r\n*page
with URL load*\r\n- three actions are open on two different pages\r\n-
we re-load page 2 with two open trays and then navigate to page 1
to\r\nsee the third one open\r\n- also re-load page 1; we see the tray
open, then navigate to page 2 to\r\nsee the other two trays
open.\r\n\r\n![response-logs-page-reload](58896b2e-4078-42c0-ac6c-c34d5b1cd42b)\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":"9e01dc815f87ccb70f961852f6d7c014e3e43c0b"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157777","number":157777,"mergeCommit":{"message":"[Security
Solution][Endpoint][Response Actions] Fix table navigation when trays
are expanded (#157777)\n\n## Summary\r\n\r\nFixes an issue where when an
action detail is shown via an expanded tray\r\nitem and the total number
of items goes beyond the first page on the\r\nresponse actions history
page/flyout, switching between pages while the\r\ntray is open breaks
the page.\r\n\r\n- [x] fix paging with trays expanded on a flyout \r\n-
[x] fix paging with trays expanded on a page\r\n- [x] ensure when the
page is loaded with `?withOutputs=` with action\r\nids from different
sets of pages, table paging doesn't break when paged,\r\nand trays show
open for the action ids in `?withOutputs=` URL param\r\n- tests:\r\n -
[x] page navigation flyout/page view\r\n - [x] page reload with URL
params (cypress)\r\n
\r\n**flyout**\r\n\r\n![response-logs-flyout](b68f6e5d-9d0e-456f-8b07-dea07526571b)\r\n\r\n*page
with URL load*\r\n- three actions are open on two different pages\r\n-
we re-load page 2 with two open trays and then navigate to page 1
to\r\nsee the third one open\r\n- also re-load page 1; we see the tray
open, then navigate to page 2 to\r\nsee the other two trays
open.\r\n\r\n![response-logs-page-reload](58896b2e-4078-42c0-ac6c-c34d5b1cd42b)\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":"9e01dc815f87ccb70f961852f6d7c014e3e43c0b"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Ashokaditya <1849116+ashokaditya@users.noreply.github.com>
2023-05-26 07:33:20 -07:00
Kibana Machine
8c83d40f58
[8.8] [maps] fix toolbar action button not filled when selected (#158284) (#158556)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[maps] fix toolbar action button not filled when selected
(#158284)](https://github.com/elastic/kibana/pull/158284)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T12:20:48Z","message":"[maps]
fix toolbar action button not filled when selected (#158284)\n\nFixes
https://github.com/elastic/kibana/issues/158221\r\n\r\nUpdated CSS
selector to look for any class containing\r\n\"euiButtonIcon-fill\"
instead of old \"euiButtonIcon--fill\". Had to use\r\nwild card select
because class name as dynamic id in it, for
example\r\n\"css-1q7ycil-euiButtonIcon-empty-primary-hoverStyles\"\r\n\r\nNow,
button is filled and icon is white when selected.\r\n<img width=\"400\"
alt=\"Screen Shot 2023-05-23 at 10 34 42
AM\"\r\nsrc=\"821d95da-df7a-4779-a7fa-2ce2aa61fa7d\">\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"33f5bb6ba57f533b9ac894f4f6020d6c855ab1ad","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","Feature:Maps","v8.9.0","v8.8.1"],"number":158284,"url":"https://github.com/elastic/kibana/pull/158284","mergeCommit":{"message":"[maps]
fix toolbar action button not filled when selected (#158284)\n\nFixes
https://github.com/elastic/kibana/issues/158221\r\n\r\nUpdated CSS
selector to look for any class containing\r\n\"euiButtonIcon-fill\"
instead of old \"euiButtonIcon--fill\". Had to use\r\nwild card select
because class name as dynamic id in it, for
example\r\n\"css-1q7ycil-euiButtonIcon-empty-primary-hoverStyles\"\r\n\r\nNow,
button is filled and icon is white when selected.\r\n<img width=\"400\"
alt=\"Screen Shot 2023-05-23 at 10 34 42
AM\"\r\nsrc=\"821d95da-df7a-4779-a7fa-2ce2aa61fa7d\">\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"33f5bb6ba57f533b9ac894f4f6020d6c855ab1ad"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158284","number":158284,"mergeCommit":{"message":"[maps]
fix toolbar action button not filled when selected (#158284)\n\nFixes
https://github.com/elastic/kibana/issues/158221\r\n\r\nUpdated CSS
selector to look for any class containing\r\n\"euiButtonIcon-fill\"
instead of old \"euiButtonIcon--fill\". Had to use\r\nwild card select
because class name as dynamic id in it, for
example\r\n\"css-1q7ycil-euiButtonIcon-empty-primary-hoverStyles\"\r\n\r\nNow,
button is filled and icon is white when selected.\r\n<img width=\"400\"
alt=\"Screen Shot 2023-05-23 at 10 34 42
AM\"\r\nsrc=\"821d95da-df7a-4779-a7fa-2ce2aa61fa7d\">\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"33f5bb6ba57f533b9ac894f4f6020d6c855ab1ad"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nathan Reese <reese.nathan@elastic.co>
2023-05-26 07:06:03 -07:00
Konrad Szwarc
5ca00fc51f
[8.8] [Defend Workflows][E2E]Endpoint e2e response console (#155605) (#158553)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Defend Workflows][E2E]Endpoint e2e response console
(#155605)](https://github.com/elastic/kibana/pull/155605)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Konrad
Szwarc","email":"konrad.szwarc@elastic.co"},"sourceCommit":{"committedDate":"2023-05-02T09:02:06Z","message":"[Defend
Workflows][E2E]Endpoint e2e response console (#155605)\n\nDepends on
https://github.com/elastic/kibana/pull/155519\r\n\r\nE2E coverage of
`isolate`, `processes`, `kill-process` and\r\n`suspend-process` commands
on mocked endpoint.\r\n\r\nE2E coverage of the above but on real
endpoint
is\r\n[here](https://github.com/elastic/kibana/pull/155519).\r\n\r\nBecause
these tests are run against mocked data I've decided not to
mock\r\n`kill-process` and `suspend-process` outcome (whether process
is\r\nactually killed/suspended) because it would mean testing
mocks\r\nthemselves. What is tested is the outcome the user sees
('Action\r\ncompleted').\r\n\r\n---------\r\n\r\nCo-authored-by: Patryk
Kopycinski
<contact@patrykkopycinski.com>","sha":"fd5309f6a02bce641c4baf79500acfe797e294f7","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Defend
Workflows","v8.8.0","v8.9.0"],"number":155605,"url":"https://github.com/elastic/kibana/pull/155605","mergeCommit":{"message":"[Defend
Workflows][E2E]Endpoint e2e response console (#155605)\n\nDepends on
https://github.com/elastic/kibana/pull/155519\r\n\r\nE2E coverage of
`isolate`, `processes`, `kill-process` and\r\n`suspend-process` commands
on mocked endpoint.\r\n\r\nE2E coverage of the above but on real
endpoint
is\r\n[here](https://github.com/elastic/kibana/pull/155519).\r\n\r\nBecause
these tests are run against mocked data I've decided not to
mock\r\n`kill-process` and `suspend-process` outcome (whether process
is\r\nactually killed/suspended) because it would mean testing
mocks\r\nthemselves. What is tested is the outcome the user sees
('Action\r\ncompleted').\r\n\r\n---------\r\n\r\nCo-authored-by: Patryk
Kopycinski
<contact@patrykkopycinski.com>","sha":"fd5309f6a02bce641c4baf79500acfe797e294f7"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/155605","number":155605,"mergeCommit":{"message":"[Defend
Workflows][E2E]Endpoint e2e response console (#155605)\n\nDepends on
https://github.com/elastic/kibana/pull/155519\r\n\r\nE2E coverage of
`isolate`, `processes`, `kill-process` and\r\n`suspend-process` commands
on mocked endpoint.\r\n\r\nE2E coverage of the above but on real
endpoint
is\r\n[here](https://github.com/elastic/kibana/pull/155519).\r\n\r\nBecause
these tests are run against mocked data I've decided not to
mock\r\n`kill-process` and `suspend-process` outcome (whether process
is\r\nactually killed/suspended) because it would mean testing
mocks\r\nthemselves. What is tested is the outcome the user sees
('Action\r\ncompleted').\r\n\r\n---------\r\n\r\nCo-authored-by: Patryk
Kopycinski
<contact@patrykkopycinski.com>","sha":"fd5309f6a02bce641c4baf79500acfe797e294f7"}}]}]
BACKPORT-->
2023-05-26 07:01:22 -07:00
Christos Nasikas
41428d0808
[8.8] [Cases] Fix bug with registered attachmets memoization (#158441) (#158559)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Cases] Fix bug with registered attachmets memoization
(#158441)](https://github.com/elastic/kibana/pull/158441)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Christos
Nasikas","email":"christos.nasikas@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T12:43:43Z","message":"[Cases]
Fix bug with registered attachmets memoization (#158441)\n\n##
Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/156179 I fixed
a bug with the\r\nmemorization of the react components of registered
attachments in Cases.\r\nThis fix introduced another bug which I am
fixing in this PR.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/158447\r\n\r\n###
Bug\r\n\r\n\r\n782a552c-29bd-4bae-b66b-8620cbdeb5ff\r\n\r\n###
Fix\r\n\r\n\r\na4834ce2-73c8-48cb-9ec4-f480133eca38\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release notes\r\n\r\nFix a bug where ML embeddables, OsQuery, and IoCs
attachments in a case\r\nrender the wrong
view.","sha":"a2a0860f65013167a8e097d821eefa7fe81b8832","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:ResponseOps","Feature:Cases","v8.9.0","v8.8.1"],"number":158441,"url":"https://github.com/elastic/kibana/pull/158441","mergeCommit":{"message":"[Cases]
Fix bug with registered attachmets memoization (#158441)\n\n##
Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/156179 I fixed
a bug with the\r\nmemorization of the react components of registered
attachments in Cases.\r\nThis fix introduced another bug which I am
fixing in this PR.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/158447\r\n\r\n###
Bug\r\n\r\n\r\n782a552c-29bd-4bae-b66b-8620cbdeb5ff\r\n\r\n###
Fix\r\n\r\n\r\na4834ce2-73c8-48cb-9ec4-f480133eca38\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release notes\r\n\r\nFix a bug where ML embeddables, OsQuery, and IoCs
attachments in a case\r\nrender the wrong
view.","sha":"a2a0860f65013167a8e097d821eefa7fe81b8832"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158441","number":158441,"mergeCommit":{"message":"[Cases]
Fix bug with registered attachmets memoization (#158441)\n\n##
Summary\r\n\r\nIn https://github.com/elastic/kibana/pull/156179 I fixed
a bug with the\r\nmemorization of the react components of registered
attachments in Cases.\r\nThis fix introduced another bug which I am
fixing in this PR.\r\n\r\nFixes:
https://github.com/elastic/kibana/issues/158447\r\n\r\n###
Bug\r\n\r\n\r\n782a552c-29bd-4bae-b66b-8620cbdeb5ff\r\n\r\n###
Fix\r\n\r\n\r\na4834ce2-73c8-48cb-9ec4-f480133eca38\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n##
Release notes\r\n\r\nFix a bug where ML embeddables, OsQuery, and IoCs
attachments in a case\r\nrender the wrong
view.","sha":"a2a0860f65013167a8e097d821eefa7fe81b8832"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2023-05-26 07:00:35 -07:00
Kibana Machine
82c4eac47b
[8.8] [Synthetics] - Fix broken sort behavior on overview page. (#158411) (#158550)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Synthetics] - Fix broken sort behavior on overview page.
(#158411)](https://github.com/elastic/kibana/pull/158411)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Abdul Wahab
Zahid","email":"awahab07@yahoo.com"},"sourceCommit":{"committedDate":"2023-05-26T10:38:35Z","message":"[Synthetics]
- Fix broken sort behavior on overview page. (#158411)\n\nWhen sorting
on Synthetics -> Overview page, cards keep loading until\r\nthe next
periodic update. This PR fixes this
behavior.","sha":"bb495c2d5088456208ca26980d7c4c122f2743d9","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.8.0","v8.9.0"],"number":158411,"url":"https://github.com/elastic/kibana/pull/158411","mergeCommit":{"message":"[Synthetics]
- Fix broken sort behavior on overview page. (#158411)\n\nWhen sorting
on Synthetics -> Overview page, cards keep loading until\r\nthe next
periodic update. This PR fixes this
behavior.","sha":"bb495c2d5088456208ca26980d7c4c122f2743d9"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158411","number":158411,"mergeCommit":{"message":"[Synthetics]
- Fix broken sort behavior on overview page. (#158411)\n\nWhen sorting
on Synthetics -> Overview page, cards keep loading until\r\nthe next
periodic update. This PR fixes this
behavior.","sha":"bb495c2d5088456208ca26980d7c4c122f2743d9"}}]}]
BACKPORT-->

Co-authored-by: Abdul Wahab Zahid <awahab07@yahoo.com>
2023-05-26 04:43:52 -07:00
Dzmitry Lemechko
dc74b994f6
[8.8] unskip tests for chrome, fix tags (#158405) (#158545)
# Backport

This will backport the following commits from `main` to `8.8`:
- [unskip tests for chrome, fix tags
(#158405)](https://github.com/elastic/kibana/pull/158405)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T08:19:53Z","message":"unskip
tests for chrome, fix tags (#158405)\n\n## Summary\r\n\r\nWith Firefox
update to v113 on our CI workers, we noticed that tests are\r\nrun
slower and more often fail with timeouts.\r\nUnfortunately our auto-skip
functionality skip the test suite\r\ncompletely, meaning it won't run on
Chrome as well.\r\n\r\nThis PR unskips the firefox failed test to run on
Chrome, I also fix the\r\nlabels for some suites to run only sub set of
tests for
now.","sha":"5d4eec5131a797708bd2b8fae5a4706ecc3e7679","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.8.1"],"number":158405,"url":"https://github.com/elastic/kibana/pull/158405","mergeCommit":{"message":"unskip
tests for chrome, fix tags (#158405)\n\n## Summary\r\n\r\nWith Firefox
update to v113 on our CI workers, we noticed that tests are\r\nrun
slower and more often fail with timeouts.\r\nUnfortunately our auto-skip
functionality skip the test suite\r\ncompletely, meaning it won't run on
Chrome as well.\r\n\r\nThis PR unskips the firefox failed test to run on
Chrome, I also fix the\r\nlabels for some suites to run only sub set of
tests for
now.","sha":"5d4eec5131a797708bd2b8fae5a4706ecc3e7679"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158405","number":158405,"mergeCommit":{"message":"unskip
tests for chrome, fix tags (#158405)\n\n## Summary\r\n\r\nWith Firefox
update to v113 on our CI workers, we noticed that tests are\r\nrun
slower and more often fail with timeouts.\r\nUnfortunately our auto-skip
functionality skip the test suite\r\ncompletely, meaning it won't run on
Chrome as well.\r\n\r\nThis PR unskips the firefox failed test to run on
Chrome, I also fix the\r\nlabels for some suites to run only sub set of
tests for
now.","sha":"5d4eec5131a797708bd2b8fae5a4706ecc3e7679"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->
2023-05-26 04:25:28 -07:00
Kibana Machine
5fe0c97371
[8.8] [Security Solution][Detection Engine] fixes wildcard in field names issue for query language in detection rules (#157981) (#158539)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution][Detection Engine] fixes wildcard in field names
issue for query language in detection rules
(#157981)](https://github.com/elastic/kibana/pull/157981)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Vitalii
Dmyterko","email":"92328789+vitaliidm@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-26T09:12:21Z","message":"[Security
Solution][Detection Engine] fixes wildcard in field names issue for
query language in detection rules (#157981)\n\n## Summary\r\n\r\n- fixes
https://github.com/elastic/kibana/issues/149920 for the\r\nfollowing
rule types\r\n - query\r\n - new terms\r\n - threshold\r\n - threat
match\r\n\r\nTechnical details:\r\n- EQL doesn't support wildcard in
field names, so no need to search for\r\nwildcard fields for EQL type
rules\r\n- `lucene` language doesn't need to retrieve wildcard fields,
so we can\r\nskip fetching this fields when rule is configured with
it\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable
to this PR.\r\n\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### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ddc81633d29f4e115785f79432e774e98580c058","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:
SecuritySolution","backport:prev-minor","v8.9.0","v8.8.1","Team:Detection
Engine"],"number":157981,"url":"https://github.com/elastic/kibana/pull/157981","mergeCommit":{"message":"[Security
Solution][Detection Engine] fixes wildcard in field names issue for
query language in detection rules (#157981)\n\n## Summary\r\n\r\n- fixes
https://github.com/elastic/kibana/issues/149920 for the\r\nfollowing
rule types\r\n - query\r\n - new terms\r\n - threshold\r\n - threat
match\r\n\r\nTechnical details:\r\n- EQL doesn't support wildcard in
field names, so no need to search for\r\nwildcard fields for EQL type
rules\r\n- `lucene` language doesn't need to retrieve wildcard fields,
so we can\r\nskip fetching this fields when rule is configured with
it\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable
to this PR.\r\n\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### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ddc81633d29f4e115785f79432e774e98580c058"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157981","number":157981,"mergeCommit":{"message":"[Security
Solution][Detection Engine] fixes wildcard in field names issue for
query language in detection rules (#157981)\n\n## Summary\r\n\r\n- fixes
https://github.com/elastic/kibana/issues/149920 for the\r\nfollowing
rule types\r\n - query\r\n - new terms\r\n - threshold\r\n - threat
match\r\n\r\nTechnical details:\r\n- EQL doesn't support wildcard in
field names, so no need to search for\r\nwildcard fields for EQL type
rules\r\n- `lucene` language doesn't need to retrieve wildcard fields,
so we can\r\nskip fetching this fields when rule is configured with
it\r\n\r\n### Checklist\r\n\r\nDelete any items that are not applicable
to this PR.\r\n\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### For
maintainers\r\n\r\n- [ ] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ddc81633d29f4e115785f79432e774e98580c058"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>
2023-05-26 03:59:28 -07:00
Kibana Machine
c67d7a113f
[8.8] update geckodriver to 4.0.0 (#158384) (#158536)
# Backport

This will backport the following commits from `main` to `8.8`:
- [update geckodriver to 4.0.0
(#158384)](https://github.com/elastic/kibana/pull/158384)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Dzmitry
Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2023-05-26T08:24:19Z","message":"update
geckodriver to 4.0.0 (#158384)\n\n## Summary\r\n\r\nUpdating geckodriver
dependency to use the latest 0.33.0 driver. Module\r\nwas reworked, I
removed import from
webdriver.ts","sha":"0f8b3595f13c8b1e37374998c0df44c1737f8a95","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.7.2","v8.9.0","v8.8.1"],"number":158384,"url":"https://github.com/elastic/kibana/pull/158384","mergeCommit":{"message":"update
geckodriver to 4.0.0 (#158384)\n\n## Summary\r\n\r\nUpdating geckodriver
dependency to use the latest 0.33.0 driver. Module\r\nwas reworked, I
removed import from
webdriver.ts","sha":"0f8b3595f13c8b1e37374998c0df44c1737f8a95"}},"sourceBranch":"main","suggestedTargetBranches":["8.7","8.8"],"targetPullRequestStates":[{"branch":"8.7","label":"v8.7.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158384","number":158384,"mergeCommit":{"message":"update
geckodriver to 4.0.0 (#158384)\n\n## Summary\r\n\r\nUpdating geckodriver
dependency to use the latest 0.33.0 driver. Module\r\nwas reworked, I
removed import from
webdriver.ts","sha":"0f8b3595f13c8b1e37374998c0df44c1737f8a95"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
2023-05-26 02:30:04 -07:00
gchaps
638710c831
[DOCS] Updates release notes (#158524)
## Summary

This PR adds the system indices to the release notes.
2023-05-25 17:04:08 -07:00
Tiago Costa
a9155623ce
chore(NA): bump version to 8.8.1 (#158455)
Usually bump from 8.8.0 to 8.8.1

---------

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-05-25 19:52:10 +01:00
Kibana Machine
bc5230735e
[8.8] [DOCS] Allow users authenticated with API keys to manage alerting rules (#158428) (#158497)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Allow users authenticated with API keys to manage alerting
rules (#158428)](https://github.com/elastic/kibana/pull/158428)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-05-25T17:32:11Z","message":"[DOCS]
Allow users authenticated with API keys to manage alerting rules
(#158428)","sha":"4cf817a1abb3ddd657c7c11d75c5bd7f9e8aed27","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.9.0","v8.8.1"],"number":158428,"url":"https://github.com/elastic/kibana/pull/158428","mergeCommit":{"message":"[DOCS]
Allow users authenticated with API keys to manage alerting rules
(#158428)","sha":"4cf817a1abb3ddd657c7c11d75c5bd7f9e8aed27"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158428","number":158428,"mergeCommit":{"message":"[DOCS]
Allow users authenticated with API keys to manage alerting rules
(#158428)","sha":"4cf817a1abb3ddd657c7c11d75c5bd7f9e8aed27"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-05-25 13:54:13 -04:00
Kibana Machine
1b72e4ae6d
[8.8] [DOCS] Clarify support for data views in stack rules (#158431) (#158463)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Clarify support for data views in stack rules
(#158431)](https://github.com/elastic/kibana/pull/158431)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-05-25T14:53:57Z","message":"[DOCS]
Clarify support for data views in stack rules
(#158431)","sha":"4981f37014829f26514067d2570d7f992c6a76ef","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.9.0"],"number":158431,"url":"https://github.com/elastic/kibana/pull/158431","mergeCommit":{"message":"[DOCS]
Clarify support for data views in stack rules
(#158431)","sha":"4981f37014829f26514067d2570d7f992c6a76ef"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158431","number":158431,"mergeCommit":{"message":"[DOCS]
Clarify support for data views in stack rules
(#158431)","sha":"4981f37014829f26514067d2570d7f992c6a76ef"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-05-25 11:15:24 -04:00
Kibana Machine
fe1289cc9c
[8.8] [DOCS] Telemetry settings: improve phrasing (#158396) (#158462)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Telemetry settings: improve phrasing
(#158396)](https://github.com/elastic/kibana/pull/158396)

<!--- Backport version: 8.9.7 -->

### 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":"2023-05-25T14:46:08Z","message":"[DOCS]
Telemetry settings: improve phrasing
(#158396)","sha":"995b0a46e9da573d14bf0e5af27b4b028bd5293d","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","Team:Core","v8.0.0","release_note:skip","docs","v8.1.0","v7.17.0","v8.2.0","v8.3.0","v8.4.0","v8.5.0","v8.6.0","v8.7.0","v8.8.0","v8.9.0"],"number":158396,"url":"https://github.com/elastic/kibana/pull/158396","mergeCommit":{"message":"[DOCS]
Telemetry settings: improve phrasing
(#158396)","sha":"995b0a46e9da573d14bf0e5af27b4b028bd5293d"}},"sourceBranch":"main","suggestedTargetBranches":["8.0","8.1","7.17","8.2","8.3","8.4","8.5","8.6","8.7","8.8"],"targetPullRequestStates":[{"branch":"8.0","label":"v8.0.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.1","label":"v8.1.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"7.17","label":"v7.17.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.2","label":"v8.2.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.3","label":"v8.3.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.4","label":"v8.4.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.5","label":"v8.5.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.6","label":"v8.6.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.7","label":"v8.7.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158396","number":158396,"mergeCommit":{"message":"[DOCS]
Telemetry settings: improve phrasing
(#158396)","sha":"995b0a46e9da573d14bf0e5af27b4b028bd5293d"}}]}]
BACKPORT-->

Co-authored-by: Alejandro Fernández Haro <alejandro.haro@elastic.co>
2023-05-25 11:10:34 -04:00
Kibana Machine
de87c1417a
[8.8] [Enterprise Search] [Search Application] Fix error message when creating duplicate search application (#158333) (#158458)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Enterprise Search] [Search Application] Fix error message when
creating duplicate search application
(#158333)](https://github.com/elastic/kibana/pull/158333)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Saarika
Bhasi","email":"55930906+saarikabhasi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-25T12:57:45Z","message":"[Enterprise
Search] [Search Application] Fix error message when creating duplicate
search application (#158333)\n\n## Summar\r\n\r\n* Instead of showing
Status Code **502: Internal Server Error**, Shows\r\n**409 :
Conflict**\r\n* Shows `\"Search application name already taken. Choose
another name\"`\r\nwhen duplicate search application is
created.\r\n\r\n## Screen
Recording\r\n\r\n\r\n96615f59-6fa2-4e4c-9758-f128ec56e455\r\n\r\n<img
width=\"1728\"
alt=\"Response\"\r\nsrc=\"56368b62-1799-4749-a019-67154dfb1cca\">","sha":"0b93a956db6b1ac9e2db5a57e77c690372f76bb7","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.9.0","v8.8.1"],"number":158333,"url":"https://github.com/elastic/kibana/pull/158333","mergeCommit":{"message":"[Enterprise
Search] [Search Application] Fix error message when creating duplicate
search application (#158333)\n\n## Summar\r\n\r\n* Instead of showing
Status Code **502: Internal Server Error**, Shows\r\n**409 :
Conflict**\r\n* Shows `\"Search application name already taken. Choose
another name\"`\r\nwhen duplicate search application is
created.\r\n\r\n## Screen
Recording\r\n\r\n\r\n96615f59-6fa2-4e4c-9758-f128ec56e455\r\n\r\n<img
width=\"1728\"
alt=\"Response\"\r\nsrc=\"56368b62-1799-4749-a019-67154dfb1cca\">","sha":"0b93a956db6b1ac9e2db5a57e77c690372f76bb7"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158333","number":158333,"mergeCommit":{"message":"[Enterprise
Search] [Search Application] Fix error message when creating duplicate
search application (#158333)\n\n## Summar\r\n\r\n* Instead of showing
Status Code **502: Internal Server Error**, Shows\r\n**409 :
Conflict**\r\n* Shows `\"Search application name already taken. Choose
another name\"`\r\nwhen duplicate search application is
created.\r\n\r\n## Screen
Recording\r\n\r\n\r\n96615f59-6fa2-4e4c-9758-f128ec56e455\r\n\r\n<img
width=\"1728\"
alt=\"Response\"\r\nsrc=\"56368b62-1799-4749-a019-67154dfb1cca\">","sha":"0b93a956db6b1ac9e2db5a57e77c690372f76bb7"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com>
2023-05-25 07:11:50 -07:00
Yan Savitski
3b54b080e3
[8.8] [Search Application] Fix doc link in navigation toolbar (#158203) (#158453)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Search Application] Fix doc link in navigation toolbar
(#158203)](https://github.com/elastic/kibana/pull/158203)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Yan
Savitski","email":"yan.savitski@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T01:53:07Z","message":"[Search
Application] Fix doc link in navigation toolbar (#158203)\n\n- Fix the
way of using setActionMenu. According their doc and source\r\ncode we
need to call it twice, for moun and unmount.\r\n- Fix redirection issue
and using reactDom in rendering of action items\r\n\r\n<img
width=\"926\"
alt=\"image\"\r\nsrc=\"1e531299-e055-4af1-8ec7-92511e1a6e81\">","sha":"1b0a1ec30cde7355fe30445df8c0e96149c68e74","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.8.0","v8.9.0"],"number":158203,"url":"https://github.com/elastic/kibana/pull/158203","mergeCommit":{"message":"[Search
Application] Fix doc link in navigation toolbar (#158203)\n\n- Fix the
way of using setActionMenu. According their doc and source\r\ncode we
need to call it twice, for moun and unmount.\r\n- Fix redirection issue
and using reactDom in rendering of action items\r\n\r\n<img
width=\"926\"
alt=\"image\"\r\nsrc=\"1e531299-e055-4af1-8ec7-92511e1a6e81\">","sha":"1b0a1ec30cde7355fe30445df8c0e96149c68e74"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158203","number":158203,"mergeCommit":{"message":"[Search
Application] Fix doc link in navigation toolbar (#158203)\n\n- Fix the
way of using setActionMenu. According their doc and source\r\ncode we
need to call it twice, for moun and unmount.\r\n- Fix redirection issue
and using reactDom in rendering of action items\r\n\r\n<img
width=\"926\"
alt=\"image\"\r\nsrc=\"1e531299-e055-4af1-8ec7-92511e1a6e81\">","sha":"1b0a1ec30cde7355fe30445df8c0e96149c68e74"}}]}]
BACKPORT-->
2023-05-25 06:50:09 -07:00
Dima Arnautov
48945fa33a
[8.8] [ML] Apply theme based on the User Profile settings (#158258) (#158442)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ML] Apply theme based on the User Profile settings
(#158258)](https://github.com/elastic/kibana/pull/158258)

<!--- Backport version: 8.9.7 -->

### 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":"2023-05-25T09:57:48Z","message":"[ML]
Apply theme based on the User Profile settings (#158258)\n\n##
Summary\r\n\r\nWith the release of Per User Dark Mode, code should no
longer rely on\r\ncalling `uiSettings` to determine which theme Kibana
is displayed with.\r\n\r\nWith theme settings now configurable from User
Profiles and Adv.\r\nSettings, the code that was calling uiSettings to
determine the Kibana\r\ntheme will not take into account which theme is
currently being\r\ndisplayed.\r\n\r\n\r\nApplies an appropriate EUI
theme based on the profile settings. In\r\nparticular for the following
components:\r\n- Anomaly swim lane (Fixes #158155 )\r\n- Job tree map
view (Fixes\r\nhttps://github.com/elastic/kibana/issues/158304)\r\n-
Charts-related theme settings, e.g. the Single Metric
Viewer","sha":"c5eee26671ea5e215e5182b29562f6ffe5476965","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix",":ml","Team:ML","v8.9.0","v8.8.1"],"number":158258,"url":"https://github.com/elastic/kibana/pull/158258","mergeCommit":{"message":"[ML]
Apply theme based on the User Profile settings (#158258)\n\n##
Summary\r\n\r\nWith the release of Per User Dark Mode, code should no
longer rely on\r\ncalling `uiSettings` to determine which theme Kibana
is displayed with.\r\n\r\nWith theme settings now configurable from User
Profiles and Adv.\r\nSettings, the code that was calling uiSettings to
determine the Kibana\r\ntheme will not take into account which theme is
currently being\r\ndisplayed.\r\n\r\n\r\nApplies an appropriate EUI
theme based on the profile settings. In\r\nparticular for the following
components:\r\n- Anomaly swim lane (Fixes #158155 )\r\n- Job tree map
view (Fixes\r\nhttps://github.com/elastic/kibana/issues/158304)\r\n-
Charts-related theme settings, e.g. the Single Metric
Viewer","sha":"c5eee26671ea5e215e5182b29562f6ffe5476965"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158258","number":158258,"mergeCommit":{"message":"[ML]
Apply theme based on the User Profile settings (#158258)\n\n##
Summary\r\n\r\nWith the release of Per User Dark Mode, code should no
longer rely on\r\ncalling `uiSettings` to determine which theme Kibana
is displayed with.\r\n\r\nWith theme settings now configurable from User
Profiles and Adv.\r\nSettings, the code that was calling uiSettings to
determine the Kibana\r\ntheme will not take into account which theme is
currently being\r\ndisplayed.\r\n\r\n\r\nApplies an appropriate EUI
theme based on the profile settings. In\r\nparticular for the following
components:\r\n- Anomaly swim lane (Fixes #158155 )\r\n- Job tree map
view (Fixes\r\nhttps://github.com/elastic/kibana/issues/158304)\r\n-
Charts-related theme settings, e.g. the Single Metric
Viewer","sha":"c5eee26671ea5e215e5182b29562f6ffe5476965"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-05-25 05:02:10 -07:00
Kibana Machine
ab563b95e4
[8.8] [DOCS] Removes coming tag from 8.8 release notes (#157419) (#158435)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Removes coming tag from 8.8 release notes
(#157419)](https://github.com/elastic/kibana/pull/157419)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kaarina
Tungseth","email":"kaarina.tungseth@elastic.co"},"sourceCommit":{"committedDate":"2023-05-25T06:59:59Z","message":"[DOCS]
Removes coming tag from 8.8 release notes (#157419)\n\n##
Summary\r\n\r\nRemoves `coming` tag from the 8.8 release
notes.","sha":"d14ed5fbbe98bb05f678e5ecf872f35891a109eb","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v8.8.0","v8.9.0"],"number":157419,"url":"https://github.com/elastic/kibana/pull/157419","mergeCommit":{"message":"[DOCS]
Removes coming tag from 8.8 release notes (#157419)\n\n##
Summary\r\n\r\nRemoves `coming` tag from the 8.8 release
notes.","sha":"d14ed5fbbe98bb05f678e5ecf872f35891a109eb"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157419","number":157419,"mergeCommit":{"message":"[DOCS]
Removes coming tag from 8.8 release notes (#157419)\n\n##
Summary\r\n\r\nRemoves `coming` tag from the 8.8 release
notes.","sha":"d14ed5fbbe98bb05f678e5ecf872f35891a109eb"}}]}]
BACKPORT-->

Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
2023-05-25 03:22:33 -04:00
gchaps
b3e241bd62
[DOCS] Removes tag from what's new doc (#158412)
This PR removes the tag from the What's New doc.
2023-05-25 09:00:25 +02:00
Kibana Machine
1d2f1bc5ba
[8.8] [DOCS] Automate maintenance window screenshot (#157816) (#158283)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Automate maintenance window screenshot
(#157816)](https://github.com/elastic/kibana/pull/157816)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T16:26:16Z","message":"[DOCS]
Automate maintenance window screenshot
(#157816)","sha":"877e2ac51c105994663ad88fd66c5df1e8376546","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.8.0","v8.9.0"],"number":157816,"url":"https://github.com/elastic/kibana/pull/157816","mergeCommit":{"message":"[DOCS]
Automate maintenance window screenshot
(#157816)","sha":"877e2ac51c105994663ad88fd66c5df1e8376546"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157816","number":157816,"mergeCommit":{"message":"[DOCS]
Automate maintenance window screenshot
(#157816)","sha":"877e2ac51c105994663ad88fd66c5df1e8376546"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-05-24 14:32:59 -07:00
Kibana Machine
8de126b1f2
[8.8] [DOCS] Clarify domain for ServiceNow connectors (#158336) (#158420)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Clarify domain for ServiceNow connectors
(#158336)](https://github.com/elastic/kibana/pull/158336)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-05-24T20:40:27Z","message":"[DOCS]
Clarify domain for ServiceNow connectors
(#158336)","sha":"c247899225cb781f8a8965cdec3ecf07556a859a","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorTypes","backport:prev-minor","v8.9.0"],"number":158336,"url":"https://github.com/elastic/kibana/pull/158336","mergeCommit":{"message":"[DOCS]
Clarify domain for ServiceNow connectors
(#158336)","sha":"c247899225cb781f8a8965cdec3ecf07556a859a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158336","number":158336,"mergeCommit":{"message":"[DOCS]
Clarify domain for ServiceNow connectors
(#158336)","sha":"c247899225cb781f8a8965cdec3ecf07556a859a"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-05-24 17:02:11 -04:00
Kibana Machine
153b86110d
[8.8] Fixes documentation of response codes for copy saved objects (#158416) (#158419)
# Backport

This will backport the following commits from `main` to `8.8`:
- [Fixes documentation of response codes for copy saved objects
(#158416)](https://github.com/elastic/kibana/pull/158416)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Jeramy
Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2023-05-24T20:33:29Z","message":"Fixes
documentation of response codes for copy saved objects (#158416)\n\n##
Summary\r\n\r\nMoves the response codes documented for the copy saved
object API to the\r\ncorrect document file.\r\n\r\nDocumentation was
incorrectly located
in\r\nhttps://github.com/elastic/kibana/pull/158036","sha":"ab7b2f7f79978a8c1a24859dffbb16c013d82e3a","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","Feature:Saved
Objects","Feature:Security/Spaces","release_note:skip","backport:prev-minor","v8.9.0"],"number":158416,"url":"https://github.com/elastic/kibana/pull/158416","mergeCommit":{"message":"Fixes
documentation of response codes for copy saved objects (#158416)\n\n##
Summary\r\n\r\nMoves the response codes documented for the copy saved
object API to the\r\ncorrect document file.\r\n\r\nDocumentation was
incorrectly located
in\r\nhttps://github.com/elastic/kibana/pull/158036","sha":"ab7b2f7f79978a8c1a24859dffbb16c013d82e3a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158416","number":158416,"mergeCommit":{"message":"Fixes
documentation of response codes for copy saved objects (#158416)\n\n##
Summary\r\n\r\nMoves the response codes documented for the copy saved
object API to the\r\ncorrect document file.\r\n\r\nDocumentation was
incorrectly located
in\r\nhttps://github.com/elastic/kibana/pull/158036","sha":"ab7b2f7f79978a8c1a24859dffbb16c013d82e3a"}}]}]
BACKPORT-->

Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>
2023-05-24 16:56:17 -04:00
Kibana Machine
2135cf0ff9
[8.8] Handles non-existing objects in _copy_saved_objects API call (#158036) (#158399)
# Backport

This will backport the following commits from `main` to `8.8`:
- [Handles non-existing objects in _copy_saved_objects API call
(#158036)](https://github.com/elastic/kibana/pull/158036)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Jeramy
Soucy","email":"jeramy.soucy@elastic.co"},"sourceCommit":{"committedDate":"2023-05-24T16:20:46Z","message":"Handles
non-existing objects in _copy_saved_objects API call (#158036)\n\nCloses
#156791\r\n\r\n## Summary\r\n\r\nThis PR implements catching the error
thrown by the\r\nsaved_objects_exporter when an object is not found, and
responding with\r\na detailed 404 (\"Not Found\") rather than a generic
500 (\"Internal Server\r\nError\") response message.\r\n\r\n### Example
Response:\r\n```\r\n{\r\n \"statusCode\": 404,\r\n \"error\": \"Not
Found\",\r\n \"message\": \"Saved objects not found\",\r\n
\"attributes\": {\r\n \"objects\": [\r\n {\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73d\",\r\n \"type\":
\"dashboard\"\r\n },\r\n {\r\n \"id\":
\"571aaf70-4c88-11e8-b3d7-01146121b73d\",\r\n \"type\": \"search\"\r\n
},\r\n {\r\n \"id\": \"d3d7af60-4c81-11e8-b3d7-01146121b73d\",\r\n
\"type\": \"index-pattern\"\r\n }\r\n ]\r\n }\r\n}\r\n```\r\n\r\n###
Testing\r\n\r\n1. Install sample flight data, find the id of the flights
dashboard SO\r\n2. Create an additional space 'b'\r\n3. Issue a request
to copy saved objects to space b\r\n```\r\nPOST
kbn:/api/spaces/_copy_saved_objects\r\n{\r\n \"spaces\": [\r\n \"b\"\r\n
],\r\n \"objects\": [\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73e\"\r\n },\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73f\"\r\n
},\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73g\"\r\n }\r\n ]\r\n}\r\n```\r\n4.
Verify response\r\n```\r\n{\r\n \"statusCode\": 404,\r\n \"error\":
\"Not Found\",\r\n \"message\": \"Saved objects not found\",\r\n
\"attributes\": {\r\n \"objects\": [\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73e\"\r\n
},\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73f\"\r\n },\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73g\"\r\n
}\r\n ]\r\n }\r\n}\r\n```\r\n5. Issue a request to copy the flights
dashboard SO\r\n6. Verify the usual response (200, missing
references)\r\n7. Issue a malformed request to copy an SO\r\n8. Verify
status 400 response with
details","sha":"1589547b6f143c45c782ed857902026af2e7e38a","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Security","Feature:Saved
Objects","Feature:Security/Spaces","backport:all-open","v8.9.0"],"number":158036,"url":"https://github.com/elastic/kibana/pull/158036","mergeCommit":{"message":"Handles
non-existing objects in _copy_saved_objects API call (#158036)\n\nCloses
#156791\r\n\r\n## Summary\r\n\r\nThis PR implements catching the error
thrown by the\r\nsaved_objects_exporter when an object is not found, and
responding with\r\na detailed 404 (\"Not Found\") rather than a generic
500 (\"Internal Server\r\nError\") response message.\r\n\r\n### Example
Response:\r\n```\r\n{\r\n \"statusCode\": 404,\r\n \"error\": \"Not
Found\",\r\n \"message\": \"Saved objects not found\",\r\n
\"attributes\": {\r\n \"objects\": [\r\n {\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73d\",\r\n \"type\":
\"dashboard\"\r\n },\r\n {\r\n \"id\":
\"571aaf70-4c88-11e8-b3d7-01146121b73d\",\r\n \"type\": \"search\"\r\n
},\r\n {\r\n \"id\": \"d3d7af60-4c81-11e8-b3d7-01146121b73d\",\r\n
\"type\": \"index-pattern\"\r\n }\r\n ]\r\n }\r\n}\r\n```\r\n\r\n###
Testing\r\n\r\n1. Install sample flight data, find the id of the flights
dashboard SO\r\n2. Create an additional space 'b'\r\n3. Issue a request
to copy saved objects to space b\r\n```\r\nPOST
kbn:/api/spaces/_copy_saved_objects\r\n{\r\n \"spaces\": [\r\n \"b\"\r\n
],\r\n \"objects\": [\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73e\"\r\n },\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73f\"\r\n
},\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73g\"\r\n }\r\n ]\r\n}\r\n```\r\n4.
Verify response\r\n```\r\n{\r\n \"statusCode\": 404,\r\n \"error\":
\"Not Found\",\r\n \"message\": \"Saved objects not found\",\r\n
\"attributes\": {\r\n \"objects\": [\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73e\"\r\n
},\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73f\"\r\n },\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73g\"\r\n
}\r\n ]\r\n }\r\n}\r\n```\r\n5. Issue a request to copy the flights
dashboard SO\r\n6. Verify the usual response (200, missing
references)\r\n7. Issue a malformed request to copy an SO\r\n8. Verify
status 400 response with
details","sha":"1589547b6f143c45c782ed857902026af2e7e38a"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158036","number":158036,"mergeCommit":{"message":"Handles
non-existing objects in _copy_saved_objects API call (#158036)\n\nCloses
#156791\r\n\r\n## Summary\r\n\r\nThis PR implements catching the error
thrown by the\r\nsaved_objects_exporter when an object is not found, and
responding with\r\na detailed 404 (\"Not Found\") rather than a generic
500 (\"Internal Server\r\nError\") response message.\r\n\r\n### Example
Response:\r\n```\r\n{\r\n \"statusCode\": 404,\r\n \"error\": \"Not
Found\",\r\n \"message\": \"Saved objects not found\",\r\n
\"attributes\": {\r\n \"objects\": [\r\n {\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73d\",\r\n \"type\":
\"dashboard\"\r\n },\r\n {\r\n \"id\":
\"571aaf70-4c88-11e8-b3d7-01146121b73d\",\r\n \"type\": \"search\"\r\n
},\r\n {\r\n \"id\": \"d3d7af60-4c81-11e8-b3d7-01146121b73d\",\r\n
\"type\": \"index-pattern\"\r\n }\r\n ]\r\n }\r\n}\r\n```\r\n\r\n###
Testing\r\n\r\n1. Install sample flight data, find the id of the flights
dashboard SO\r\n2. Create an additional space 'b'\r\n3. Issue a request
to copy saved objects to space b\r\n```\r\nPOST
kbn:/api/spaces/_copy_saved_objects\r\n{\r\n \"spaces\": [\r\n \"b\"\r\n
],\r\n \"objects\": [\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73e\"\r\n },\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73f\"\r\n
},\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73g\"\r\n }\r\n ]\r\n}\r\n```\r\n4.
Verify response\r\n```\r\n{\r\n \"statusCode\": 404,\r\n \"error\":
\"Not Found\",\r\n \"message\": \"Saved objects not found\",\r\n
\"attributes\": {\r\n \"objects\": [\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73e\"\r\n
},\r\n {\r\n \"type\": \"dashboard\",\r\n \"id\":
\"7adfa750-4c81-11e8-b3d7-01146121b73f\"\r\n },\r\n {\r\n \"type\":
\"dashboard\",\r\n \"id\": \"7adfa750-4c81-11e8-b3d7-01146121b73g\"\r\n
}\r\n ]\r\n }\r\n}\r\n```\r\n5. Issue a request to copy the flights
dashboard SO\r\n6. Verify the usual response (200, missing
references)\r\n7. Issue a malformed request to copy an SO\r\n8. Verify
status 400 response with
details","sha":"1589547b6f143c45c782ed857902026af2e7e38a"}}]}]
BACKPORT-->

Co-authored-by: Jeramy Soucy <jeramy.soucy@elastic.co>
2023-05-24 10:32:34 -07:00
Kibana Machine
8bc6826e1e
[8.8] [DOCS] Replace description attributes with frontmatter for migration (#158126) (#158389)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Replace description attributes with frontmatter for migration
(#158126)](https://github.com/elastic/kibana/pull/158126)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-05-24T15:16:43Z","message":"[DOCS]
Replace description attributes with frontmatter for migration
(#158126)","sha":"668968b758cb1e8717ae640e0c318509ec133322","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","v8.8.0","v8.9.0"],"number":158126,"url":"https://github.com/elastic/kibana/pull/158126","mergeCommit":{"message":"[DOCS]
Replace description attributes with frontmatter for migration
(#158126)","sha":"668968b758cb1e8717ae640e0c318509ec133322"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158126","number":158126,"mergeCommit":{"message":"[DOCS]
Replace description attributes with frontmatter for migration
(#158126)","sha":"668968b758cb1e8717ae640e0c318509ec133322"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-05-24 11:39:32 -04:00
Kibana Machine
f48357c957
[8.8] Update security telemetry filterlist with network fields. (#158166) (#158351)
# Backport

This will backport the following commits from `main` to `8.8`:
- [Update security telemetry filterlist with network fields.
(#158166)](https://github.com/elastic/kibana/pull/158166)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Pete
Hampton","email":"pjhampton@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-23T16:25:23Z","message":"Update
security telemetry filterlist with network fields. (#158166)\n\n##
Summary\r\n\r\nThis PR filters in network-related fields to improve
threat research\r\ncontext, improve telemetry on existing network-based
rules, and allow us\r\nto provide additional malicious indicators with
research publications.\r\n\r\n - Issue backref'd\r\n - OOB artifact
backref'd\r\n - Stakeholders and legal engaged\r\n\r\ncc
@terrancedejesus for context. \r\n\r\n### Checklist\r\n\r\nDelete any
items that are not applicable to this PR.\r\n\r\n- [ ] Any text added
follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8761e5057c7b87d54fcabcc3c7574ed1ce952a08","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Telemetry","release_note:skip","Team:
SecuritySolution","auto-backport","v8.9.0","v8.8.1"],"number":158166,"url":"https://github.com/elastic/kibana/pull/158166","mergeCommit":{"message":"Update
security telemetry filterlist with network fields. (#158166)\n\n##
Summary\r\n\r\nThis PR filters in network-related fields to improve
threat research\r\ncontext, improve telemetry on existing network-based
rules, and allow us\r\nto provide additional malicious indicators with
research publications.\r\n\r\n - Issue backref'd\r\n - OOB artifact
backref'd\r\n - Stakeholders and legal engaged\r\n\r\ncc
@terrancedejesus for context. \r\n\r\n### Checklist\r\n\r\nDelete any
items that are not applicable to this PR.\r\n\r\n- [ ] Any text added
follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8761e5057c7b87d54fcabcc3c7574ed1ce952a08"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158166","number":158166,"mergeCommit":{"message":"Update
security telemetry filterlist with network fields. (#158166)\n\n##
Summary\r\n\r\nThis PR filters in network-related fields to improve
threat research\r\ncontext, improve telemetry on existing network-based
rules, and allow us\r\nto provide additional malicious indicators with
research publications.\r\n\r\n - Issue backref'd\r\n - OOB artifact
backref'd\r\n - Stakeholders and legal engaged\r\n\r\ncc
@terrancedejesus for context. \r\n\r\n### Checklist\r\n\r\nDelete any
items that are not applicable to this PR.\r\n\r\n- [ ] Any text added
follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"8761e5057c7b87d54fcabcc3c7574ed1ce952a08"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Pete Hampton <pjhampton@users.noreply.github.com>
2023-05-24 03:32:34 -07:00
Kibana Machine
303c8f2e8f
[8.8] [Enterprise Search][Search Application] Remove application name validation from Create Search App Flyout (#158120) (#158332)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Enterprise Search][Search Application] Remove application name
validation from Create Search App Flyout
(#158120)](https://github.com/elastic/kibana/pull/158120)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Saarika
Bhasi","email":"55930906+saarikabhasi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-23T21:48:14Z","message":"[Enterprise
Search][Search Application] Remove application name validation from
Create Search App Flyout (#158120)\n\n## Summary\r\n\r\n* Remove search
application name validation from UI side in Create search application
Flyout, Instead verify error from
logs.\r\n\r\n\r\n\r\n\r\n\r\n2a945d8d-45ae-41ce-a143-a126b993132d","sha":"2a97425f5804379474faf5b3630de53401c3280f","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:EnterpriseSearch","v8.9.0","v8.8.1"],"number":158120,"url":"https://github.com/elastic/kibana/pull/158120","mergeCommit":{"message":"[Enterprise
Search][Search Application] Remove application name validation from
Create Search App Flyout (#158120)\n\n## Summary\r\n\r\n* Remove search
application name validation from UI side in Create search application
Flyout, Instead verify error from
logs.\r\n\r\n\r\n\r\n\r\n\r\n2a945d8d-45ae-41ce-a143-a126b993132d","sha":"2a97425f5804379474faf5b3630de53401c3280f"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158120","number":158120,"mergeCommit":{"message":"[Enterprise
Search][Search Application] Remove application name validation from
Create Search App Flyout (#158120)\n\n## Summary\r\n\r\n* Remove search
application name validation from UI side in Create search application
Flyout, Instead verify error from
logs.\r\n\r\n\r\n\r\n\r\n\r\n2a945d8d-45ae-41ce-a143-a126b993132d","sha":"2a97425f5804379474faf5b3630de53401c3280f"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Saarika Bhasi <55930906+saarikabhasi@users.noreply.github.com>
2023-05-23 15:59:50 -07:00
Kibana Machine
79f2cc6467
[8.8] [DOCS] Add steps for Docker image verification (#158303) (#158331)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Add steps for Docker image verification
(#158303)](https://github.com/elastic/kibana/pull/158303)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"David
Kilfoyle","email":"41695641+kilfoyle@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-23T21:19:29Z","message":"[DOCS]
Add steps for Docker image verification (#158303)\n\nThis adds steps to
the [Install Kibana
with\r\nDocker](https://www.elastic.co/guide/en/kibana/current/docker.html)
page\r\nfor verifying the downloaded Docker images. I split apart the
original\r\nversion which had all the commands in one block. Having them
separate\r\nallows us to add in the optional \"verify images\" step with
a link to the\r\nElasticsearch docs for additional info.\r\n\r\nRel:
https://github.com/elastic/dev/issues/2002\r\n\r\n**Preview**\r\n\r\n---\r\n![Screenshot
2023-05-23 at 1 56
32\r\nPM](7d35b9ad-d0f1-4c01-b26b-6ca469fdc644)\r\n\r\n---\r\n\r\n![Screenshot
2023-05-23 at 1 47
24\r\nPM](0ec110be-1560-4dcc-8949-792e09846ee9)\r\n\r\n---------\r\n\r\nCo-authored-by:
Tiago Costa
<tiago.costa@elastic.co>","sha":"fb9e3c9ec80e5ba22b6315b7963ad20caa84f439","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v8.8.0","v8.9.0"],"number":158303,"url":"https://github.com/elastic/kibana/pull/158303","mergeCommit":{"message":"[DOCS]
Add steps for Docker image verification (#158303)\n\nThis adds steps to
the [Install Kibana
with\r\nDocker](https://www.elastic.co/guide/en/kibana/current/docker.html)
page\r\nfor verifying the downloaded Docker images. I split apart the
original\r\nversion which had all the commands in one block. Having them
separate\r\nallows us to add in the optional \"verify images\" step with
a link to the\r\nElasticsearch docs for additional info.\r\n\r\nRel:
https://github.com/elastic/dev/issues/2002\r\n\r\n**Preview**\r\n\r\n---\r\n![Screenshot
2023-05-23 at 1 56
32\r\nPM](7d35b9ad-d0f1-4c01-b26b-6ca469fdc644)\r\n\r\n---\r\n\r\n![Screenshot
2023-05-23 at 1 47
24\r\nPM](0ec110be-1560-4dcc-8949-792e09846ee9)\r\n\r\n---------\r\n\r\nCo-authored-by:
Tiago Costa
<tiago.costa@elastic.co>","sha":"fb9e3c9ec80e5ba22b6315b7963ad20caa84f439"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158303","number":158303,"mergeCommit":{"message":"[DOCS]
Add steps for Docker image verification (#158303)\n\nThis adds steps to
the [Install Kibana
with\r\nDocker](https://www.elastic.co/guide/en/kibana/current/docker.html)
page\r\nfor verifying the downloaded Docker images. I split apart the
original\r\nversion which had all the commands in one block. Having them
separate\r\nallows us to add in the optional \"verify images\" step with
a link to the\r\nElasticsearch docs for additional info.\r\n\r\nRel:
https://github.com/elastic/dev/issues/2002\r\n\r\n**Preview**\r\n\r\n---\r\n![Screenshot
2023-05-23 at 1 56
32\r\nPM](7d35b9ad-d0f1-4c01-b26b-6ca469fdc644)\r\n\r\n---\r\n\r\n![Screenshot
2023-05-23 at 1 47
24\r\nPM](0ec110be-1560-4dcc-8949-792e09846ee9)\r\n\r\n---------\r\n\r\nCo-authored-by:
Tiago Costa
<tiago.costa@elastic.co>","sha":"fb9e3c9ec80e5ba22b6315b7963ad20caa84f439"}}]}]
BACKPORT-->

Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com>
2023-05-23 17:43:08 -04:00
Kibana Machine
96c6d15f00
[8.8] [DOCS] Maintenance window column in alerts tables (#158125) (#158301)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Maintenance window column in alerts tables
(#158125)](https://github.com/elastic/kibana/pull/158125)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T17:49:18Z","message":"[DOCS]
Maintenance window column in alerts tables
(#158125)","sha":"1b71d2ca3c7b0492e88f44c70ab08f60acb47435","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.8.0","v8.9.0"],"number":158125,"url":"https://github.com/elastic/kibana/pull/158125","mergeCommit":{"message":"[DOCS]
Maintenance window column in alerts tables
(#158125)","sha":"1b71d2ca3c7b0492e88f44c70ab08f60acb47435"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158125","number":158125,"mergeCommit":{"message":"[DOCS]
Maintenance window column in alerts tables
(#158125)","sha":"1b71d2ca3c7b0492e88f44c70ab08f60acb47435"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-05-23 14:12:21 -04:00
Kibana Machine
46f6a76e61
[8.8] [DOCS] Conditional actions in Kibana alerting summary (#158045) (#158300)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Conditional actions in Kibana alerting summary
(#158045)](https://github.com/elastic/kibana/pull/158045)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lisa
Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T17:50:17Z","message":"[DOCS]
Conditional actions in Kibana alerting summary
(#158045)","sha":"c5a1d6b5f45207767ab6f2e0acb5bc8134468ff2","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Alerting","release_note:skip","Team:ResponseOps","docs","backport:prev-minor","v8.8.0","v8.9.0"],"number":158045,"url":"https://github.com/elastic/kibana/pull/158045","mergeCommit":{"message":"[DOCS]
Conditional actions in Kibana alerting summary
(#158045)","sha":"c5a1d6b5f45207767ab6f2e0acb5bc8134468ff2"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158045","number":158045,"mergeCommit":{"message":"[DOCS]
Conditional actions in Kibana alerting summary
(#158045)","sha":"c5a1d6b5f45207767ab6f2e0acb5bc8134468ff2"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2023-05-23 14:11:43 -04:00
Kibana Machine
b95e1bcbb4
[8.8] [docs] [kql] Update KQL docs to include info about errors with multiple field types (#158035) (#158294)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[docs] [kql] Update KQL docs to include info about errors with
multiple field types
(#158035)](https://github.com/elastic/kibana/pull/158035)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Lukas
Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T16:29:47Z","message":"[docs]
[kql] Update KQL docs to include info about errors with multiple field
types (#158035)\n\n## Summary\r\n\r\nWe received feedback that the given
example would result in errors,\r\nsince it targets
both\r\n[string](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-body-content)\r\nand\r\n[numeric](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-bytes)\r\nfields,
so we've updated the example with something that won't result in\r\nan
error, and updated the docs with a note that explains when/why
these\r\nerrors may occur.\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
gchaps
<33642766+gchaps@users.noreply.github.com>","sha":"be35641e171a7b65b2d719f3e1276c183b0a8024","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v8.0.2","v8.1.4","v8.2.4","v8.3.4","v8.4.4","v8.5.4","v8.6.3","v8.7.2","v8.9.0","v7.17.11","v8.8.1"],"number":158035,"url":"https://github.com/elastic/kibana/pull/158035","mergeCommit":{"message":"[docs]
[kql] Update KQL docs to include info about errors with multiple field
types (#158035)\n\n## Summary\r\n\r\nWe received feedback that the given
example would result in errors,\r\nsince it targets
both\r\n[string](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-body-content)\r\nand\r\n[numeric](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-bytes)\r\nfields,
so we've updated the example with something that won't result in\r\nan
error, and updated the docs with a note that explains when/why
these\r\nerrors may occur.\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
gchaps
<33642766+gchaps@users.noreply.github.com>","sha":"be35641e171a7b65b2d719f3e1276c183b0a8024"}},"sourceBranch":"main","suggestedTargetBranches":["8.0","8.1","8.2","8.3","8.4","8.5","8.6","8.7","7.17","8.8"],"targetPullRequestStates":[{"branch":"8.0","label":"v8.0.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.1","label":"v8.1.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.2","label":"v8.2.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.3","label":"v8.3.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.4","label":"v8.4.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.5","label":"v8.5.4","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.6","label":"v8.6.3","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.7","label":"v8.7.2","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158035","number":158035,"mergeCommit":{"message":"[docs]
[kql] Update KQL docs to include info about errors with multiple field
types (#158035)\n\n## Summary\r\n\r\nWe received feedback that the given
example would result in errors,\r\nsince it targets
both\r\n[string](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-body-content)\r\nand\r\n[numeric](https://www.elastic.co/guide/en/ecs/current/ecs-http.html#field-http-response-bytes)\r\nfields,
so we've updated the example with something that won't result in\r\nan
error, and updated the docs with a note that explains when/why
these\r\nerrors may occur.\r\n\r\n### Checklist\r\n\r\nDelete any items
that are not applicable to this PR.\r\n\r\n- [ ] Any text added follows
[EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)\r\n-
[
]\r\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials\r\n- [ ] [Unit
or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [ ] Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard accessibility](https://webaim.org/techniques/keyboard/))\r\n-
[ ] Any UI touched in this PR does not create any new axe
failures\r\n(run axe in
browser:\r\n[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/),\r\n[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US))\r\n-
[ ] If a plugin configuration key changed, check if it needs to
be\r\nallowlisted in the cloud and added to the
[docker\r\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\r\n-
[ ] This renders correctly on smaller devices using a
responsive\r\nlayout. (You can test this [in
your\r\nbrowser](https://www.browserstack.com/guide/responsive-testing-on-local-server))\r\n-
[ ] This was checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\r\n\r\n\r\n###
Risk Matrix\r\n\r\nDelete this section if it is not applicable to this
PR.\r\n\r\nBefore closing this PR, invite QA, stakeholders, and other
developers to\r\nidentify risks that should be tested prior to the
change/feature\r\nrelease.\r\n\r\nWhen forming the risk matrix, consider
some of the following examples\r\nand how they may potentially impact
the change:\r\n\r\n| Risk | Probability | Severity | Mitigation/Notes
|\r\n\r\n|---------------------------|-------------|----------|-------------------------|\r\n|
Multiple Spaces&mdash;unexpected behavior in non-default Kibana
Space.\r\n| Low | High | Integration tests will verify that all features
are still\r\nsupported in non-default Kibana Space and when user
switches between\r\nspaces. |\r\n| Multiple nodes&mdash;Elasticsearch
polling might have race conditions\r\nwhen multiple Kibana nodes are
polling for the same tasks. | High | Low\r\n| Tasks are idempotent, so
executing them multiple times will not result\r\nin logical error, but
will degrade performance. To test for this case we\r\nadd plenty of unit
tests around this logic and document manual testing\r\nprocedure. |\r\n|
Code should gracefully handle cases when feature X or plugin Y
are\r\ndisabled. | Medium | High | Unit tests will verify that any
feature flag\r\nor plugin combination still results in our service
operational. |\r\n| [See more potential
risk\r\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)
|\r\n\r\n\r\n### For maintainers\r\n\r\n- [ ] This was checked for
breaking API changes and was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by:
gchaps
<33642766+gchaps@users.noreply.github.com>","sha":"be35641e171a7b65b2d719f3e1276c183b0a8024"}},{"branch":"7.17","label":"v7.17.11","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Lukas Olson <lukas@elastic.co>
2023-05-23 13:00:03 -04:00
Lisa Cawley
1f9316a633
[DOCS] Add highlight for Slack connector improvements (#158111) 2023-05-23 09:21:50 -07:00
Kibana Machine
ca54090121
[8.8] [DOCS] Adds 8.8 Viz docs (#157215) (#158281)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Adds 8.8 Viz docs
(#157215)](https://github.com/elastic/kibana/pull/157215)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Kaarina
Tungseth","email":"kaarina.tungseth@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T15:41:42Z","message":"[DOCS]
Adds 8.8 Viz docs (#157215)\n\n## Summary\r\n\r\nAdds the 8.8
documentation for the following:\r\n\r\n- Enable report sharing:
https://github.com/elastic/kibana/pull/153429\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/reporting-getting-started.html\r\n\r\n-
Random sampling feature:
https://github.com/elastic/kibana/pull/143221\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#improve-visualization-loading-time\r\n\r\n-
Improve Ignore global filters
UI:\r\nhttps://github.com/elastic/kibana/pull/154441
and\r\nhttps://github.com/elastic/kibana/pull/155280\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#add-annotations\r\n\r\n---------\r\n\r\nCo-authored-by:
Tim Sullivan
<tsullivan@users.noreply.github.com>","sha":"06a800fbad1f2a8fd9146bfe0c439e2107f771fc","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","Team:SharedUX","v8.8.0","v8.9.0"],"number":157215,"url":"https://github.com/elastic/kibana/pull/157215","mergeCommit":{"message":"[DOCS]
Adds 8.8 Viz docs (#157215)\n\n## Summary\r\n\r\nAdds the 8.8
documentation for the following:\r\n\r\n- Enable report sharing:
https://github.com/elastic/kibana/pull/153429\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/reporting-getting-started.html\r\n\r\n-
Random sampling feature:
https://github.com/elastic/kibana/pull/143221\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#improve-visualization-loading-time\r\n\r\n-
Improve Ignore global filters
UI:\r\nhttps://github.com/elastic/kibana/pull/154441
and\r\nhttps://github.com/elastic/kibana/pull/155280\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#add-annotations\r\n\r\n---------\r\n\r\nCo-authored-by:
Tim Sullivan
<tsullivan@users.noreply.github.com>","sha":"06a800fbad1f2a8fd9146bfe0c439e2107f771fc"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157215","number":157215,"mergeCommit":{"message":"[DOCS]
Adds 8.8 Viz docs (#157215)\n\n## Summary\r\n\r\nAdds the 8.8
documentation for the following:\r\n\r\n- Enable report sharing:
https://github.com/elastic/kibana/pull/153429\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/reporting-getting-started.html\r\n\r\n-
Random sampling feature:
https://github.com/elastic/kibana/pull/143221\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#improve-visualization-loading-time\r\n\r\n-
Improve Ignore global filters
UI:\r\nhttps://github.com/elastic/kibana/pull/154441
and\r\nhttps://github.com/elastic/kibana/pull/155280\r\nDocs
preview:\r\nhttps://kibana_157215.docs-preview.app.elstc.co/guide/en/kibana/master/lens.html#add-annotations\r\n\r\n---------\r\n\r\nCo-authored-by:
Tim Sullivan
<tsullivan@users.noreply.github.com>","sha":"06a800fbad1f2a8fd9146bfe0c439e2107f771fc"}}]}]
BACKPORT-->

Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
2023-05-23 12:03:21 -04:00
Kibana Machine
ff4f42a086
[8.8] [maps] fix Maps don't display darktheme when user has dark theme enabled in profile (#158219) (#158272)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[maps] fix Maps don't display darktheme when user has dark theme
enabled in profile
(#158219)](https://github.com/elastic/kibana/pull/158219)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Nathan
Reese","email":"reese.nathan@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T14:33:41Z","message":"[maps]
fix Maps don't display darktheme when user has dark theme enabled in
profile (#158219)\n\nFixes
https://github.com/elastic/kibana/issues/158050\r\n\r\nPR updates
`getIsDarkMode` to read value from theme$ instead of\r\nUiSettings,
since UiSettings does not contain profile theming. Part
of\r\nhttps://github.com/elastic/kibana/issues/158201\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"bb1cf6609a4cf5c8208318b803f6a7cdc0f2e913","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Presentation","Feature:Maps","v8.9.0","v8.8.1"],"number":158219,"url":"https://github.com/elastic/kibana/pull/158219","mergeCommit":{"message":"[maps]
fix Maps don't display darktheme when user has dark theme enabled in
profile (#158219)\n\nFixes
https://github.com/elastic/kibana/issues/158050\r\n\r\nPR updates
`getIsDarkMode` to read value from theme$ instead of\r\nUiSettings,
since UiSettings does not contain profile theming. Part
of\r\nhttps://github.com/elastic/kibana/issues/158201\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"bb1cf6609a4cf5c8208318b803f6a7cdc0f2e913"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158219","number":158219,"mergeCommit":{"message":"[maps]
fix Maps don't display darktheme when user has dark theme enabled in
profile (#158219)\n\nFixes
https://github.com/elastic/kibana/issues/158050\r\n\r\nPR updates
`getIsDarkMode` to read value from theme$ instead of\r\nUiSettings,
since UiSettings does not contain profile theming. Part
of\r\nhttps://github.com/elastic/kibana/issues/158201\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"bb1cf6609a4cf5c8208318b803f6a7cdc0f2e913"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Nathan Reese <reese.nathan@elastic.co>
2023-05-23 08:52:55 -07:00
Lisa Cawley
363169b907
[DOCS] Highlight cases links in alerts table (#158097) 2023-05-23 07:40:21 -07:00
Kibana Machine
362b82c129
[8.8] Update saved objects migrations documentation for 8.8.0 (#158241) (#158270)
# Backport

This will backport the following commits from `main` to `8.8`:
- [Update saved objects migrations documentation for 8.8.0
(#158241)](https://github.com/elastic/kibana/pull/158241)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Gerard
Soldevila","email":"gerard.soldevila@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T13:53:52Z","message":"Update
saved objects migrations documentation for 8.8.0
(#158241)\n\nDocumentation must reflect changes brought by the [dot
kibana\r\nsplit](https://github.com/elastic/kibana/pull/154888).\r\n\r\nOur
public facing documentation just mentions two indices
e.g.\r\n\r\nhttps://www.elastic.co/guide/en/kibana/8.8/saved-object-migrations.html\r\n\r\nhttps://www.elastic.co/guide/en/kibana/8.8/resolve-migrations-failures.html#upgrade-migrations-old-indices\r\nthis
one in particular mentions that \"all other indices are safe
to\r\ndelete\".","sha":"70eb9d3ecbb11768d091fca385bad4f20960deef","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","documentation","Feature:Migrations","backport:prev-minor","v8.8.0","v8.9.0","v8.8.1"],"number":158241,"url":"https://github.com/elastic/kibana/pull/158241","mergeCommit":{"message":"Update
saved objects migrations documentation for 8.8.0
(#158241)\n\nDocumentation must reflect changes brought by the [dot
kibana\r\nsplit](https://github.com/elastic/kibana/pull/154888).\r\n\r\nOur
public facing documentation just mentions two indices
e.g.\r\n\r\nhttps://www.elastic.co/guide/en/kibana/8.8/saved-object-migrations.html\r\n\r\nhttps://www.elastic.co/guide/en/kibana/8.8/resolve-migrations-failures.html#upgrade-migrations-old-indices\r\nthis
one in particular mentions that \"all other indices are safe
to\r\ndelete\".","sha":"70eb9d3ecbb11768d091fca385bad4f20960deef"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158241","number":158241,"mergeCommit":{"message":"Update
saved objects migrations documentation for 8.8.0
(#158241)\n\nDocumentation must reflect changes brought by the [dot
kibana\r\nsplit](https://github.com/elastic/kibana/pull/154888).\r\n\r\nOur
public facing documentation just mentions two indices
e.g.\r\n\r\nhttps://www.elastic.co/guide/en/kibana/8.8/saved-object-migrations.html\r\n\r\nhttps://www.elastic.co/guide/en/kibana/8.8/resolve-migrations-failures.html#upgrade-migrations-old-indices\r\nthis
one in particular mentions that \"all other indices are safe
to\r\ndelete\".","sha":"70eb9d3ecbb11768d091fca385bad4f20960deef"}}]}]
BACKPORT-->

Co-authored-by: Gerard Soldevila <gerard.soldevila@elastic.co>
2023-05-23 10:15:19 -04:00
Kibana Machine
2973fcc10d
[8.8] Security tech debt cleanup (#157990) (#158234)
# Backport

This will backport the following commits from `main` to `8.8`:
- [Security tech debt cleanup
(#157990)](https://github.com/elastic/kibana/pull/157990)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Thom
Heymann","email":"190132+thomheymann@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-23T08:30:48Z","message":"Security
tech debt cleanup (#157990)\n\n## Summary\r\n\r\nThis PR cleans up some
outstanding tech debt.\r\n\r\n### 1. Remove deprecation warning for
`disabled` prop\r\n\r\nThis property was marked as deprecated the moment
it was introduced
(See\r\nhttps://github.com/elastic/kibana/pull/118001/files#r753124740).
However\r\nit has been adopted by Fleet and Guided Onboarding plugins so
I don't\r\nthink there's value in keeping this deprecation warning in
place.\r\n\r\nAs an alternative we could also bump the `@removeBy`
version if people\r\nthink we should still remove this
property.\r\n\r\n\r\n### ~~2. Remove deprecated property
`requiredRoles`~~\r\n\r\n~~This property has been deprecated and marked
for removal for 8.8. The\r\nproperty isn't being used anywhere in our
codebase and we have reached\r\nfeature freeze for 8.8 so looks safe to
be removed now.~~\r\n\r\nTurns out this property is still used and can't
be removed without\r\nbreaking existing functionality so reverting that
commit.","sha":"3800ce4c9cbbceaa861b62de2fd217f0c1961b98","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Security","release_note:skip","v8.9.0","v8.8.1"],"number":157990,"url":"https://github.com/elastic/kibana/pull/157990","mergeCommit":{"message":"Security
tech debt cleanup (#157990)\n\n## Summary\r\n\r\nThis PR cleans up some
outstanding tech debt.\r\n\r\n### 1. Remove deprecation warning for
`disabled` prop\r\n\r\nThis property was marked as deprecated the moment
it was introduced
(See\r\nhttps://github.com/elastic/kibana/pull/118001/files#r753124740).
However\r\nit has been adopted by Fleet and Guided Onboarding plugins so
I don't\r\nthink there's value in keeping this deprecation warning in
place.\r\n\r\nAs an alternative we could also bump the `@removeBy`
version if people\r\nthink we should still remove this
property.\r\n\r\n\r\n### ~~2. Remove deprecated property
`requiredRoles`~~\r\n\r\n~~This property has been deprecated and marked
for removal for 8.8. The\r\nproperty isn't being used anywhere in our
codebase and we have reached\r\nfeature freeze for 8.8 so looks safe to
be removed now.~~\r\n\r\nTurns out this property is still used and can't
be removed without\r\nbreaking existing functionality so reverting that
commit.","sha":"3800ce4c9cbbceaa861b62de2fd217f0c1961b98"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157990","number":157990,"mergeCommit":{"message":"Security
tech debt cleanup (#157990)\n\n## Summary\r\n\r\nThis PR cleans up some
outstanding tech debt.\r\n\r\n### 1. Remove deprecation warning for
`disabled` prop\r\n\r\nThis property was marked as deprecated the moment
it was introduced
(See\r\nhttps://github.com/elastic/kibana/pull/118001/files#r753124740).
However\r\nit has been adopted by Fleet and Guided Onboarding plugins so
I don't\r\nthink there's value in keeping this deprecation warning in
place.\r\n\r\nAs an alternative we could also bump the `@removeBy`
version if people\r\nthink we should still remove this
property.\r\n\r\n\r\n### ~~2. Remove deprecated property
`requiredRoles`~~\r\n\r\n~~This property has been deprecated and marked
for removal for 8.8. The\r\nproperty isn't being used anywhere in our
codebase and we have reached\r\nfeature freeze for 8.8 so looks safe to
be removed now.~~\r\n\r\nTurns out this property is still used and can't
be removed without\r\nbreaking existing functionality so reverting that
commit.","sha":"3800ce4c9cbbceaa861b62de2fd217f0c1961b98"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Co-authored-by: Thom Heymann <190132+thomheymann@users.noreply.github.com>
2023-05-23 02:57:05 -07:00
Rudolf Meijering
45c322aa65
[8.8] Make updateAndPickupMappings batch size configurable (#153185) (#158235)
# Backport

This will backport the following commits from `main` to `8.8`:
- [Make updateAndPickupMappings batch size configurable
(#153185)](https://github.com/elastic/kibana/pull/153185)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Rudolf
Meijering","email":"skaapgif@gmail.com"},"sourceCommit":{"committedDate":"2023-05-22T12:08:02Z","message":"Make
updateAndPickupMappings batch size configurable (#153185)\n\n##
Summary\r\n\r\nUse migrations.batchSize config for the scroll_size in
update_by_query /\r\nupdateAndPickupMappings. The default
scroll_size=1000 can sometimes\r\ncause Elasticsearch to fail with
`RecyclerBytesStreamOutput cannot hold\r\nmore than 2GB of
data`\r\n\r\nOn CI our Elasticsearch cluster does not have enough memory
to reproduce\r\n`RecyclerBytesStreamOutput` error it OOMs before it's
able to load 2GB.\r\n\r\nHowever it's possible to test manually:\r\n1.
Start Elasticsearch with 8GB heap `ES_JAVA_OPTS=' -Xms8g -Xmx8g'
yarn\r\nes snapshot`\r\n2. Ingest > 2GB of saved objects distributed
over batchSize documents (<\r\n1000)\r\n ```\r\ncurl -XPOST
\"elastic:changeme@localhost:9200/_security/user/superuser\"\r\n-H
\"kbn-xsrf: reporting\" -H \"Content-Type: application/json\" -d'\r\n
{\r\n \"password\" : \"changeme\", \r\n \"roles\" : [ \"superuser\",
\"grant_kibana_system_indices\" ]\r\n }'\r\n\r\ncurl
-XPUT\r\n\"superuser:changeme@localhost:9200/.kibana_8.4.0_001/_mappings\"
-H\r\n\"kbn-xsrf: reporting\" -H \"Content-Type: application/json\"
-d'\r\n {\r\n\"dynamic\": false,\r\n \"properties\": {\r\n\r\n }\r\n\r\n
}'\r\n\r\n set -B # enable brace expansion\r\n for i in {1..500};
do\r\ncurl -k --data-binary \"@/Users/rudolf/dev/kibana/body.json\" -X
PUT\r\n\"http://superuser:changeme@localhost:9200/.kibana_8.4.0_001/_doc/cases-comments:\"{$i}\"?&pretty=true\"\r\n-H
\"Content-Type: application/json\"\r\n done\r\n\r\ncurl -XPOST
\"superuser:changeme@localhost:9200/_aliases\" -H
\"kbn-xsrf:\r\nreporting\" -H \"Content-Type: application/json\" -d'\r\n
{\r\n \"actions\": [\r\n {\r\n \"add\": {\r\n \"index\":
\".kibana_8.4.0_001\",\r\n \"alias\": \".kibana_8.4.0\"\r\n }\r\n },\r\n
{\r\n \"add\": {\r\n \"index\": \".kibana_8.4.0_001\",\r\n \"alias\":
\".kibana\"\r\n }\r\n }\r\n ]\r\n }'\r\n ```\r\n body.json\r\n ```\r\n
{\r\n \"cases-comments\": {\r\n \"comment\": \"...put lots of data
here...\",\r\n \"type\": \"user\",\r\n \"owner\": \"cases\",\r\n
\"created_at\": \"2023-05-09T08:07:50.121Z\",\r\n \"created_by\": {\r\n
\"email\": null,\r\n \"full_name\": null,\r\n \"username\":
\"elastic\"\r\n },\r\n \"pushed_at\": null,\r\n \"pushed_by\": null,\r\n
\"updated_at\": null,\r\n \"updated_by\": null\r\n },\r\n \"type\":
\"cases-comments\",\r\n \"references\": [\r\n {\r\n \"type\":
\"cases\",\r\n \"name\": \"associated-cases\",\r\n \"id\":
\"9563b290-ee40-11ed-8fcc-e975e7d47f63\"\r\n }\r\n ],\r\n
\"namespaces\": [\r\n \"default\"\r\n ],\r\n \"migrationVersion\": {\r\n
\"cases-comments\": \"8.6.0\"\r\n },\r\n \"coreMigrationVersion\":
\"8.7.2\",\r\n \"updated_at\": \"2023-05-09T08:07:50.168Z\",\r\n
\"created_at\": \"2023-05-09T08:07:50.168Z\"\r\n }\r\n ```\r\n3. Run
Kibana with default and smaller migrations.batchSize\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c79c09c3d0edeb31e2b1a9b8b6181fcb7bf9c587","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:skip","Feature:Migrations","backport:prev-minor","Epic:KBNA-7838","v8.9.0"],"number":153185,"url":"https://github.com/elastic/kibana/pull/153185","mergeCommit":{"message":"Make
updateAndPickupMappings batch size configurable (#153185)\n\n##
Summary\r\n\r\nUse migrations.batchSize config for the scroll_size in
update_by_query /\r\nupdateAndPickupMappings. The default
scroll_size=1000 can sometimes\r\ncause Elasticsearch to fail with
`RecyclerBytesStreamOutput cannot hold\r\nmore than 2GB of
data`\r\n\r\nOn CI our Elasticsearch cluster does not have enough memory
to reproduce\r\n`RecyclerBytesStreamOutput` error it OOMs before it's
able to load 2GB.\r\n\r\nHowever it's possible to test manually:\r\n1.
Start Elasticsearch with 8GB heap `ES_JAVA_OPTS=' -Xms8g -Xmx8g'
yarn\r\nes snapshot`\r\n2. Ingest > 2GB of saved objects distributed
over batchSize documents (<\r\n1000)\r\n ```\r\ncurl -XPOST
\"elastic:changeme@localhost:9200/_security/user/superuser\"\r\n-H
\"kbn-xsrf: reporting\" -H \"Content-Type: application/json\" -d'\r\n
{\r\n \"password\" : \"changeme\", \r\n \"roles\" : [ \"superuser\",
\"grant_kibana_system_indices\" ]\r\n }'\r\n\r\ncurl
-XPUT\r\n\"superuser:changeme@localhost:9200/.kibana_8.4.0_001/_mappings\"
-H\r\n\"kbn-xsrf: reporting\" -H \"Content-Type: application/json\"
-d'\r\n {\r\n\"dynamic\": false,\r\n \"properties\": {\r\n\r\n }\r\n\r\n
}'\r\n\r\n set -B # enable brace expansion\r\n for i in {1..500};
do\r\ncurl -k --data-binary \"@/Users/rudolf/dev/kibana/body.json\" -X
PUT\r\n\"http://superuser:changeme@localhost:9200/.kibana_8.4.0_001/_doc/cases-comments:\"{$i}\"?&pretty=true\"\r\n-H
\"Content-Type: application/json\"\r\n done\r\n\r\ncurl -XPOST
\"superuser:changeme@localhost:9200/_aliases\" -H
\"kbn-xsrf:\r\nreporting\" -H \"Content-Type: application/json\" -d'\r\n
{\r\n \"actions\": [\r\n {\r\n \"add\": {\r\n \"index\":
\".kibana_8.4.0_001\",\r\n \"alias\": \".kibana_8.4.0\"\r\n }\r\n },\r\n
{\r\n \"add\": {\r\n \"index\": \".kibana_8.4.0_001\",\r\n \"alias\":
\".kibana\"\r\n }\r\n }\r\n ]\r\n }'\r\n ```\r\n body.json\r\n ```\r\n
{\r\n \"cases-comments\": {\r\n \"comment\": \"...put lots of data
here...\",\r\n \"type\": \"user\",\r\n \"owner\": \"cases\",\r\n
\"created_at\": \"2023-05-09T08:07:50.121Z\",\r\n \"created_by\": {\r\n
\"email\": null,\r\n \"full_name\": null,\r\n \"username\":
\"elastic\"\r\n },\r\n \"pushed_at\": null,\r\n \"pushed_by\": null,\r\n
\"updated_at\": null,\r\n \"updated_by\": null\r\n },\r\n \"type\":
\"cases-comments\",\r\n \"references\": [\r\n {\r\n \"type\":
\"cases\",\r\n \"name\": \"associated-cases\",\r\n \"id\":
\"9563b290-ee40-11ed-8fcc-e975e7d47f63\"\r\n }\r\n ],\r\n
\"namespaces\": [\r\n \"default\"\r\n ],\r\n \"migrationVersion\": {\r\n
\"cases-comments\": \"8.6.0\"\r\n },\r\n \"coreMigrationVersion\":
\"8.7.2\",\r\n \"updated_at\": \"2023-05-09T08:07:50.168Z\",\r\n
\"created_at\": \"2023-05-09T08:07:50.168Z\"\r\n }\r\n ```\r\n3. Run
Kibana with default and smaller migrations.batchSize\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c79c09c3d0edeb31e2b1a9b8b6181fcb7bf9c587"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/153185","number":153185,"mergeCommit":{"message":"Make
updateAndPickupMappings batch size configurable (#153185)\n\n##
Summary\r\n\r\nUse migrations.batchSize config for the scroll_size in
update_by_query /\r\nupdateAndPickupMappings. The default
scroll_size=1000 can sometimes\r\ncause Elasticsearch to fail with
`RecyclerBytesStreamOutput cannot hold\r\nmore than 2GB of
data`\r\n\r\nOn CI our Elasticsearch cluster does not have enough memory
to reproduce\r\n`RecyclerBytesStreamOutput` error it OOMs before it's
able to load 2GB.\r\n\r\nHowever it's possible to test manually:\r\n1.
Start Elasticsearch with 8GB heap `ES_JAVA_OPTS=' -Xms8g -Xmx8g'
yarn\r\nes snapshot`\r\n2. Ingest > 2GB of saved objects distributed
over batchSize documents (<\r\n1000)\r\n ```\r\ncurl -XPOST
\"elastic:changeme@localhost:9200/_security/user/superuser\"\r\n-H
\"kbn-xsrf: reporting\" -H \"Content-Type: application/json\" -d'\r\n
{\r\n \"password\" : \"changeme\", \r\n \"roles\" : [ \"superuser\",
\"grant_kibana_system_indices\" ]\r\n }'\r\n\r\ncurl
-XPUT\r\n\"superuser:changeme@localhost:9200/.kibana_8.4.0_001/_mappings\"
-H\r\n\"kbn-xsrf: reporting\" -H \"Content-Type: application/json\"
-d'\r\n {\r\n\"dynamic\": false,\r\n \"properties\": {\r\n\r\n }\r\n\r\n
}'\r\n\r\n set -B # enable brace expansion\r\n for i in {1..500};
do\r\ncurl -k --data-binary \"@/Users/rudolf/dev/kibana/body.json\" -X
PUT\r\n\"http://superuser:changeme@localhost:9200/.kibana_8.4.0_001/_doc/cases-comments:\"{$i}\"?&pretty=true\"\r\n-H
\"Content-Type: application/json\"\r\n done\r\n\r\ncurl -XPOST
\"superuser:changeme@localhost:9200/_aliases\" -H
\"kbn-xsrf:\r\nreporting\" -H \"Content-Type: application/json\" -d'\r\n
{\r\n \"actions\": [\r\n {\r\n \"add\": {\r\n \"index\":
\".kibana_8.4.0_001\",\r\n \"alias\": \".kibana_8.4.0\"\r\n }\r\n },\r\n
{\r\n \"add\": {\r\n \"index\": \".kibana_8.4.0_001\",\r\n \"alias\":
\".kibana\"\r\n }\r\n }\r\n ]\r\n }'\r\n ```\r\n body.json\r\n ```\r\n
{\r\n \"cases-comments\": {\r\n \"comment\": \"...put lots of data
here...\",\r\n \"type\": \"user\",\r\n \"owner\": \"cases\",\r\n
\"created_at\": \"2023-05-09T08:07:50.121Z\",\r\n \"created_by\": {\r\n
\"email\": null,\r\n \"full_name\": null,\r\n \"username\":
\"elastic\"\r\n },\r\n \"pushed_at\": null,\r\n \"pushed_by\": null,\r\n
\"updated_at\": null,\r\n \"updated_by\": null\r\n },\r\n \"type\":
\"cases-comments\",\r\n \"references\": [\r\n {\r\n \"type\":
\"cases\",\r\n \"name\": \"associated-cases\",\r\n \"id\":
\"9563b290-ee40-11ed-8fcc-e975e7d47f63\"\r\n }\r\n ],\r\n
\"namespaces\": [\r\n \"default\"\r\n ],\r\n \"migrationVersion\": {\r\n
\"cases-comments\": \"8.6.0\"\r\n },\r\n \"coreMigrationVersion\":
\"8.7.2\",\r\n \"updated_at\": \"2023-05-09T08:07:50.168Z\",\r\n
\"created_at\": \"2023-05-09T08:07:50.168Z\"\r\n }\r\n ```\r\n3. Run
Kibana with default and smaller migrations.batchSize\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [ ] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n\r\n### For
maintainers\r\n\r\n- [x] This was checked for breaking API changes and
was
[labeled\r\nappropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"c79c09c3d0edeb31e2b1a9b8b6181fcb7bf9c587"}}]}]
BACKPORT-->
2023-05-23 02:45:11 -07:00
Kibana Machine
adec917694
[8.8] [Visualizations] Fix user profile dark mode bugs (#158162) (#158226)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Visualizations] Fix user profile dark mode bugs
(#158162)](https://github.com/elastic/kibana/pull/158162)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Stratoula
Kalafateli","email":"efstratia.kalafateli@elastic.co"},"sourceCommit":{"committedDate":"2023-05-23T06:04:43Z","message":"[Visualizations]
Fix user profile dark mode bugs (#158162)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/158154\r\nCloses
https://github.com/elastic/kibana/issues/158048\r\nCloses
https://github.com/elastic/kibana/issues/158052\r\n\r\nThis PR fixes the
UI bugs that were created when we added the user\r\nprofile dark mode
settings.\r\n\r\nThere are many cases in our visualizations where we are
checking if the\r\nuiSetting is in dark mode and apply custom colors.
This is not the case\r\nanymore. Now we need to check this flag from the
theme$.\r\n\r\nThere is a bug on the user profile service. When the user
profile is set\r\nto Light and the advanced setting is set to dark mode,
the dark mode is\r\napplied. I have reported this to the security
team.\r\n\r\n### Checklist\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>","sha":"2c1a2ef93ade7ed28b95293dff735a62f0ff5c70","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Visualizations","Team:Visualizations","release_note:skip","backport:prev-minor","v8.9.0","v8.8.1"],"number":158162,"url":"https://github.com/elastic/kibana/pull/158162","mergeCommit":{"message":"[Visualizations]
Fix user profile dark mode bugs (#158162)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/158154\r\nCloses
https://github.com/elastic/kibana/issues/158048\r\nCloses
https://github.com/elastic/kibana/issues/158052\r\n\r\nThis PR fixes the
UI bugs that were created when we added the user\r\nprofile dark mode
settings.\r\n\r\nThere are many cases in our visualizations where we are
checking if the\r\nuiSetting is in dark mode and apply custom colors.
This is not the case\r\nanymore. Now we need to check this flag from the
theme$.\r\n\r\nThere is a bug on the user profile service. When the user
profile is set\r\nto Light and the advanced setting is set to dark mode,
the dark mode is\r\napplied. I have reported this to the security
team.\r\n\r\n### Checklist\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>","sha":"2c1a2ef93ade7ed28b95293dff735a62f0ff5c70"}},"sourceBranch":"main","suggestedTargetBranches":["8.8"],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/158162","number":158162,"mergeCommit":{"message":"[Visualizations]
Fix user profile dark mode bugs (#158162)\n\n## Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/158154\r\nCloses
https://github.com/elastic/kibana/issues/158048\r\nCloses
https://github.com/elastic/kibana/issues/158052\r\n\r\nThis PR fixes the
UI bugs that were created when we added the user\r\nprofile dark mode
settings.\r\n\r\nThere are many cases in our visualizations where we are
checking if the\r\nuiSetting is in dark mode and apply custom colors.
This is not the case\r\nanymore. Now we need to check this flag from the
theme$.\r\n\r\nThere is a bug on the user profile service. When the user
profile is set\r\nto Light and the advanced setting is set to dark mode,
the dark mode is\r\napplied. I have reported this to the security
team.\r\n\r\n### Checklist\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>","sha":"2c1a2ef93ade7ed28b95293dff735a62f0ff5c70"}},{"branch":"8.8","label":"v8.8.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

---------

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
2023-05-23 12:07:44 +03:00
Kibana Machine
e687aef540
[8.8] [Security Solution] Fix incorrectly applied emotion styles (#157935) (#158058)
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution] Fix incorrectly applied emotion styles
(#157935)](https://github.com/elastic/kibana/pull/157935)

<!--- Backport version: 8.9.7 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Maxim
Palenov","email":"maxim.palenov@elastic.co"},"sourceCommit":{"committedDate":"2023-05-18T07:54:40Z","message":"[Security
Solution] Fix incorrectly applied emotion styles
(#157935)\n\n**Resolves:**
https://github.com/elastic/kibana/issues/156820\r\n\r\n##
Summary\r\n\r\nThis PR fixes improperly applied styles via emotion on
the rule details page.\r\n\r\n*Before:*\r\n\r\n<img width=\"2267\"
alt=\"image\"
src=\"https://user-images.githubusercontent.com/92328789/236432092-1a102af4-e746-4c32-ba17-6d17f76df6d2.png\">\r\n\r\n<img
width=\"2236\" alt=\"image\"
src=\"https://user-images.githubusercontent.com/92328789/236432072-da6efa55-0953-4abc-a5b5-c27be2b103ee.png\">\r\n\r\n*After:*\r\n\r\n<img
width=\"2267\" alt=\"image\"
src=\"4431eda1-0a69-403a-ad93-51658d0dbeff\">\r\n\r\n<img
width=\"2236\" alt=\"image\"
src=\"06647825-9b1f-4cd8-a60a-2c8988acbd9b\">\r\n\r\n\r\n##
Details\r\n\r\nRecent investigation has revealed emotion css styles
aren't applied correctly on production while the problem isn't
noticeable locally. This is caused by simultaneously using
**styled-components** and **emotion** in Security Solution plugin.
Further research lead to a way to fix it\r\n\r\n1. import `css` utility
function from `@emotion/css` instead of `@emotion/react`\r\n2. apply
styles using `className` instead of `css`\r\n\r\nLike in the code
below\r\n\r\n```ts\r\nimport { css } from
'@emotion/css';\r\n\r\n...\r\n\r\n<div className={css`\r\n padding-left:
200px;\r\n`}>\r\n
TEST\r\n</div>\r\n\r\n...\r\n```","sha":"8cf6d034e3a22370b73cf66ae893f8d7ff6b158d","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:Detections
and Resp","Team: SecuritySolution","Feature:Rule
Details","backport:prev-minor","ci:cloud-deploy","v8.9.0","Team:Detection
Engine"],"number":157935,"url":"https://github.com/elastic/kibana/pull/157935","mergeCommit":{"message":"[Security
Solution] Fix incorrectly applied emotion styles
(#157935)\n\n**Resolves:**
https://github.com/elastic/kibana/issues/156820\r\n\r\n##
Summary\r\n\r\nThis PR fixes improperly applied styles via emotion on
the rule details page.\r\n\r\n*Before:*\r\n\r\n<img width=\"2267\"
alt=\"image\"
src=\"https://user-images.githubusercontent.com/92328789/236432092-1a102af4-e746-4c32-ba17-6d17f76df6d2.png\">\r\n\r\n<img
width=\"2236\" alt=\"image\"
src=\"https://user-images.githubusercontent.com/92328789/236432072-da6efa55-0953-4abc-a5b5-c27be2b103ee.png\">\r\n\r\n*After:*\r\n\r\n<img
width=\"2267\" alt=\"image\"
src=\"4431eda1-0a69-403a-ad93-51658d0dbeff\">\r\n\r\n<img
width=\"2236\" alt=\"image\"
src=\"06647825-9b1f-4cd8-a60a-2c8988acbd9b\">\r\n\r\n\r\n##
Details\r\n\r\nRecent investigation has revealed emotion css styles
aren't applied correctly on production while the problem isn't
noticeable locally. This is caused by simultaneously using
**styled-components** and **emotion** in Security Solution plugin.
Further research lead to a way to fix it\r\n\r\n1. import `css` utility
function from `@emotion/css` instead of `@emotion/react`\r\n2. apply
styles using `className` instead of `css`\r\n\r\nLike in the code
below\r\n\r\n```ts\r\nimport { css } from
'@emotion/css';\r\n\r\n...\r\n\r\n<div className={css`\r\n padding-left:
200px;\r\n`}>\r\n
TEST\r\n</div>\r\n\r\n...\r\n```","sha":"8cf6d034e3a22370b73cf66ae893f8d7ff6b158d"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.9.0","labelRegex":"^v8.9.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/157935","number":157935,"mergeCommit":{"message":"[Security
Solution] Fix incorrectly applied emotion styles
(#157935)\n\n**Resolves:**
https://github.com/elastic/kibana/issues/156820\r\n\r\n##
Summary\r\n\r\nThis PR fixes improperly applied styles via emotion on
the rule details page.\r\n\r\n*Before:*\r\n\r\n<img width=\"2267\"
alt=\"image\"
src=\"https://user-images.githubusercontent.com/92328789/236432092-1a102af4-e746-4c32-ba17-6d17f76df6d2.png\">\r\n\r\n<img
width=\"2236\" alt=\"image\"
src=\"https://user-images.githubusercontent.com/92328789/236432072-da6efa55-0953-4abc-a5b5-c27be2b103ee.png\">\r\n\r\n*After:*\r\n\r\n<img
width=\"2267\" alt=\"image\"
src=\"4431eda1-0a69-403a-ad93-51658d0dbeff\">\r\n\r\n<img
width=\"2236\" alt=\"image\"
src=\"06647825-9b1f-4cd8-a60a-2c8988acbd9b\">\r\n\r\n\r\n##
Details\r\n\r\nRecent investigation has revealed emotion css styles
aren't applied correctly on production while the problem isn't
noticeable locally. This is caused by simultaneously using
**styled-components** and **emotion** in Security Solution plugin.
Further research lead to a way to fix it\r\n\r\n1. import `css` utility
function from `@emotion/css` instead of `@emotion/react`\r\n2. apply
styles using `className` instead of `css`\r\n\r\nLike in the code
below\r\n\r\n```ts\r\nimport { css } from
'@emotion/css';\r\n\r\n...\r\n\r\n<div className={css`\r\n padding-left:
200px;\r\n`}>\r\n
TEST\r\n</div>\r\n\r\n...\r\n```","sha":"8cf6d034e3a22370b73cf66ae893f8d7ff6b158d"}}]}]
BACKPORT-->

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
2023-05-23 11:00:09 +02:00