github-mirrors/kibana
1
0
Fork 0
mirror of https://github.com/elastic/kibana.git synced 2025-04-21 08:19:33 -04:00
Code Issues Projects Releases Packages Wiki Activity
63385 commits 434 branches 495 tags 22 GiB
Commit graph

7808 commits

Author SHA1 Message Date
Kibana Machine
d927533c49
[8.8] [Infrastructure UI] Host limit telemetry (#155726) (#157409) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Infrastructure UI] Host limit telemetry
(#155726)](https://github.com/elastic/kibana/pull/155726)

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

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

<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-11T15:44:38Z","message":"[Infrastructure
UI] Host limit telemetry (#155726)\n\ncloses:
https://github.com/elastic/kibana/issues/155567\r\n\r\n##
Summary\r\n\r\nThis PR adds a new custom event to track the total number
of hosts, as\r\nwell as adjusts a few `data-test-subj` attribute values
to meet the\r\nnaming convention defined in the
observability-dev\r\n[docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention)\r\n\r\n\r\n###
For Reviewers\r\n\r\nAn option for not allowing yet a new custom event
in FS could be\r\ntriggering the new custom events only for self-managed
customers, and in\r\nFS watch the element that holds the total number of
hosts. But for now,\r\nI decided to allow the new custom event in FS for
consistency\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"937912b056f5876247f27a7baad5314401e65939","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Metrics
UI","Team:Infra Monitoring
UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0"],"number":155726,"url":"https://github.com/elastic/kibana/pull/155726","mergeCommit":{"message":"[Infrastructure
UI] Host limit telemetry (#155726)\n\ncloses:
https://github.com/elastic/kibana/issues/155567\r\n\r\n##
Summary\r\n\r\nThis PR adds a new custom event to track the total number
of hosts, as\r\nwell as adjusts a few `data-test-subj` attribute values
to meet the\r\nnaming convention defined in the
observability-dev\r\n[docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention)\r\n\r\n\r\n###
For Reviewers\r\n\r\nAn option for not allowing yet a new custom event
in FS could be\r\ntriggering the new custom events only for self-managed
customers, and in\r\nFS watch the element that holds the total number of
hosts. But for now,\r\nI decided to allow the new custom event in FS for
consistency\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"937912b056f5876247f27a7baad5314401e65939"}},"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/155726","number":155726,"mergeCommit":{"message":"[Infrastructure
UI] Host limit telemetry (#155726)\n\ncloses:
https://github.com/elastic/kibana/issues/155567\r\n\r\n##
Summary\r\n\r\nThis PR adds a new custom event to track the total number
of hosts, as\r\nwell as adjusts a few `data-test-subj` attribute values
to meet the\r\nnaming convention defined in the
observability-dev\r\n[docs](https://github.com/elastic/observability-dev/blob/main/docs/how-we-work/telemetry/telemetry-convention.md#naming-convention)\r\n\r\n\r\n###
For Reviewers\r\n\r\nAn option for not allowing yet a new custom event
in FS could be\r\ntriggering the new custom events only for self-managed
customers, and in\r\nFS watch the element that holds the total number of
hosts. But for now,\r\nI decided to allow the new custom event in FS for
consistency\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"937912b056f5876247f27a7baad5314401e65939"}}]}]
BACKPORT-->

Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
 2023-05-11 10:01:52 -07:00
Kibana Machine
e5a2779330
[8.8] [Synthetics] allow saving params for lightweight monitors (#157226) (#157297) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Synthetics] allow saving params for lightweight monitors
(#157226)](https://github.com/elastic/kibana/pull/157226)

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

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

<!--BACKPORT [{"author":{"name":"Dominique
Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2023-05-10T15:58:32Z","message":"[Synthetics]
allow saving params for lightweight monitors (#157226)\n\n##
Summary\r\n\r\nRelates to
https://github.com/elastic/synthetics/issues/725\r\n\r\nAllows the
`params` value to be saved against lightweight monitors.\r\n\r\nThis
ensures that the formatters for both private and public location\r\ncan
access these params, and apply them as overwrites to global
params.\r\n\r\n### Testing\r\n\r\n1. Check out associated synthetics
agent PR \r\n2. Create a global parameter, for example
`GLOBAL_URL`\r\n3. Create lightweight monitor that uses that global
parameter in your\r\nproject file\r\n4. Push the monitor and navigate to
Synthetics. Ensure the monitor uses\r\nthe value of the `GLOBAL_URL`
parameter appropriately\r\n5. Navigate back to your project config. In
your `synthetics.config.ts`\r\nfile, add a param for `GLOBAL_URL`\r\n6.
Repush your monitor\r\n7. Confirm `GLOBAL_URL` is overwritten by the
pushed
params","sha":"1f99b80c5b876c68fd137972b49861fd7e590459","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","v8.8.0","v8.7.2","v8.9.0"],"number":157226,"url":"https://github.com/elastic/kibana/pull/157226","mergeCommit":{"message":"[Synthetics]
allow saving params for lightweight monitors (#157226)\n\n##
Summary\r\n\r\nRelates to
https://github.com/elastic/synthetics/issues/725\r\n\r\nAllows the
`params` value to be saved against lightweight monitors.\r\n\r\nThis
ensures that the formatters for both private and public location\r\ncan
access these params, and apply them as overwrites to global
params.\r\n\r\n### Testing\r\n\r\n1. Check out associated synthetics
agent PR \r\n2. Create a global parameter, for example
`GLOBAL_URL`\r\n3. Create lightweight monitor that uses that global
parameter in your\r\nproject file\r\n4. Push the monitor and navigate to
Synthetics. Ensure the monitor uses\r\nthe value of the `GLOBAL_URL`
parameter appropriately\r\n5. Navigate back to your project config. In
your `synthetics.config.ts`\r\nfile, add a param for `GLOBAL_URL`\r\n6.
Repush your monitor\r\n7. Confirm `GLOBAL_URL` is overwritten by the
pushed
params","sha":"1f99b80c5b876c68fd137972b49861fd7e590459"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.7"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","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/157226","number":157226,"mergeCommit":{"message":"[Synthetics]
allow saving params for lightweight monitors (#157226)\n\n##
Summary\r\n\r\nRelates to
https://github.com/elastic/synthetics/issues/725\r\n\r\nAllows the
`params` value to be saved against lightweight monitors.\r\n\r\nThis
ensures that the formatters for both private and public location\r\ncan
access these params, and apply them as overwrites to global
params.\r\n\r\n### Testing\r\n\r\n1. Check out associated synthetics
agent PR \r\n2. Create a global parameter, for example
`GLOBAL_URL`\r\n3. Create lightweight monitor that uses that global
parameter in your\r\nproject file\r\n4. Push the monitor and navigate to
Synthetics. Ensure the monitor uses\r\nthe value of the `GLOBAL_URL`
parameter appropriately\r\n5. Navigate back to your project config. In
your `synthetics.config.ts`\r\nfile, add a param for `GLOBAL_URL`\r\n6.
Repush your monitor\r\n7. Confirm `GLOBAL_URL` is overwritten by the
pushed params","sha":"1f99b80c5b876c68fd137972b49861fd7e590459"}}]}]
BACKPORT-->

Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co>
 2023-05-10 10:15:13 -07:00
Yulia Čech
7ae7eecbcc
[8.8] [Ingest Pipelines] Unskip functional and a11y tests (#157173) (#157257) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Ingest Pipelines] Unskip functional and a11y tests
(#157173)](https://github.com/elastic/kibana/pull/157173)

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

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

<!--BACKPORT [{"author":{"name":"Yulia
Čech","email":"6585477+yuliacech@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-09T16:08:15Z","message":"[Ingest
Pipelines] Unskip functional and a11y tests (#157173)\n\n##
Summary\r\nFixes
https://github.com/elastic/kibana/issues/156015\r\nFixes
https://github.com/elastic/kibana/issues/156014\r\nFixes
https://github.com/elastic/kibana/issues/155924 \r\nFixes
https://github.com/elastic/kibana/issues/155914\r\n\r\nThe Ingest
Pipelines tests were broken because of a new pipeline\r\nintroduced in
https://github.com/elastic/elasticsearch/pull/95198 but\r\nthere was a
fix added in\r\nhttps://github.com/elastic/elasticsearch/pull/95621. The
last PR fixes\r\nthe error where it was not possible to delete the
pipeline in the tests.\r\nThis PR unskips the tests since they should
now work as
expected.","sha":"32bc5c77bbe5b17215715ea56c4a13593855323c","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Deployment
Management","release_note:skip","Feature:Ingest Node
Pipelines","v8.8.0","v8.9.0"],"number":157173,"url":"https://github.com/elastic/kibana/pull/157173","mergeCommit":{"message":"[Ingest
Pipelines] Unskip functional and a11y tests (#157173)\n\n##
Summary\r\nFixes
https://github.com/elastic/kibana/issues/156015\r\nFixes
https://github.com/elastic/kibana/issues/156014\r\nFixes
https://github.com/elastic/kibana/issues/155924 \r\nFixes
https://github.com/elastic/kibana/issues/155914\r\n\r\nThe Ingest
Pipelines tests were broken because of a new pipeline\r\nintroduced in
https://github.com/elastic/elasticsearch/pull/95198 but\r\nthere was a
fix added in\r\nhttps://github.com/elastic/elasticsearch/pull/95621. The
last PR fixes\r\nthe error where it was not possible to delete the
pipeline in the tests.\r\nThis PR unskips the tests since they should
now work as
expected.","sha":"32bc5c77bbe5b17215715ea56c4a13593855323c"}},"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/157173","number":157173,"mergeCommit":{"message":"[Ingest
Pipelines] Unskip functional and a11y tests (#157173)\n\n##
Summary\r\nFixes
https://github.com/elastic/kibana/issues/156015\r\nFixes
https://github.com/elastic/kibana/issues/156014\r\nFixes
https://github.com/elastic/kibana/issues/155924 \r\nFixes
https://github.com/elastic/kibana/issues/155914\r\n\r\nThe Ingest
Pipelines tests were broken because of a new pipeline\r\nintroduced in
https://github.com/elastic/elasticsearch/pull/95198 but\r\nthere was a
fix added in\r\nhttps://github.com/elastic/elasticsearch/pull/95621. The
last PR fixes\r\nthe error where it was not possible to delete the
pipeline in the tests.\r\nThis PR unskips the tests since they should
now work as
expected.","sha":"32bc5c77bbe5b17215715ea56c4a13593855323c"}}]}]
BACKPORT-->
 2023-05-10 05:59:49 -07:00
Kibana Machine
951802a7a9
[8.8] [Security Solution][Alerts] resolves alerts suppression review feedback (#155839) (#157192) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution][Alerts] resolves alerts suppression review
feedback (#155839)](https://github.com/elastic/kibana/pull/155839)

<!--- 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-09T16:12:20Z","message":"[Security
Solution][Alerts] resolves alerts suppression review feedback
(#155839)\n\n## Summary\r\n\r\n- addresses review feedback
on\r\nhttps://github.com/elastic/kibana/pull/155055\r\n- addresses UI
changes from\r\nhttps://github.com/elastic/kibana/issues/150101\r\n -
removes accordion in favour of intended suppression components\r\n -
adds popover with a link to documentation\r\n - changes wording\r\n-
addresses https://github.com/elastic/kibana/issues/156247\r\n\r\n###
Before\r\n<img width=\"1017\" alt=\"Screenshot 2023-04-24 at 19 44
33\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/234824612-b0ed2870-8aa0-44af-a37d-c061358c54a3.png\">\r\n\r\n###
After\r\n\r\n#### Intended Fields\r\n<img width=\"1016\"
alt=\"Screenshot 2023-05-05 at 10 42
46\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/236426053-279d2f5b-46ea-434b-9cfa-696c71321661.png\">\r\n\r\n####
Tooltip\r\n<img width=\"1016\" alt=\"Screenshot 2023-05-05 at 10 43
41\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/236426061-1c39a5c2-63ca-4a36-b15e-2a1c1943481d.png\">\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Garrett Spong
<spong@users.noreply.github.com>","sha":"31b6062148b55f712015fc9061172eca54c0acd4","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:
SecuritySolution","Team:Detection
Alerts","backport:prev-minor","v8.8.0","v8.9.0"],"number":155839,"url":"https://github.com/elastic/kibana/pull/155839","mergeCommit":{"message":"[Security
Solution][Alerts] resolves alerts suppression review feedback
(#155839)\n\n## Summary\r\n\r\n- addresses review feedback
on\r\nhttps://github.com/elastic/kibana/pull/155055\r\n- addresses UI
changes from\r\nhttps://github.com/elastic/kibana/issues/150101\r\n -
removes accordion in favour of intended suppression components\r\n -
adds popover with a link to documentation\r\n - changes wording\r\n-
addresses https://github.com/elastic/kibana/issues/156247\r\n\r\n###
Before\r\n<img width=\"1017\" alt=\"Screenshot 2023-04-24 at 19 44
33\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/234824612-b0ed2870-8aa0-44af-a37d-c061358c54a3.png\">\r\n\r\n###
After\r\n\r\n#### Intended Fields\r\n<img width=\"1016\"
alt=\"Screenshot 2023-05-05 at 10 42
46\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/236426053-279d2f5b-46ea-434b-9cfa-696c71321661.png\">\r\n\r\n####
Tooltip\r\n<img width=\"1016\" alt=\"Screenshot 2023-05-05 at 10 43
41\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/236426061-1c39a5c2-63ca-4a36-b15e-2a1c1943481d.png\">\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Garrett Spong
<spong@users.noreply.github.com>","sha":"31b6062148b55f712015fc9061172eca54c0acd4"}},"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/155839","number":155839,"mergeCommit":{"message":"[Security
Solution][Alerts] resolves alerts suppression review feedback
(#155839)\n\n## Summary\r\n\r\n- addresses review feedback
on\r\nhttps://github.com/elastic/kibana/pull/155055\r\n- addresses UI
changes from\r\nhttps://github.com/elastic/kibana/issues/150101\r\n -
removes accordion in favour of intended suppression components\r\n -
adds popover with a link to documentation\r\n - changes wording\r\n-
addresses https://github.com/elastic/kibana/issues/156247\r\n\r\n###
Before\r\n<img width=\"1017\" alt=\"Screenshot 2023-04-24 at 19 44
33\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/234824612-b0ed2870-8aa0-44af-a37d-c061358c54a3.png\">\r\n\r\n###
After\r\n\r\n#### Intended Fields\r\n<img width=\"1016\"
alt=\"Screenshot 2023-05-05 at 10 42
46\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/236426053-279d2f5b-46ea-434b-9cfa-696c71321661.png\">\r\n\r\n####
Tooltip\r\n<img width=\"1016\" alt=\"Screenshot 2023-05-05 at 10 43
41\"\r\nsrc=\"https://user-images.githubusercontent.com/92328789/236426061-1c39a5c2-63ca-4a36-b15e-2a1c1943481d.png\">\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Garrett Spong
<spong@users.noreply.github.com>","sha":"31b6062148b55f712015fc9061172eca54c0acd4"}}]}]
BACKPORT-->

Co-authored-by: Vitalii Dmyterko <92328789+vitaliidm@users.noreply.github.com>
Co-authored-by: Pedro Jaramillo <pedro.jaramillo@elastic.co>
 2023-05-09 19:56:34 -07:00
Dominique Clarke
d10ba61d9f
[8.8] Revert "[Synthetics] quote monitor name to prevent invalid yaml" (#157143) (#157199) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [Revert "[Synthetics] quote monitor name to prevent invalid yaml"
(#157143)](https://github.com/elastic/kibana/pull/157143)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-05-09T11:15:46Z","message":"Revert
\"[Synthetics] quote monitor name to prevent invalid yaml\"
(#157143)","sha":"6220fae002425f4e955537c312d0e4e3c9d2bc2d","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","v8.8.0","v8.9.0"],"number":157143,"url":"https://github.com/elastic/kibana/pull/157143","mergeCommit":{"message":"Revert
\"[Synthetics] quote monitor name to prevent invalid yaml\"
(#157143)","sha":"6220fae002425f4e955537c312d0e4e3c9d2bc2d"}},"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/157143","number":157143,"mergeCommit":{"message":"Revert
\"[Synthetics] quote monitor name to prevent invalid yaml\"
(#157143)","sha":"6220fae002425f4e955537c312d0e4e3c9d2bc2d"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
 2023-05-09 12:14:24 -07:00
Tiago Costa
01aabf5792
skip flaky suite (#156106) 2023-05-09 16:46:54 +01:00
Kibana Machine
d366510a66
[8.8] [RAM] [PERF] Remove endpoint browserFields (#156869) (#157121) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[RAM] [PERF] Remove endpoint browserFields
(#156869)](https://github.com/elastic/kibana/pull/156869)

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

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

<!--BACKPORT [{"author":{"name":"Xavier
Mouligneau","email":"xavier.mouligneau@elastic.co"},"sourceCommit":{"committedDate":"2023-05-09T03:23:20Z","message":"[RAM]
[PERF] Remove endpoint browserFields (#156869)\n\n## Summary\r\n\r\nFix
https://github.com/elastic/kibana/issues/155000, @dgieselaar
thank\r\nyou so much for finding that!!! lot of love from our part. And,
we find\r\na good solution around this API... We are deleting it!!!
LOL\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---------\r\n\r\nCo-authored-by: Julian Gernun
<17549662+jcger@users.noreply.github.com>","sha":"967b88710d55f395065dd8150817281764dbc468","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v8.8.0","v8.7.2","v8.9.0"],"number":156869,"url":"https://github.com/elastic/kibana/pull/156869","mergeCommit":{"message":"[RAM]
[PERF] Remove endpoint browserFields (#156869)\n\n## Summary\r\n\r\nFix
https://github.com/elastic/kibana/issues/155000, @dgieselaar
thank\r\nyou so much for finding that!!! lot of love from our part. And,
we find\r\na good solution around this API... We are deleting it!!!
LOL\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---------\r\n\r\nCo-authored-by: Julian Gernun
<17549662+jcger@users.noreply.github.com>","sha":"967b88710d55f395065dd8150817281764dbc468"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.7"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","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/156869","number":156869,"mergeCommit":{"message":"[RAM]
[PERF] Remove endpoint browserFields (#156869)\n\n## Summary\r\n\r\nFix
https://github.com/elastic/kibana/issues/155000, @dgieselaar
thank\r\nyou so much for finding that!!! lot of love from our part. And,
we find\r\na good solution around this API... We are deleting it!!!
LOL\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---------\r\n\r\nCo-authored-by: Julian Gernun
<17549662+jcger@users.noreply.github.com>","sha":"967b88710d55f395065dd8150817281764dbc468"}}]}]
BACKPORT-->

Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
 2023-05-08 22:26:05 -07:00
Kibana Machine
f55816f117
[8.8] [RAM][8.8] Fix get active maintenance window query (#157112) (#157119) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[RAM][8.8] Fix get active maintenance window query
(#157112)](https://github.com/elastic/kibana/pull/157112)

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

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

<!--BACKPORT [{"author":{"name":"Jiawei
Wu","email":"74562234+JiaweiWu@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-09T02:27:59Z","message":"[RAM][8.8]
Fix get active maintenance window query (#157112)\n\n## Summary\r\nFix
the active maintenance window query, originally the KQL query
got\r\nconverted to something like:\r\n\r\n```\r\n query: {\r\n bool:
{\r\n filter: [\r\n {\r\n range: {\r\n
'maintenance-window.attributes.events': {\r\n gte: from,\r\n },\r\n
},\r\n },\r\n {\r\n range: {\r\n 'maintenance-window.attributes.events':
{\r\n lte: to,\r\n },\r\n },\r\n },\r\n ],\r\n },\r\n},\r\n```\r\nWhen
in reality we wanted a query like:\r\n\r\n```\r\nquery: {\r\n bool:
{\r\n filter: \r\n range: {\r\n 'maintenance-window.attributes.events':
{\r\n gte: from,\r\n lte: to,\r\n },\r\n },\r\n },\r\n
},\r\n},\r\n```\r\nWhich return some upcoming maintenance windows that
we did not want.\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":"6d4f695b759b8fe30ac7314951c39dce6f27e376","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","backport","release_note:skip","Team:ResponseOps","Feature:Alerting/RulesManagement","v8.8.0","v8.9.0"],"number":157112,"url":"https://github.com/elastic/kibana/pull/157112","mergeCommit":{"message":"[RAM][8.8]
Fix get active maintenance window query (#157112)\n\n## Summary\r\nFix
the active maintenance window query, originally the KQL query
got\r\nconverted to something like:\r\n\r\n```\r\n query: {\r\n bool:
{\r\n filter: [\r\n {\r\n range: {\r\n
'maintenance-window.attributes.events': {\r\n gte: from,\r\n },\r\n
},\r\n },\r\n {\r\n range: {\r\n 'maintenance-window.attributes.events':
{\r\n lte: to,\r\n },\r\n },\r\n },\r\n ],\r\n },\r\n},\r\n```\r\nWhen
in reality we wanted a query like:\r\n\r\n```\r\nquery: {\r\n bool:
{\r\n filter: \r\n range: {\r\n 'maintenance-window.attributes.events':
{\r\n gte: from,\r\n lte: to,\r\n },\r\n },\r\n },\r\n
},\r\n},\r\n```\r\nWhich return some upcoming maintenance windows that
we did not want.\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":"6d4f695b759b8fe30ac7314951c39dce6f27e376"}},"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/157112","number":157112,"mergeCommit":{"message":"[RAM][8.8]
Fix get active maintenance window query (#157112)\n\n## Summary\r\nFix
the active maintenance window query, originally the KQL query
got\r\nconverted to something like:\r\n\r\n```\r\n query: {\r\n bool:
{\r\n filter: [\r\n {\r\n range: {\r\n
'maintenance-window.attributes.events': {\r\n gte: from,\r\n },\r\n
},\r\n },\r\n {\r\n range: {\r\n 'maintenance-window.attributes.events':
{\r\n lte: to,\r\n },\r\n },\r\n },\r\n ],\r\n },\r\n},\r\n```\r\nWhen
in reality we wanted a query like:\r\n\r\n```\r\nquery: {\r\n bool:
{\r\n filter: \r\n range: {\r\n 'maintenance-window.attributes.events':
{\r\n gte: from,\r\n lte: to,\r\n },\r\n },\r\n },\r\n
},\r\n},\r\n```\r\nWhich return some upcoming maintenance windows that
we did not want.\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":"6d4f695b759b8fe30ac7314951c39dce6f27e376"}}]}]
BACKPORT-->

Co-authored-by: Jiawei Wu <74562234+JiaweiWu@users.noreply.github.com>
 2023-05-08 21:33:24 -07:00
Kibana Machine
07208d7518
[8.8] [RAM] alert table support runtime field (#156899) (#157037) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[RAM] alert table support runtime field
(#156899)](https://github.com/elastic/kibana/pull/156899)

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

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

<!--BACKPORT [{"author":{"name":"Xavier
Mouligneau","email":"xavier.mouligneau@elastic.co"},"sourceCommit":{"committedDate":"2023-05-08T17:44:13Z","message":"[RAM]
alert table support runtime field (#156899)\n\n## Summary\r\n\r\nFIX
https://github.com/elastic/kibana/issues/156263
&\r\nhttps://github.com/elastic/kibana/issues/155488\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"73d60085d11cd28b1eadefa63c2fcc1704336ef9","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:ResponseOps","v8.8.0","v8.9.0"],"number":156899,"url":"https://github.com/elastic/kibana/pull/156899","mergeCommit":{"message":"[RAM]
alert table support runtime field (#156899)\n\n## Summary\r\n\r\nFIX
https://github.com/elastic/kibana/issues/156263
&\r\nhttps://github.com/elastic/kibana/issues/155488\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"73d60085d11cd28b1eadefa63c2fcc1704336ef9"}},"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/156899","number":156899,"mergeCommit":{"message":"[RAM]
alert table support runtime field (#156899)\n\n## Summary\r\n\r\nFIX
https://github.com/elastic/kibana/issues/156263
&\r\nhttps://github.com/elastic/kibana/issues/155488\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios","sha":"73d60085d11cd28b1eadefa63c2fcc1704336ef9"}}]}]
BACKPORT-->

Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
 2023-05-08 16:30:01 -07:00
Dominique Clarke
e71a54fd7c
[8.8] [Synthetics] quote monitor name to prevent invalid yaml (#156210) (#157087) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Synthetics] quote monitor name to prevent invalid yaml
(#156210)](https://github.com/elastic/kibana/pull/156210)

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

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

<!--BACKPORT [{"author":{"name":"Dominique
Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2023-05-08T17:13:19Z","message":"[Synthetics]
quote monitor name to prevent invalid yaml (#156210)\n\n##
Summary\r\n\r\nAppropriately quotes monitor names for synthetics
integration policies,\r\nto ensure that customers can use monitor names
that would otherwise\r\nbreak yaml.\r\n\r\n### Testing\r\n1. Create a
private location\r\n2. Save a monitor with name `[Synthetics] test` to
that private location\r\n3. Navigate to the agent policy for that
location. Confirm that the\r\nintegration policy was added to the agent
policy, and that the name
is\r\ncorrect\r\n\r\n---------\r\n\r\nCo-authored-by: shahzad31
<shahzad31comp@gmail.com>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a22561a524c73bab055e2a7eb7411cc36158c856","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":156210,"url":"https://github.com/elastic/kibana/pull/156210","mergeCommit":{"message":"[Synthetics]
quote monitor name to prevent invalid yaml (#156210)\n\n##
Summary\r\n\r\nAppropriately quotes monitor names for synthetics
integration policies,\r\nto ensure that customers can use monitor names
that would otherwise\r\nbreak yaml.\r\n\r\n### Testing\r\n1. Create a
private location\r\n2. Save a monitor with name `[Synthetics] test` to
that private location\r\n3. Navigate to the agent policy for that
location. Confirm that the\r\nintegration policy was added to the agent
policy, and that the name
is\r\ncorrect\r\n\r\n---------\r\n\r\nCo-authored-by: shahzad31
<shahzad31comp@gmail.com>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a22561a524c73bab055e2a7eb7411cc36158c856"}},"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/156210","number":156210,"mergeCommit":{"message":"[Synthetics]
quote monitor name to prevent invalid yaml (#156210)\n\n##
Summary\r\n\r\nAppropriately quotes monitor names for synthetics
integration policies,\r\nto ensure that customers can use monitor names
that would otherwise\r\nbreak yaml.\r\n\r\n### Testing\r\n1. Create a
private location\r\n2. Save a monitor with name `[Synthetics] test` to
that private location\r\n3. Navigate to the agent policy for that
location. Confirm that the\r\nintegration policy was added to the agent
policy, and that the name
is\r\ncorrect\r\n\r\n---------\r\n\r\nCo-authored-by: shahzad31
<shahzad31comp@gmail.com>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"a22561a524c73bab055e2a7eb7411cc36158c856"}}]}]
BACKPORT-->
 2023-05-08 15:17:45 -07:00
Kibana Machine
4a7d2b3211
[8.8] [RAM] Docs for slack improvements (#153885) (#156794) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[RAM] Docs for slack improvements
(#153885)](https://github.com/elastic/kibana/pull/153885)

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

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

<!--BACKPORT
[{"author":{"name":"Julia","email":"iuliia.guskova@elastic.co"},"sourceCommit":{"committedDate":"2023-05-05T07:32:45Z","message":"[RAM]
Docs for slack improvements (#153885)\n\n## Summary\r\n\r\nDocs for new
Slack connector\r\n\r\n###
Preview\r\n\r\n\r\nhttps://kibana_153885.docs-preview.app.elstc.co/guide/en/kibana/master/slack-action-type.html\r\n\r\n---------\r\n\r\nCo-authored-by:
lcawl <lcawley@elastic.co>\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"4dd6d1a277953098b4f308253a889ab50f0c4ef5","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Actions/ConnectorTypes","ui-copy","backport:prev-minor","v8.8.0","v8.9.0"],"number":153885,"url":"https://github.com/elastic/kibana/pull/153885","mergeCommit":{"message":"[RAM]
Docs for slack improvements (#153885)\n\n## Summary\r\n\r\nDocs for new
Slack connector\r\n\r\n###
Preview\r\n\r\n\r\nhttps://kibana_153885.docs-preview.app.elstc.co/guide/en/kibana/master/slack-action-type.html\r\n\r\n---------\r\n\r\nCo-authored-by:
lcawl <lcawley@elastic.co>\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"4dd6d1a277953098b4f308253a889ab50f0c4ef5"}},"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/153885","number":153885,"mergeCommit":{"message":"[RAM]
Docs for slack improvements (#153885)\n\n## Summary\r\n\r\nDocs for new
Slack connector\r\n\r\n###
Preview\r\n\r\n\r\nhttps://kibana_153885.docs-preview.app.elstc.co/guide/en/kibana/master/slack-action-type.html\r\n\r\n---------\r\n\r\nCo-authored-by:
lcawl <lcawley@elastic.co>\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"4dd6d1a277953098b4f308253a889ab50f0c4ef5"}}]}]
BACKPORT-->

---------

Co-authored-by: Julia <iuliia.guskova@elastic.co>
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
 2023-05-08 14:17:45 -07:00
Tiago Costa
17b34f6aad
skip flaky suite (#136153) 2023-05-08 22:00:39 +01:00
Kibana Machine
387949f120
[8.8] [Synthetics] Private location better error handling (#152695) (#156807) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Synthetics] Private location better error handling
(#152695)](https://github.com/elastic/kibana/pull/152695)

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

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

<!--BACKPORT
[{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2023-05-05T09:31:59Z","message":"[Synthetics]
Private location better error handling (#152695)\n\nCo-authored-by:
Dominique Clarke
<dominique.clarke@elastic.co>","sha":"1aba7df3363d25a24b35fd0f716d5f89c76c41b8","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:uptime","release_note:skip","Team:Fleet","v8.8.0","v8.9.0"],"number":152695,"url":"https://github.com/elastic/kibana/pull/152695","mergeCommit":{"message":"[Synthetics]
Private location better error handling (#152695)\n\nCo-authored-by:
Dominique Clarke
<dominique.clarke@elastic.co>","sha":"1aba7df3363d25a24b35fd0f716d5f89c76c41b8"}},"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/152695","number":152695,"mergeCommit":{"message":"[Synthetics]
Private location better error handling (#152695)\n\nCo-authored-by:
Dominique Clarke
<dominique.clarke@elastic.co>","sha":"1aba7df3363d25a24b35fd0f716d5f89c76c41b8"}}]}]
BACKPORT-->

Co-authored-by: Shahzad <shahzad31comp@gmail.com>
Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co>
 2023-05-08 13:43:43 -07:00
Kibana Machine
075a1e380f
[8.8] [Fleet] Add integration test for epm install on multiple spaces (#156864) (#157005) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Fleet] Add integration test for epm install on multiple spaces
(#156864)](https://github.com/elastic/kibana/pull/156864)

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

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

<!--BACKPORT [{"author":{"name":"Cristina
Amico","email":"criamico@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-08T14:39:24Z","message":"[Fleet]
Add integration test for epm install on multiple spaces
(#156864)\n\nCloses
https://github.com/elastic/kibana/issues/150686\r\n\r\n##
Summary\r\n\r\nAdd integration test to cover integration installation in
multiple\r\nspaces\r\n\r\nSteps followed:\r\n- Install System
integration\r\n- Create new space\r\n- Uninstall System integration\r\n-
Install again in the new space\r\n- Verify that integration is added
successfully, assets are created and\r\ntagged with Managed and System
tags\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"de48b5d9aca1e41bcd33534844a49bb4efb7754d","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.8.0","v8.9.0"],"number":156864,"url":"https://github.com/elastic/kibana/pull/156864","mergeCommit":{"message":"[Fleet]
Add integration test for epm install on multiple spaces
(#156864)\n\nCloses
https://github.com/elastic/kibana/issues/150686\r\n\r\n##
Summary\r\n\r\nAdd integration test to cover integration installation in
multiple\r\nspaces\r\n\r\nSteps followed:\r\n- Install System
integration\r\n- Create new space\r\n- Uninstall System integration\r\n-
Install again in the new space\r\n- Verify that integration is added
successfully, assets are created and\r\ntagged with Managed and System
tags\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"de48b5d9aca1e41bcd33534844a49bb4efb7754d"}},"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/156864","number":156864,"mergeCommit":{"message":"[Fleet]
Add integration test for epm install on multiple spaces
(#156864)\n\nCloses
https://github.com/elastic/kibana/issues/150686\r\n\r\n##
Summary\r\n\r\nAdd integration test to cover integration installation in
multiple\r\nspaces\r\n\r\nSteps followed:\r\n- Install System
integration\r\n- Create new space\r\n- Uninstall System integration\r\n-
Install again in the new space\r\n- Verify that integration is added
successfully, assets are created and\r\ntagged with Managed and System
tags\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"de48b5d9aca1e41bcd33534844a49bb4efb7754d"}}]}]
BACKPORT-->

Co-authored-by: Cristina Amico <criamico@users.noreply.github.com>
 2023-05-08 09:17:28 -07:00
Kibana Machine
ff9fcc09c3
[8.8] [DOCS] Automate observability case file screenshot (#156775) (#157003) 
# Backport

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

<!--- 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-08T14:20:15Z","message":"[DOCS]
Automate observability case file screenshot
(#156775)","sha":"aaa77f462396c323dc47fb68888899cdb20d5cd6","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Cases","backport:prev-minor","v8.8.0","v8.9.0"],"number":156775,"url":"https://github.com/elastic/kibana/pull/156775","mergeCommit":{"message":"[DOCS]
Automate observability case file screenshot
(#156775)","sha":"aaa77f462396c323dc47fb68888899cdb20d5cd6"}},"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/156775","number":156775,"mergeCommit":{"message":"[DOCS]
Automate observability case file screenshot
(#156775)","sha":"aaa77f462396c323dc47fb68888899cdb20d5cd6"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
 2023-05-08 08:17:55 -07:00
Kibana Machine
5b0052ed9a
[8.8] Attempt to make Cases FTR tests less fragile (#156972) (#156983) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [Attempt to make Cases FTR tests less fragile
(#156972)](https://github.com/elastic/kibana/pull/156972)

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

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

<!--BACKPORT [{"author":{"name":"Coen
Warmer","email":"coen.warmer@gmail.com"},"sourceCommit":{"committedDate":"2023-05-08T12:28:00Z","message":"Attempt
to make Cases FTR tests less fragile
(#156972)","sha":"6ad8c42d58a30e8188776bf56479124e7941f569","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","v8.8.0","v8.9.0"],"number":156972,"url":"https://github.com/elastic/kibana/pull/156972","mergeCommit":{"message":"Attempt
to make Cases FTR tests less fragile
(#156972)","sha":"6ad8c42d58a30e8188776bf56479124e7941f569"}},"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/156972","number":156972,"mergeCommit":{"message":"Attempt
to make Cases FTR tests less fragile
(#156972)","sha":"6ad8c42d58a30e8188776bf56479124e7941f569"}}]}]
BACKPORT-->

Co-authored-by: Coen Warmer <coen.warmer@gmail.com>
 2023-05-08 06:29:00 -07:00
Kibana Machine
2a20412fd0
[8.8] [Cloud Security][Bug Fix] Empty EKS Dashboard / Wrong number of Healthy agents shown fix (#156601) (#156919) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Cloud Security][Bug Fix] Empty EKS Dashboard / Wrong number of
Healthy agents shown fix
(#156601)](https://github.com/elastic/kibana/pull/156601)

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

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

<!--BACKPORT [{"author":{"name":"Rickyanto
Ang","email":"rickyangwyn@gmail.com"},"sourceCommit":{"committedDate":"2023-05-05T20:44:05Z","message":"[Cloud
Security][Bug Fix] Empty EKS Dashboard / Wrong number of Healthy agents
shown fix (#156601)\n\n## Summary\r\n\r\nThis Fix is to address issue
where Healthy agents remains zero even when\r\nwe have Healthy agents
and EKS Dashboard is empty even though we have\r\nfindings for that
integration flowing in\r\n\r\nAlso added new API test for
Benchmark\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b5fc7c4054a1bb97e4f522ee61c19a62054cace9","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Cloud
Security","v8.8.0","v8.9.0"],"number":156601,"url":"https://github.com/elastic/kibana/pull/156601","mergeCommit":{"message":"[Cloud
Security][Bug Fix] Empty EKS Dashboard / Wrong number of Healthy agents
shown fix (#156601)\n\n## Summary\r\n\r\nThis Fix is to address issue
where Healthy agents remains zero even when\r\nwe have Healthy agents
and EKS Dashboard is empty even though we have\r\nfindings for that
integration flowing in\r\n\r\nAlso added new API test for
Benchmark\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b5fc7c4054a1bb97e4f522ee61c19a62054cace9"}},"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/156601","number":156601,"mergeCommit":{"message":"[Cloud
Security][Bug Fix] Empty EKS Dashboard / Wrong number of Healthy agents
shown fix (#156601)\n\n## Summary\r\n\r\nThis Fix is to address issue
where Healthy agents remains zero even when\r\nwe have Healthy agents
and EKS Dashboard is empty even though we have\r\nfindings for that
integration flowing in\r\n\r\nAlso added new API test for
Benchmark\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"b5fc7c4054a1bb97e4f522ee61c19a62054cace9"}}]}]
BACKPORT-->

Co-authored-by: Rickyanto Ang <rickyangwyn@gmail.com>
 2023-05-05 14:56:08 -07:00
Tiago Costa
5d2cbb7852
skip flaky suite (#155846) 2023-05-05 20:04:26 +01:00
Kibana Machine
aa02d2e5e3 skip failing test suite (#156346) 2023-05-05 14:22:48 -04:00
Tiago Costa
d8bd37c58e
skip failing es promotion suites (#156902) 2023-05-05 19:08:17 +01:00
Tiago Costa
d7c83d4779
skip failing es promotion suites (#156901) 2023-05-05 19:02:41 +01:00
Kibana Machine
c9f4b22a26
[8.8] [Dashboard] Fix "Unlink from library" panel title bug (#156589) (#156871) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Dashboard] Fix "Unlink from library" panel title bug
(#156589)](https://github.com/elastic/kibana/pull/156589)

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

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

<!--BACKPORT [{"author":{"name":"Hannah
Mudge","email":"Heenawter@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-05T14:54:39Z","message":"[Dashboard]
Fix \"Unlink from library\" panel title bug (#156589)\n\nCloses
https://github.com/elastic/kibana/issues/156539\r\nCloses
https://github.com/elastic/kibana/issues/156544\r\n\r\n##
Summary\r\n\r\n\r\nAs part of investigating the attached flaky test
suite, I realized that\r\nthe flakiness was because we weren't waiting
long enough for a panel to\r\nbe added and/or removed from the library -
so, I added a check to ensure\r\nthe library notification appears in
`saveToLibrary`, and similarly I\r\nadded a check to ensure that the
library notification **disappears**
in\r\n`unlinkFromLibary`.\r\n\r\nHowever, after adding these extra
checks, the following test started
to\r\nfail:\r\n\r\n\r\n23a45bde21/x-pack/test/functional/apps/dashboard/group2/panel_titles.ts (L148-L155)\r\n\r\nWay,
way, way back in `8.1`, one of my
[first\r\nPRs](https://github.com/elastic/kibana/pull/120815) was meant
to fix\r\nsome problems with dashboard panel titles - as part of this, I
was\r\n**supposed** to make sure that, if a by-reference panel is given
a\r\ncustom panel title, the title should remain the same after
unlinking\r\n(i.e. it should remain as the custom title rather than
resetting to the\r\nby-reference title). So, I added the above test to
verify this\r\nbehaviour.\r\n\r\nTurns out, though, that this test had a
flaw - because we weren't\r\nwaiting long enough for the panel to
actually be disconnected from the\r\nlibrary, this test was only passing
because it was grabbing and\r\ncomparing titles **before** the unlink
was complete - so, even though\r\nthe title actually **was** being reset
back to the original library\r\ntitle, this test did not catch this bug.
This has been the case since\r\n`8.1` when this test was introduced -
not sure how it was missed, but we\r\nnever actually fixed the bug where
dashboard panel titles are getting\r\nreset when unlinking from the
library.\r\n\r\nSo, this PR actually accomplishes two things:\r\n1) It
fixes the flakiness of the attached tests by adding the extra\r\nlibrary
notification
checks:\r\n<a\r\nhref=\"236044233-8a07aadc-8a55-40f2-9ed2-798a91501f68.png\"/></a>\r\n2)
It ensures that, if a by-reference panel has a custom
title,\r\nunlinking it from the library will not impact that
title.\r\n\r\n###
Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/8698078/236062484-b1cedc47-cb19-4273-aec7-17d24b55953b.mov\r\n\r\n\r\n###
After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/8698078/236062862-aace4f09-d007-401a-ba57-b9b74fda0b33.mov\r\n\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\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":"ce7ef40d9a79313be64057af6fb7f143a44a434a","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Feature:Embedding","release_note:fix","Team:Presentation","loe:days","impact:high","backport:prev-minor","v8.9.0"],"number":156589,"url":"https://github.com/elastic/kibana/pull/156589","mergeCommit":{"message":"[Dashboard]
Fix \"Unlink from library\" panel title bug (#156589)\n\nCloses
https://github.com/elastic/kibana/issues/156539\r\nCloses
https://github.com/elastic/kibana/issues/156544\r\n\r\n##
Summary\r\n\r\n\r\nAs part of investigating the attached flaky test
suite, I realized that\r\nthe flakiness was because we weren't waiting
long enough for a panel to\r\nbe added and/or removed from the library -
so, I added a check to ensure\r\nthe library notification appears in
`saveToLibrary`, and similarly I\r\nadded a check to ensure that the
library notification **disappears**
in\r\n`unlinkFromLibary`.\r\n\r\nHowever, after adding these extra
checks, the following test started
to\r\nfail:\r\n\r\n\r\n23a45bde21/x-pack/test/functional/apps/dashboard/group2/panel_titles.ts (L148-L155)\r\n\r\nWay,
way, way back in `8.1`, one of my
[first\r\nPRs](https://github.com/elastic/kibana/pull/120815) was meant
to fix\r\nsome problems with dashboard panel titles - as part of this, I
was\r\n**supposed** to make sure that, if a by-reference panel is given
a\r\ncustom panel title, the title should remain the same after
unlinking\r\n(i.e. it should remain as the custom title rather than
resetting to the\r\nby-reference title). So, I added the above test to
verify this\r\nbehaviour.\r\n\r\nTurns out, though, that this test had a
flaw - because we weren't\r\nwaiting long enough for the panel to
actually be disconnected from the\r\nlibrary, this test was only passing
because it was grabbing and\r\ncomparing titles **before** the unlink
was complete - so, even though\r\nthe title actually **was** being reset
back to the original library\r\ntitle, this test did not catch this bug.
This has been the case since\r\n`8.1` when this test was introduced -
not sure how it was missed, but we\r\nnever actually fixed the bug where
dashboard panel titles are getting\r\nreset when unlinking from the
library.\r\n\r\nSo, this PR actually accomplishes two things:\r\n1) It
fixes the flakiness of the attached tests by adding the extra\r\nlibrary
notification
checks:\r\n<a\r\nhref=\"236044233-8a07aadc-8a55-40f2-9ed2-798a91501f68.png\"/></a>\r\n2)
It ensures that, if a by-reference panel has a custom
title,\r\nunlinking it from the library will not impact that
title.\r\n\r\n###
Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/8698078/236062484-b1cedc47-cb19-4273-aec7-17d24b55953b.mov\r\n\r\n\r\n###
After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/8698078/236062862-aace4f09-d007-401a-ba57-b9b74fda0b33.mov\r\n\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\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":"ce7ef40d9a79313be64057af6fb7f143a44a434a"}},"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/156589","number":156589,"mergeCommit":{"message":"[Dashboard]
Fix \"Unlink from library\" panel title bug (#156589)\n\nCloses
https://github.com/elastic/kibana/issues/156539\r\nCloses
https://github.com/elastic/kibana/issues/156544\r\n\r\n##
Summary\r\n\r\n\r\nAs part of investigating the attached flaky test
suite, I realized that\r\nthe flakiness was because we weren't waiting
long enough for a panel to\r\nbe added and/or removed from the library -
so, I added a check to ensure\r\nthe library notification appears in
`saveToLibrary`, and similarly I\r\nadded a check to ensure that the
library notification **disappears**
in\r\n`unlinkFromLibary`.\r\n\r\nHowever, after adding these extra
checks, the following test started
to\r\nfail:\r\n\r\n\r\n23a45bde21/x-pack/test/functional/apps/dashboard/group2/panel_titles.ts (L148-L155)\r\n\r\nWay,
way, way back in `8.1`, one of my
[first\r\nPRs](https://github.com/elastic/kibana/pull/120815) was meant
to fix\r\nsome problems with dashboard panel titles - as part of this, I
was\r\n**supposed** to make sure that, if a by-reference panel is given
a\r\ncustom panel title, the title should remain the same after
unlinking\r\n(i.e. it should remain as the custom title rather than
resetting to the\r\nby-reference title). So, I added the above test to
verify this\r\nbehaviour.\r\n\r\nTurns out, though, that this test had a
flaw - because we weren't\r\nwaiting long enough for the panel to
actually be disconnected from the\r\nlibrary, this test was only passing
because it was grabbing and\r\ncomparing titles **before** the unlink
was complete - so, even though\r\nthe title actually **was** being reset
back to the original library\r\ntitle, this test did not catch this bug.
This has been the case since\r\n`8.1` when this test was introduced -
not sure how it was missed, but we\r\nnever actually fixed the bug where
dashboard panel titles are getting\r\nreset when unlinking from the
library.\r\n\r\nSo, this PR actually accomplishes two things:\r\n1) It
fixes the flakiness of the attached tests by adding the extra\r\nlibrary
notification
checks:\r\n<a\r\nhref=\"236044233-8a07aadc-8a55-40f2-9ed2-798a91501f68.png\"/></a>\r\n2)
It ensures that, if a by-reference panel has a custom
title,\r\nunlinking it from the library will not impact that
title.\r\n\r\n###
Before\r\n\r\n\r\nhttps://user-images.githubusercontent.com/8698078/236062484-b1cedc47-cb19-4273-aec7-17d24b55953b.mov\r\n\r\n\r\n###
After\r\n\r\n\r\nhttps://user-images.githubusercontent.com/8698078/236062862-aace4f09-d007-401a-ba57-b9b74fda0b33.mov\r\n\r\n\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common scenarios\r\n- [x] This was
checked for
[cross-browser\r\ncompatibility](https://www.elastic.co/support/matrix#matrix_browsers)\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":"ce7ef40d9a79313be64057af6fb7f143a44a434a"}}]}]
BACKPORT-->

Co-authored-by: Hannah Mudge <Heenawter@users.noreply.github.com>
 2023-05-05 09:11:49 -07:00
Kibana Machine
b02e35daf9
[8.8] [TSVB] Remove all usages of resetPage from tests (#156785) (#156865) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[TSVB] Remove all usages of resetPage from tests
(#156785)](https://github.com/elastic/kibana/pull/156785)

<!--- 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-05T13:47:50Z","message":"[TSVB]
Remove all usages of resetPage from tests (#156785)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/156705\r\nCloses
https://github.com/elastic/kibana/issues/156796\r\n\r\nRemoves all the
visualBuilder.resetPage() usages as they are
flaky.","sha":"589e21b0d2827ef535dc293d79c06855fd79b837","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:TSVB","Team:Visualizations","failed-test","release_note:skip","backport:prev-minor","v8.8.0","v8.9.0"],"number":156785,"url":"https://github.com/elastic/kibana/pull/156785","mergeCommit":{"message":"[TSVB]
Remove all usages of resetPage from tests (#156785)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/156705\r\nCloses
https://github.com/elastic/kibana/issues/156796\r\n\r\nRemoves all the
visualBuilder.resetPage() usages as they are
flaky.","sha":"589e21b0d2827ef535dc293d79c06855fd79b837"}},"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/156785","number":156785,"mergeCommit":{"message":"[TSVB]
Remove all usages of resetPage from tests (#156785)\n\n##
Summary\r\n\r\nCloses
https://github.com/elastic/kibana/issues/156705\r\nCloses
https://github.com/elastic/kibana/issues/156796\r\n\r\nRemoves all the
visualBuilder.resetPage() usages as they are
flaky.","sha":"589e21b0d2827ef535dc293d79c06855fd79b837"}}]}]
BACKPORT-->

Co-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
 2023-05-05 07:54:59 -07:00
Kibana Machine
772c00c87e
[8.8] [ResponseOps][Maintenance Window] Add and improve E2E tests for the maintenance window table (#156611) (#156853) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ResponseOps][Maintenance Window] Add and improve E2E tests for the
maintenance window table
(#156611)](https://github.com/elastic/kibana/pull/156611)

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

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

<!--BACKPORT [{"author":{"name":"Alexi
Doak","email":"109488926+doakalexi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-05T12:47:40Z","message":"[ResponseOps][Maintenance
Window] Add and improve E2E tests for the maintenance window table
(#156611)\n\n## Summary\r\n\r\nAdds functional tests for the maintenance
windows table.\r\n\r\nShould test:\r\n- Cancel a maintenance window\r\n-
Archiving/Unarchiving a maintenance window\r\n- Cancelling and archiving
a maintenance window\r\n- Searching/filtering\r\n\r\n\r\nIssue linked -
https://github.com/elastic/kibana/issues/155902","sha":"3fef5e5cda748c11786cfe66f69644b56841d656","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","v8.8.0","v8.9.0"],"number":156611,"url":"https://github.com/elastic/kibana/pull/156611","mergeCommit":{"message":"[ResponseOps][Maintenance
Window] Add and improve E2E tests for the maintenance window table
(#156611)\n\n## Summary\r\n\r\nAdds functional tests for the maintenance
windows table.\r\n\r\nShould test:\r\n- Cancel a maintenance window\r\n-
Archiving/Unarchiving a maintenance window\r\n- Cancelling and archiving
a maintenance window\r\n- Searching/filtering\r\n\r\n\r\nIssue linked -
https://github.com/elastic/kibana/issues/155902","sha":"3fef5e5cda748c11786cfe66f69644b56841d656"}},"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/156611","number":156611,"mergeCommit":{"message":"[ResponseOps][Maintenance
Window] Add and improve E2E tests for the maintenance window table
(#156611)\n\n## Summary\r\n\r\nAdds functional tests for the maintenance
windows table.\r\n\r\nShould test:\r\n- Cancel a maintenance window\r\n-
Archiving/Unarchiving a maintenance window\r\n- Cancelling and archiving
a maintenance window\r\n- Searching/filtering\r\n\r\n\r\nIssue linked -
https://github.com/elastic/kibana/issues/155902","sha":"3fef5e5cda748c11786cfe66f69644b56841d656"}}]}]
BACKPORT-->

Co-authored-by: Alexi Doak <109488926+doakalexi@users.noreply.github.com>
 2023-05-05 07:52:38 -07:00
Kibana Machine
a93823e4a9
[8.8] skip field_formatters test suite (#156834) (#156846) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [skip field_formatters test suite
(#156834)](https://github.com/elastic/kibana/pull/156834)

<!--- 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-05T12:25:16Z","message":"skip
field_formatters test suite (#156834)\n\n## Summary\r\n\r\nSkipping due
to multiple failures
#156153","sha":"88cbc0f641d3fdf02b6fb0325a491a49703bbd75","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","v8.9.0","v8.8.1"],"number":156834,"url":"https://github.com/elastic/kibana/pull/156834","mergeCommit":{"message":"skip
field_formatters test suite (#156834)\n\n## Summary\r\n\r\nSkipping due
to multiple failures
#156153","sha":"88cbc0f641d3fdf02b6fb0325a491a49703bbd75"}},"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/156834","number":156834,"mergeCommit":{"message":"skip
field_formatters test suite (#156834)\n\n## Summary\r\n\r\nSkipping due
to multiple failures
#156153","sha":"88cbc0f641d3fdf02b6fb0325a491a49703bbd75"}},{"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-05 13:33:33 +01:00
Tiago Costa
c58ada9d2c
skip flaky suite (#156792) 2023-05-05 13:16:23 +01:00
Kibana Machine
36d827ad1d
[8.8] [ML] Functional tests - stabilize export job tests (#156586) (#156790) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ML] Functional tests - stabilize export job tests
(#156586)](https://github.com/elastic/kibana/pull/156586)

<!--- 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-05T07:17:04Z","message":"[ML]
Functional tests - stabilize export job tests (#156586)\n\nThis PR
stabilizes the export job tests by making sure the export\r\nsuccess
toast is closed before moving on to the next test. As part of\r\nthat,
the toasts service got two new methods\r\n`dismissAllToastsWithChecks`
and
`assertToastCount`.","sha":"dd1fd2647a453fe9ad233d3afc9848b507c945da","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","backport:prev-minor","v8.8.0","v8.9.0"],"number":156586,"url":"https://github.com/elastic/kibana/pull/156586","mergeCommit":{"message":"[ML]
Functional tests - stabilize export job tests (#156586)\n\nThis PR
stabilizes the export job tests by making sure the export\r\nsuccess
toast is closed before moving on to the next test. As part of\r\nthat,
the toasts service got two new methods\r\n`dismissAllToastsWithChecks`
and
`assertToastCount`.","sha":"dd1fd2647a453fe9ad233d3afc9848b507c945da"}},"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/156586","number":156586,"mergeCommit":{"message":"[ML]
Functional tests - stabilize export job tests (#156586)\n\nThis PR
stabilizes the export job tests by making sure the export\r\nsuccess
toast is closed before moving on to the next test. As part of\r\nthat,
the toasts service got two new methods\r\n`dismissAllToastsWithChecks`
and
`assertToastCount`.","sha":"dd1fd2647a453fe9ad233d3afc9848b507c945da"}}]}]
BACKPORT-->

Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
 2023-05-05 02:31:23 -07:00
Kibana Machine
e76daa4135
[8.8] [RAM][Maintenance Window][8.8]Fix window maintenance workflow (#156427) (#156770) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[RAM][Maintenance Window][8.8]Fix window maintenance workflow
(#156427)](https://github.com/elastic/kibana/pull/156427)

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

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

<!--BACKPORT [{"author":{"name":"Jiawei
Wu","email":"74562234+JiaweiWu@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-05T00:11:26Z","message":"[RAM][Maintenance
Window][8.8]Fix window maintenance workflow (#156427)\n\n##
Summary\r\n\r\nThe way that we canceled every notification for our alert
life cycle\r\nduring an active maintenance window was not close enough
to what our\r\ncustomers were expecting. For our persisted security
solution alerts, we\r\ndid not have to change the logic because it will
always be a new alert.\r\nTherefore, @shanisagiv1, @mdefazio, @JiaweiWu,
and @XavierM had a\r\ndiscussion about this problem and we decided
this:\r\n\r\nTo summarize, we will only keep the notification during a
maintenance\r\nwindow if an alert has been created/active outside of
window\r\nmaintenance. We created three different scenarios to explain
the new\r\nlogic and we will make the assumption that our alert has an
action per\r\nstatus change. For you to understand the different
scenarios, I created\r\nthis legend below:\r\n<img width=\"223\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236045974-f4fa379b-db5e-41f8-91a8-2689b9f24dab.png\">\r\n\r\n###
Scenario I\r\nIf an alert is active/created before a maintenance window
and recovered\r\ninside of the maintenance window then we will send
notifications\r\n<img width=\"463\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236046473-d04df836-d3e6-42d8-97be-8b4f1544cc1a.png\">\r\n\r\n###
Scenario II\r\nIf an alert is active/created and recovered inside of
window maintenance\r\nthen we will NOT send notifications\r\n<img
width=\"407\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236046913-c2f77131-9ff1-4864-9dab-89c4c429152e.png\">\r\n\r\n###
Scenario III\r\nif an alert is active/created in a maintenance window
and recovered\r\noutside of the maintenance window then we will not send
notifications\r\n<img width=\"496\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236047613-e63efe52-87fa-419e-9e0e-965b1d10ae18.png\">\r\n\r\n\r\n###
Checklist\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---------\r\n\r\nCo-authored-by: Xavier Mouligneau
<xavier.mouligneau@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ea407983bbd6a364f23f6780ff1049f679f53488","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","backport","release_note:skip","Team:ResponseOps","Feature:Alerting/RulesManagement","v8.8.0","v8.9.0"],"number":156427,"url":"https://github.com/elastic/kibana/pull/156427","mergeCommit":{"message":"[RAM][Maintenance
Window][8.8]Fix window maintenance workflow (#156427)\n\n##
Summary\r\n\r\nThe way that we canceled every notification for our alert
life cycle\r\nduring an active maintenance window was not close enough
to what our\r\ncustomers were expecting. For our persisted security
solution alerts, we\r\ndid not have to change the logic because it will
always be a new alert.\r\nTherefore, @shanisagiv1, @mdefazio, @JiaweiWu,
and @XavierM had a\r\ndiscussion about this problem and we decided
this:\r\n\r\nTo summarize, we will only keep the notification during a
maintenance\r\nwindow if an alert has been created/active outside of
window\r\nmaintenance. We created three different scenarios to explain
the new\r\nlogic and we will make the assumption that our alert has an
action per\r\nstatus change. For you to understand the different
scenarios, I created\r\nthis legend below:\r\n<img width=\"223\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236045974-f4fa379b-db5e-41f8-91a8-2689b9f24dab.png\">\r\n\r\n###
Scenario I\r\nIf an alert is active/created before a maintenance window
and recovered\r\ninside of the maintenance window then we will send
notifications\r\n<img width=\"463\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236046473-d04df836-d3e6-42d8-97be-8b4f1544cc1a.png\">\r\n\r\n###
Scenario II\r\nIf an alert is active/created and recovered inside of
window maintenance\r\nthen we will NOT send notifications\r\n<img
width=\"407\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236046913-c2f77131-9ff1-4864-9dab-89c4c429152e.png\">\r\n\r\n###
Scenario III\r\nif an alert is active/created in a maintenance window
and recovered\r\noutside of the maintenance window then we will not send
notifications\r\n<img width=\"496\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236047613-e63efe52-87fa-419e-9e0e-965b1d10ae18.png\">\r\n\r\n\r\n###
Checklist\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---------\r\n\r\nCo-authored-by: Xavier Mouligneau
<xavier.mouligneau@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ea407983bbd6a364f23f6780ff1049f679f53488"}},"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/156427","number":156427,"mergeCommit":{"message":"[RAM][Maintenance
Window][8.8]Fix window maintenance workflow (#156427)\n\n##
Summary\r\n\r\nThe way that we canceled every notification for our alert
life cycle\r\nduring an active maintenance window was not close enough
to what our\r\ncustomers were expecting. For our persisted security
solution alerts, we\r\ndid not have to change the logic because it will
always be a new alert.\r\nTherefore, @shanisagiv1, @mdefazio, @JiaweiWu,
and @XavierM had a\r\ndiscussion about this problem and we decided
this:\r\n\r\nTo summarize, we will only keep the notification during a
maintenance\r\nwindow if an alert has been created/active outside of
window\r\nmaintenance. We created three different scenarios to explain
the new\r\nlogic and we will make the assumption that our alert has an
action per\r\nstatus change. For you to understand the different
scenarios, I created\r\nthis legend below:\r\n<img width=\"223\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236045974-f4fa379b-db5e-41f8-91a8-2689b9f24dab.png\">\r\n\r\n###
Scenario I\r\nIf an alert is active/created before a maintenance window
and recovered\r\ninside of the maintenance window then we will send
notifications\r\n<img width=\"463\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236046473-d04df836-d3e6-42d8-97be-8b4f1544cc1a.png\">\r\n\r\n###
Scenario II\r\nIf an alert is active/created and recovered inside of
window maintenance\r\nthen we will NOT send notifications\r\n<img
width=\"407\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236046913-c2f77131-9ff1-4864-9dab-89c4c429152e.png\">\r\n\r\n###
Scenario III\r\nif an alert is active/created in a maintenance window
and recovered\r\noutside of the maintenance window then we will not send
notifications\r\n<img width=\"496\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/236047613-e63efe52-87fa-419e-9e0e-965b1d10ae18.png\">\r\n\r\n\r\n###
Checklist\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---------\r\n\r\nCo-authored-by: Xavier Mouligneau
<xavier.mouligneau@elastic.co>\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"ea407983bbd6a364f23f6780ff1049f679f53488"}}]}]
BACKPORT-->

Co-authored-by: Jiawei Wu <74562234+JiaweiWu@users.noreply.github.com>
 2023-05-04 19:12:46 -07:00
Kibana Machine
d802d4fba9
[8.8] [DOCS] Case file attachments (#156459) (#156765) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[DOCS] Case file attachments
(#156459)](https://github.com/elastic/kibana/pull/156459)

<!--- 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-04T23:27:47Z","message":"[DOCS]
Case file attachments
(#156459)","sha":"a83ab21783dcf0ea9c9176b6476d609ddb28108f","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:ResponseOps","docs","Feature:Cases","backport:prev-minor","v8.8.0","v8.9.0"],"number":156459,"url":"https://github.com/elastic/kibana/pull/156459","mergeCommit":{"message":"[DOCS]
Case file attachments
(#156459)","sha":"a83ab21783dcf0ea9c9176b6476d609ddb28108f"}},"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/156459","number":156459,"mergeCommit":{"message":"[DOCS]
Case file attachments
(#156459)","sha":"a83ab21783dcf0ea9c9176b6476d609ddb28108f"}}]}]
BACKPORT-->

Co-authored-by: Lisa Cawley <lcawley@elastic.co>
 2023-05-04 19:04:18 -07:00
Kibana Machine
67699a987e
[8.8] [Security Solution] Add a migration to unmute custom Security Solution rules (#156593) (#156728) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution] Add a migration to unmute custom Security
Solution rules (#156593)](https://github.com/elastic/kibana/pull/156593)

<!--- 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-04T19:11:35Z","message":"[Security
Solution] Add a migration to unmute custom Security Solution rules
(#156593)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/156352\r\n\r\n##
Summary\r\n\r\nThis PR adds a migration to unmute all Security
Solution's custom rules while migrating to Kibana `8.8`. As we added
support for rule snoozing in `8.8`
https://github.com/elastic/security-team/issues/5308 users are able to
manage muting of rule notifications. Prior `8.8` Security Solution's
custom rules were muted under the hood if there is no
actions.","sha":"fc107d0e5b36e7bc49f4230f2a85d50d16050323","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Detections
and Resp","Team: SecuritySolution","Team:Detection
Rules","backport:prev-minor","v8.8.0","v8.9.0"],"number":156593,"url":"https://github.com/elastic/kibana/pull/156593","mergeCommit":{"message":"[Security
Solution] Add a migration to unmute custom Security Solution rules
(#156593)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/156352\r\n\r\n##
Summary\r\n\r\nThis PR adds a migration to unmute all Security
Solution's custom rules while migrating to Kibana `8.8`. As we added
support for rule snoozing in `8.8`
https://github.com/elastic/security-team/issues/5308 users are able to
manage muting of rule notifications. Prior `8.8` Security Solution's
custom rules were muted under the hood if there is no
actions.","sha":"fc107d0e5b36e7bc49f4230f2a85d50d16050323"}},"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/156593","number":156593,"mergeCommit":{"message":"[Security
Solution] Add a migration to unmute custom Security Solution rules
(#156593)\n\n**Addresses:**
https://github.com/elastic/kibana/issues/156352\r\n\r\n##
Summary\r\n\r\nThis PR adds a migration to unmute all Security
Solution's custom rules while migrating to Kibana `8.8`. As we added
support for rule snoozing in `8.8`
https://github.com/elastic/security-team/issues/5308 users are able to
manage muting of rule notifications. Prior `8.8` Security Solution's
custom rules were muted under the hood if there is no
actions.","sha":"fc107d0e5b36e7bc49f4230f2a85d50d16050323"}}]}]
BACKPORT-->

Co-authored-by: Maxim Palenov <maxim.palenov@elastic.co>
 2023-05-04 14:25:44 -07:00
Rodney Norris
c6a65ad0f0
[8.8][Backport][Enterprise Search] Move Search Applications to Applications module (#156725) 
## Summary

Backport of #155805
 2023-05-04 12:36:22 -07:00
Tiago Costa
b8904f0332
skip flaky suite (#156151) 2023-05-04 18:16:51 +01:00
Tiago Costa
35b33012bb
skip flaky suite (#156088) 2023-05-04 15:58:32 +01:00
Kibana Machine
a8000223c1
[8.8] [Security Solution] [Fix] Leading Action column width: session viewer not visible (#156521) (#156679) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Security Solution] [Fix] Leading Action column width: session viewer
not visible (#156521)](https://github.com/elastic/kibana/pull/156521)

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

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

<!--BACKPORT [{"author":{"name":"Jatin
Kathuria","email":"jatin.kathuria@elastic.co"},"sourceCommit":{"committedDate":"2023-05-04T12:08:58Z","message":"[Security
Solution] [Fix] Leading Action column width: session viewer not visible
(#156521)\n\n## Summary\r\n\r\nThis PR handles #156450. below tasks has
been carried out in this PR\r\n\r\n- Modified resolver generator script
to add process ancestry (\r\n`process.entry_leader.start` was
missing)\r\n- Added cypress test to make sure buttons are visible. \r\n-
Added a new dummy minimal dataset called `process_ancestry`
which\r\nenabled analyzer and session viewer buttons.\r\n- Width is
being calculated automatically. Please see below video for\r\nthe
demo.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7485038/235917406-8d77f0c9-7c44-4c29-a79a-90b99f117e0d.mov\r\n\r\n
\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [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":"6a85012951139ac9353fad63a24b1c43e4c7aabf","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Threat
Hunting:Investigations","v8.8.0","v8.9.0"],"number":156521,"url":"https://github.com/elastic/kibana/pull/156521","mergeCommit":{"message":"[Security
Solution] [Fix] Leading Action column width: session viewer not visible
(#156521)\n\n## Summary\r\n\r\nThis PR handles #156450. below tasks has
been carried out in this PR\r\n\r\n- Modified resolver generator script
to add process ancestry (\r\n`process.entry_leader.start` was
missing)\r\n- Added cypress test to make sure buttons are visible. \r\n-
Added a new dummy minimal dataset called `process_ancestry`
which\r\nenabled analyzer and session viewer buttons.\r\n- Width is
being calculated automatically. Please see below video for\r\nthe
demo.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7485038/235917406-8d77f0c9-7c44-4c29-a79a-90b99f117e0d.mov\r\n\r\n
\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [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":"6a85012951139ac9353fad63a24b1c43e4c7aabf"}},"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/156521","number":156521,"mergeCommit":{"message":"[Security
Solution] [Fix] Leading Action column width: session viewer not visible
(#156521)\n\n## Summary\r\n\r\nThis PR handles #156450. below tasks has
been carried out in this PR\r\n\r\n- Modified resolver generator script
to add process ancestry (\r\n`process.entry_leader.start` was
missing)\r\n- Added cypress test to make sure buttons are visible. \r\n-
Added a new dummy minimal dataset called `process_ancestry`
which\r\nenabled analyzer and session viewer buttons.\r\n- Width is
being calculated automatically. Please see below video for\r\nthe
demo.\r\n\r\n\r\nhttps://user-images.githubusercontent.com/7485038/235917406-8d77f0c9-7c44-4c29-a79a-90b99f117e0d.mov\r\n\r\n
\r\n\r\n\r\n### Checklist\r\n\r\nDelete any items that are not
applicable to this PR.\r\n\r\n- [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":"6a85012951139ac9353fad63a24b1c43e4c7aabf"}}]}]
BACKPORT-->

Co-authored-by: Jatin Kathuria <jatin.kathuria@elastic.co>
 2023-05-04 06:55:10 -07:00
Kibana Machine
177ef155b4
[8.8] [ML] Add functional testing for continuous transforms (creation, start, stop, reset) (#156128) (#156598) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ML] Add functional testing for continuous transforms (creation,
start, stop, reset)
(#156128)](https://github.com/elastic/kibana/pull/156128)

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

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

<!--BACKPORT [{"author":{"name":"Quynh Nguyen
(Quinn)","email":"43350163+qn895@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-03T17:36:38Z","message":"[ML]
Add functional testing for continuous transforms (creation, start, stop,
reset) (#156128)\n\n## Summary\r\n\r\nPart of
https://github.com/elastic/kibana/issues/152009. This PR
adds\r\nfunctional test for continuous transforms related actions
including\r\ncreation, start, stop, and reset. It also stablizes tests
skipped
in\r\nhttps://github.com/elastic/kibana/issues/151889.\r\n\r\nStarted
[flaky test suite runner for
continuous\r\ntransform](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2185)...\r\n\r\nStarted
[flaky test suite runner for creation index pattern
(previously\r\nskipped)](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2187)...\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- [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- [ ] 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:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f61546629dc787c320582ff9b26777c493d0459d","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","test_ui_functional","release_note:skip","v8.8.0","v8.9.0"],"number":156128,"url":"https://github.com/elastic/kibana/pull/156128","mergeCommit":{"message":"[ML]
Add functional testing for continuous transforms (creation, start, stop,
reset) (#156128)\n\n## Summary\r\n\r\nPart of
https://github.com/elastic/kibana/issues/152009. This PR
adds\r\nfunctional test for continuous transforms related actions
including\r\ncreation, start, stop, and reset. It also stablizes tests
skipped
in\r\nhttps://github.com/elastic/kibana/issues/151889.\r\n\r\nStarted
[flaky test suite runner for
continuous\r\ntransform](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2185)...\r\n\r\nStarted
[flaky test suite runner for creation index pattern
(previously\r\nskipped)](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2187)...\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- [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- [ ] 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:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f61546629dc787c320582ff9b26777c493d0459d"}},"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/156128","number":156128,"mergeCommit":{"message":"[ML]
Add functional testing for continuous transforms (creation, start, stop,
reset) (#156128)\n\n## Summary\r\n\r\nPart of
https://github.com/elastic/kibana/issues/152009. This PR
adds\r\nfunctional test for continuous transforms related actions
including\r\ncreation, start, stop, and reset. It also stablizes tests
skipped
in\r\nhttps://github.com/elastic/kibana/issues/151889.\r\n\r\nStarted
[flaky test suite runner for
continuous\r\ntransform](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2185)...\r\n\r\nStarted
[flaky test suite runner for creation index pattern
(previously\r\nskipped)](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2187)...\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- [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- [ ] 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:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"f61546629dc787c320582ff9b26777c493d0459d"}}]}]
BACKPORT-->

Co-authored-by: Quynh Nguyen (Quinn) <43350163+qn895@users.noreply.github.com>
 2023-05-03 11:55:45 -07:00
Kibana Machine
b64f2f2d0b
[8.8] [APM] Check if metric fields exist (#145348) (#156006) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[APM] Check if metric fields exist
(#145348)](https://github.com/elastic/kibana/pull/145348)

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

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

<!--BACKPORT [{"author":{"name":"Katerina
Patticha","email":"aikaterini.patticha@elastic.co"},"sourceCommit":{"committedDate":"2023-04-27T12:55:14Z","message":"[APM]
Check if metric fields exist (#145348)\n\nFixes the error
\r\n```\r\n\"script_stack\": [\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues.throwIfEmpty(ScriptDocValues.java:92)\",\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.get(ScriptDocValues.java:110)\",\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.getValue(ScriptDocValues.java:105)\",\r\n
\"\"\"total = useCgroupLimit ? doc[limitKey].value :
doc['system.memory.total'].value;\r\n\r\n double \"\"\",\r\n \" ^----
HERE\"\r\n\r\n\r\n```\r\n\r\nconnected
https://github.com/elastic/sdh-apm/issues/765
(internal)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Søren Louv-Jansen
<sorenlouv@gmail.com>","sha":"98165d26846367b98a259f76b664545a43d2434b","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","Team:APM","backport:prev-minor","v8.8.0","v8.7.1","v8.9.0"],"number":145348,"url":"https://github.com/elastic/kibana/pull/145348","mergeCommit":{"message":"[APM]
Check if metric fields exist (#145348)\n\nFixes the error
\r\n```\r\n\"script_stack\": [\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues.throwIfEmpty(ScriptDocValues.java:92)\",\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.get(ScriptDocValues.java:110)\",\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.getValue(ScriptDocValues.java:105)\",\r\n
\"\"\"total = useCgroupLimit ? doc[limitKey].value :
doc['system.memory.total'].value;\r\n\r\n double \"\"\",\r\n \" ^----
HERE\"\r\n\r\n\r\n```\r\n\r\nconnected
https://github.com/elastic/sdh-apm/issues/765
(internal)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Søren Louv-Jansen
<sorenlouv@gmail.com>","sha":"98165d26846367b98a259f76b664545a43d2434b"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.7"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.7","label":"v8.7.1","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/145348","number":145348,"mergeCommit":{"message":"[APM]
Check if metric fields exist (#145348)\n\nFixes the error
\r\n```\r\n\"script_stack\": [\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues.throwIfEmpty(ScriptDocValues.java:92)\",\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.get(ScriptDocValues.java:110)\",\r\n
\"org.elasticsearch.server@8.5.0-SNAPSHOT/org.elasticsearch.index.fielddata.ScriptDocValues$Longs.getValue(ScriptDocValues.java:105)\",\r\n
\"\"\"total = useCgroupLimit ? doc[limitKey].value :
doc['system.memory.total'].value;\r\n\r\n double \"\"\",\r\n \" ^----
HERE\"\r\n\r\n\r\n```\r\n\r\nconnected
https://github.com/elastic/sdh-apm/issues/765
(internal)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>\r\nCo-authored-by:
Søren Louv-Jansen
<sorenlouv@gmail.com>","sha":"98165d26846367b98a259f76b664545a43d2434b"}}]}]
BACKPORT-->

Co-authored-by: Katerina Patticha <aikaterini.patticha@elastic.co>
 2023-05-03 10:17:11 -07:00
Kibana Machine
a5921f0203
[8.8] [Guided onboarding] Fix the missing help link (#156399) (#156550) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Guided onboarding] Fix the missing help link
(#156399)](https://github.com/elastic/kibana/pull/156399)

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

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

<!--BACKPORT [{"author":{"name":"Yulia
Čech","email":"6585477+yuliacech@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-03T14:00:09Z","message":"[Guided
onboarding] Fix the missing help link (#156399)\n\n##
Summary\r\n\r\nThis PR fixes a bug introduced
in\r\nhttps://github.com/elastic/kibana/pull/155065/ that I noticed
when\r\ntesting guided onboarding for v8.9.0: the help link was missing
from the\r\nhelp menu. I added a functional test for the help link but
we also need\r\na test that the link is hidden when the user doesn't
have access to\r\nguided onboarding (opened an issue for
that\r\n[here](https://github.com/elastic/kibana/issues/156410)).\r\n\r\n###
How to test\r\n1. Add xpack.cloud.id: 'testID' to
/config/kibana.dev.yml\r\n2. Start ES with yarn es snapshot and Kibana
with `yarn start``\r\n3. Check that the help link \"Setup guides\" is
displayed in the help menu\r\n\r\n### Screenshot \r\n<img width=\"336\"
alt=\"Screenshot 2023-05-02 at 17 27
20\"\r\nsrc=\"https://user-images.githubusercontent.com/6585477/235712599-812b422d-3092-45b3-a726-37f6b90e81c1.png\">","sha":"d00e2a366f872d80b5cd598765f8a5aee50cc399","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Journey/Onboarding","v8.8.0","v8.9.0"],"number":156399,"url":"https://github.com/elastic/kibana/pull/156399","mergeCommit":{"message":"[Guided
onboarding] Fix the missing help link (#156399)\n\n##
Summary\r\n\r\nThis PR fixes a bug introduced
in\r\nhttps://github.com/elastic/kibana/pull/155065/ that I noticed
when\r\ntesting guided onboarding for v8.9.0: the help link was missing
from the\r\nhelp menu. I added a functional test for the help link but
we also need\r\na test that the link is hidden when the user doesn't
have access to\r\nguided onboarding (opened an issue for
that\r\n[here](https://github.com/elastic/kibana/issues/156410)).\r\n\r\n###
How to test\r\n1. Add xpack.cloud.id: 'testID' to
/config/kibana.dev.yml\r\n2. Start ES with yarn es snapshot and Kibana
with `yarn start``\r\n3. Check that the help link \"Setup guides\" is
displayed in the help menu\r\n\r\n### Screenshot \r\n<img width=\"336\"
alt=\"Screenshot 2023-05-02 at 17 27
20\"\r\nsrc=\"https://user-images.githubusercontent.com/6585477/235712599-812b422d-3092-45b3-a726-37f6b90e81c1.png\">","sha":"d00e2a366f872d80b5cd598765f8a5aee50cc399"}},"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/156399","number":156399,"mergeCommit":{"message":"[Guided
onboarding] Fix the missing help link (#156399)\n\n##
Summary\r\n\r\nThis PR fixes a bug introduced
in\r\nhttps://github.com/elastic/kibana/pull/155065/ that I noticed
when\r\ntesting guided onboarding for v8.9.0: the help link was missing
from the\r\nhelp menu. I added a functional test for the help link but
we also need\r\na test that the link is hidden when the user doesn't
have access to\r\nguided onboarding (opened an issue for
that\r\n[here](https://github.com/elastic/kibana/issues/156410)).\r\n\r\n###
How to test\r\n1. Add xpack.cloud.id: 'testID' to
/config/kibana.dev.yml\r\n2. Start ES with yarn es snapshot and Kibana
with `yarn start``\r\n3. Check that the help link \"Setup guides\" is
displayed in the help menu\r\n\r\n### Screenshot \r\n<img width=\"336\"
alt=\"Screenshot 2023-05-02 at 17 27
20\"\r\nsrc=\"https://user-images.githubusercontent.com/6585477/235712599-812b422d-3092-45b3-a726-37f6b90e81c1.png\">","sha":"d00e2a366f872d80b5cd598765f8a5aee50cc399"}}]}]
BACKPORT-->

Co-authored-by: Yulia Čech <6585477+yuliacech@users.noreply.github.com>
 2023-05-03 08:38:31 -07:00
Kibana Machine
d61043fdfa
[8.8] [functional tests] split fleet_api_integration config into smaller ones (#156407) (#156559) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[functional tests] split fleet_api_integration config into smaller
ones (#156407)](https://github.com/elastic/kibana/pull/156407)

<!--- 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-03T14:26:58Z","message":"[functional
tests] split fleet_api_integration config into smaller ones
(#156407)\n\n## Summary\r\n\r\nRuntime for
`fleet_api_integration/config` crossed the 38 min limit.\r\nIdeally
config runtime should be <10 min so that pipeline can quickly\r\nretry
failed configs (we do 1 retry on CI)\r\n\r\n<img width=\"1600\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/10977896/235707744-3120e1e9-4882-493f-9ee0-86016a765401.png\">\r\n\r\n\r\nThis
PR splits the existing config into few smaller
ones:\r\n\r\n```\r\nx-pack/test/fleet_api_integration/config.agent.ts
15m 15s\r\nx-pack/test/fleet_api_integration/config.agent_policy.ts 4m
10s\r\nx-pack/test/fleet_api_integration/config.epm.ts 8m
12s\r\nx-pack/test/fleet_api_integration/config.package_policy.ts 10m
54s\r\n// combines multiple test
files\r\nx-pack/test/fleet_api_integration/config.fleet.ts 5m
2s\r\n```","sha":"1c777a2e702f7c5ae9c1b86063515c0a27368efb","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v8.8.0","v8.7.2","v8.9.0"],"number":156407,"url":"https://github.com/elastic/kibana/pull/156407","mergeCommit":{"message":"[functional
tests] split fleet_api_integration config into smaller ones
(#156407)\n\n## Summary\r\n\r\nRuntime for
`fleet_api_integration/config` crossed the 38 min limit.\r\nIdeally
config runtime should be <10 min so that pipeline can quickly\r\nretry
failed configs (we do 1 retry on CI)\r\n\r\n<img width=\"1600\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/10977896/235707744-3120e1e9-4882-493f-9ee0-86016a765401.png\">\r\n\r\n\r\nThis
PR splits the existing config into few smaller
ones:\r\n\r\n```\r\nx-pack/test/fleet_api_integration/config.agent.ts
15m 15s\r\nx-pack/test/fleet_api_integration/config.agent_policy.ts 4m
10s\r\nx-pack/test/fleet_api_integration/config.epm.ts 8m
12s\r\nx-pack/test/fleet_api_integration/config.package_policy.ts 10m
54s\r\n// combines multiple test
files\r\nx-pack/test/fleet_api_integration/config.fleet.ts 5m
2s\r\n```","sha":"1c777a2e702f7c5ae9c1b86063515c0a27368efb"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.7"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","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/156407","number":156407,"mergeCommit":{"message":"[functional
tests] split fleet_api_integration config into smaller ones
(#156407)\n\n## Summary\r\n\r\nRuntime for
`fleet_api_integration/config` crossed the 38 min limit.\r\nIdeally
config runtime should be <10 min so that pipeline can quickly\r\nretry
failed configs (we do 1 retry on CI)\r\n\r\n<img width=\"1600\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/10977896/235707744-3120e1e9-4882-493f-9ee0-86016a765401.png\">\r\n\r\n\r\nThis
PR splits the existing config into few smaller
ones:\r\n\r\n```\r\nx-pack/test/fleet_api_integration/config.agent.ts
15m 15s\r\nx-pack/test/fleet_api_integration/config.agent_policy.ts 4m
10s\r\nx-pack/test/fleet_api_integration/config.epm.ts 8m
12s\r\nx-pack/test/fleet_api_integration/config.package_policy.ts 10m
54s\r\n// combines multiple test
files\r\nx-pack/test/fleet_api_integration/config.fleet.ts 5m
2s\r\n```","sha":"1c777a2e702f7c5ae9c1b86063515c0a27368efb"}}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2023-05-03 08:33:03 -07:00
Kibana Machine
b12b81230d
[8.8] [Defend Workflows][Bug] Case flyout z-index (#153219) (#156505) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Defend Workflows][Bug] Case flyout z-index
(#153219)](https://github.com/elastic/kibana/pull/153219)

<!--- 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-03T10:30:13Z","message":"[Defend
Workflows][Bug] Case flyout z-index (#153219)\n\nFixes
https://github.com/elastic/security-team/issues/6228\r\n\r\n5000
`z-index` set in `create-case-flyout-mask-overlay` is
being\r\noverwritten by `euiOverlayMask-belowHeader` with a value of
1000. This\r\ncauses **Case flyout** to be under the already opened
**Osquery flyout**\r\n\r\nThis PR includes cleanup in flyouts renders -
we removed unnecessary\r\n`maskProps` as well as z-indexes that were
explicitly set even though\r\nflyout component manages them
itself.\r\n\r\n\r\n![test](https://user-images.githubusercontent.com/29123534/225292177-a08d3fb8-aad3-487b-a054-6cde6aec94d7.gif)\r\n\r\n---------\r\n\r\nCo-authored-by:
Tomasz Ciecierski <ciecierskitomek@gmail.com>\r\nCo-authored-by: Tomasz
Ciecierski <tomasz.ciecierski@elastic.co>\r\nCo-authored-by: Patryk
Kopyciński <contact@patrykkopycinski.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d8fe39c18d9df7acb00a82515f5a41a6e4111c59","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:Defend
Workflows","Feature:Osquery","ci:all-cypress-suites","v8.8.0","ci:skip-cypress-osquery","v8.9.0"],"number":153219,"url":"https://github.com/elastic/kibana/pull/153219","mergeCommit":{"message":"[Defend
Workflows][Bug] Case flyout z-index (#153219)\n\nFixes
https://github.com/elastic/security-team/issues/6228\r\n\r\n5000
`z-index` set in `create-case-flyout-mask-overlay` is
being\r\noverwritten by `euiOverlayMask-belowHeader` with a value of
1000. This\r\ncauses **Case flyout** to be under the already opened
**Osquery flyout**\r\n\r\nThis PR includes cleanup in flyouts renders -
we removed unnecessary\r\n`maskProps` as well as z-indexes that were
explicitly set even though\r\nflyout component manages them
itself.\r\n\r\n\r\n![test](https://user-images.githubusercontent.com/29123534/225292177-a08d3fb8-aad3-487b-a054-6cde6aec94d7.gif)\r\n\r\n---------\r\n\r\nCo-authored-by:
Tomasz Ciecierski <ciecierskitomek@gmail.com>\r\nCo-authored-by: Tomasz
Ciecierski <tomasz.ciecierski@elastic.co>\r\nCo-authored-by: Patryk
Kopyciński <contact@patrykkopycinski.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d8fe39c18d9df7acb00a82515f5a41a6e4111c59"}},"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/153219","number":153219,"mergeCommit":{"message":"[Defend
Workflows][Bug] Case flyout z-index (#153219)\n\nFixes
https://github.com/elastic/security-team/issues/6228\r\n\r\n5000
`z-index` set in `create-case-flyout-mask-overlay` is
being\r\noverwritten by `euiOverlayMask-belowHeader` with a value of
1000. This\r\ncauses **Case flyout** to be under the already opened
**Osquery flyout**\r\n\r\nThis PR includes cleanup in flyouts renders -
we removed unnecessary\r\n`maskProps` as well as z-indexes that were
explicitly set even though\r\nflyout component manages them
itself.\r\n\r\n\r\n![test](https://user-images.githubusercontent.com/29123534/225292177-a08d3fb8-aad3-487b-a054-6cde6aec94d7.gif)\r\n\r\n---------\r\n\r\nCo-authored-by:
Tomasz Ciecierski <ciecierskitomek@gmail.com>\r\nCo-authored-by: Tomasz
Ciecierski <tomasz.ciecierski@elastic.co>\r\nCo-authored-by: Patryk
Kopyciński <contact@patrykkopycinski.com>\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d8fe39c18d9df7acb00a82515f5a41a6e4111c59"}}]}]
BACKPORT-->

Co-authored-by: Konrad Szwarc <konrad.szwarc@elastic.co>
 2023-05-03 08:31:46 -07:00
Kibana Machine
df0d0976c2
[8.8] [Lens] Fix field formatters functional tests (#156190) (#156554) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Lens] Fix field formatters functional tests
(#156190)](https://github.com/elastic/kibana/pull/156190)

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

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

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-03T14:06:49Z","message":"[Lens]
Fix field formatters functional tests (#156190)\n\n##
Summary\r\n\r\nFixes #155884 , #156463, #156463\r\n\r\nThis PR make sure
the field editor panel is closed after save before\r\nproceeding with
other steps.\r\nThe main problem here was that the tests were not
failing if the\r\nexecution was too fast and the panel was still open on
test end, so the\r\ncleanup process will fail as would expect the panel
to be closed, and\r\ncannot find the right elements to
click.\r\n\r\n\r\nFlaky runner 50 (✅
):\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2213\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":"91c1ff15d384a10d29cfe0a736f0eca8e7a6dc7f","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Visualizations","release_note:skip","Feature:Lens","backport:prev-minor","v8.9.0"],"number":156190,"url":"https://github.com/elastic/kibana/pull/156190","mergeCommit":{"message":"[Lens]
Fix field formatters functional tests (#156190)\n\n##
Summary\r\n\r\nFixes #155884 , #156463, #156463\r\n\r\nThis PR make sure
the field editor panel is closed after save before\r\nproceeding with
other steps.\r\nThe main problem here was that the tests were not
failing if the\r\nexecution was too fast and the panel was still open on
test end, so the\r\ncleanup process will fail as would expect the panel
to be closed, and\r\ncannot find the right elements to
click.\r\n\r\n\r\nFlaky runner 50 (✅
):\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2213\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":"91c1ff15d384a10d29cfe0a736f0eca8e7a6dc7f"}},"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/156190","number":156190,"mergeCommit":{"message":"[Lens]
Fix field formatters functional tests (#156190)\n\n##
Summary\r\n\r\nFixes #155884 , #156463, #156463\r\n\r\nThis PR make sure
the field editor panel is closed after save before\r\nproceeding with
other steps.\r\nThe main problem here was that the tests were not
failing if the\r\nexecution was too fast and the panel was still open on
test end, so the\r\ncleanup process will fail as would expect the panel
to be closed, and\r\ncannot find the right elements to
click.\r\n\r\n\r\nFlaky runner 50 (✅
):\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2213\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":"91c1ff15d384a10d29cfe0a736f0eca8e7a6dc7f"}}]}]
BACKPORT-->

Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
 2023-05-03 08:10:25 -07:00
Kibana Machine
cdd9cb4ea5
[8.8] [Lens] Enabled tsdb counter fields for last_value (#156183) (#156487) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Lens] Enabled tsdb counter fields for last_value
(#156183)](https://github.com/elastic/kibana/pull/156183)

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

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

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-03T09:05:06Z","message":"[Lens]
Enabled tsdb counter fields for last_value (#156183)\n\n##
Summary\r\n\r\nFixes #156168 \r\n\r\nEnables the `last_value` operation
for TSDB `counter` field types.\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":"36c31f5c3f3face5417c044fbc3238f9a42b24a0","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:Visualizations","Feature:Lens","backport:prev-minor","v8.8.0","v8.9.0"],"number":156183,"url":"https://github.com/elastic/kibana/pull/156183","mergeCommit":{"message":"[Lens]
Enabled tsdb counter fields for last_value (#156183)\n\n##
Summary\r\n\r\nFixes #156168 \r\n\r\nEnables the `last_value` operation
for TSDB `counter` field types.\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":"36c31f5c3f3face5417c044fbc3238f9a42b24a0"}},"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/156183","number":156183,"mergeCommit":{"message":"[Lens]
Enabled tsdb counter fields for last_value (#156183)\n\n##
Summary\r\n\r\nFixes #156168 \r\n\r\nEnables the `last_value` operation
for TSDB `counter` field types.\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":"36c31f5c3f3face5417c044fbc3238f9a42b24a0"}}]}]
BACKPORT-->

Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
 2023-05-03 03:10:11 -07:00
Kibana Machine
3e9f8c7026
[8.8] [ML] Functional tests - stabilize and re-enable export jobs tests (#152334) (#156480) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[ML] Functional tests - stabilize and re-enable export jobs tests
(#152334)](https://github.com/elastic/kibana/pull/152334)

<!--- 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-03T08:19:44Z","message":"[ML]
Functional tests - stabilize and re-enable export jobs tests
(#152334)\n\nThis PR re-enables the export job tests and the reporting
download tests\r\nafter the underlying issues has been fixed by
switching to the new\r\nheadless browser
mode.","sha":"a90f4c24dac8d6d23105e1a5119c36634aa27f42","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":[":ml","release_note:skip","backport:prev-minor","v8.8.0","v8.9.0"],"number":152334,"url":"https://github.com/elastic/kibana/pull/152334","mergeCommit":{"message":"[ML]
Functional tests - stabilize and re-enable export jobs tests
(#152334)\n\nThis PR re-enables the export job tests and the reporting
download tests\r\nafter the underlying issues has been fixed by
switching to the new\r\nheadless browser
mode.","sha":"a90f4c24dac8d6d23105e1a5119c36634aa27f42"}},"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/152334","number":152334,"mergeCommit":{"message":"[ML]
Functional tests - stabilize and re-enable export jobs tests
(#152334)\n\nThis PR re-enables the export job tests and the reporting
download tests\r\nafter the underlying issues has been fixed by
switching to the new\r\nheadless browser
mode.","sha":"a90f4c24dac8d6d23105e1a5119c36634aa27f42"}}]}] BACKPORT-->

Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
 2023-05-03 02:32:11 -07:00
Kibana Machine
e86a6e1ff6
[8.8] [functional tests] split security and spaces ftr configs (#156350) (#156468) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[functional tests] split security and spaces ftr configs
(#156350)](https://github.com/elastic/kibana/pull/156350)

<!--- 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-03T06:57:57Z","message":"[functional
tests] split security and spaces ftr configs (#156350)\n\n##
Summary\r\n\r\nSplitting ftr configs to speed up ftr tests run on CI
\r\n\r\n```\r\nThe following \"Functional Tests\" configs have durations
that exceed the maximum amount of time desired for a single CI job.
\r\nThis is not an error, and if you don't own any of these configs then
you can ignore this warning.If you own any of these\r\nconfigs please
split them up ASAP and ask Operations if you have questions about how to
do
that.\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_basic.ts:
38.2
minutes\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_trial.ts:
38.2 minutes\r\n```\r\n\r\nAfter
split:\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_basic.ts\r\n20m
29s\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/copy_to_space_config_basic.ts\r\n20m
52s\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_trial.ts\r\n19m
57s\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/copy_to_space_config_trial.ts\r\n21m
5s\r\n\r\nRebalancing it with other configs should speedup CI by at
least
few\r\nminutes","sha":"424eae3f4d0f55f684a5b3c3b46847eb723233c9","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v8.8.0","v8.7.2","v8.9.0"],"number":156350,"url":"https://github.com/elastic/kibana/pull/156350","mergeCommit":{"message":"[functional
tests] split security and spaces ftr configs (#156350)\n\n##
Summary\r\n\r\nSplitting ftr configs to speed up ftr tests run on CI
\r\n\r\n```\r\nThe following \"Functional Tests\" configs have durations
that exceed the maximum amount of time desired for a single CI job.
\r\nThis is not an error, and if you don't own any of these configs then
you can ignore this warning.If you own any of these\r\nconfigs please
split them up ASAP and ask Operations if you have questions about how to
do
that.\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_basic.ts:
38.2
minutes\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_trial.ts:
38.2 minutes\r\n```\r\n\r\nAfter
split:\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_basic.ts\r\n20m
29s\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/copy_to_space_config_basic.ts\r\n20m
52s\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_trial.ts\r\n19m
57s\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/copy_to_space_config_trial.ts\r\n21m
5s\r\n\r\nRebalancing it with other configs should speedup CI by at
least
few\r\nminutes","sha":"424eae3f4d0f55f684a5b3c3b46847eb723233c9"}},"sourceBranch":"main","suggestedTargetBranches":["8.8","8.7"],"targetPullRequestStates":[{"branch":"8.8","label":"v8.8.0","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/156350","number":156350,"mergeCommit":{"message":"[functional
tests] split security and spaces ftr configs (#156350)\n\n##
Summary\r\n\r\nSplitting ftr configs to speed up ftr tests run on CI
\r\n\r\n```\r\nThe following \"Functional Tests\" configs have durations
that exceed the maximum amount of time desired for a single CI job.
\r\nThis is not an error, and if you don't own any of these configs then
you can ignore this warning.If you own any of these\r\nconfigs please
split them up ASAP and ask Operations if you have questions about how to
do
that.\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_basic.ts:
38.2
minutes\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_trial.ts:
38.2 minutes\r\n```\r\n\r\nAfter
split:\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_basic.ts\r\n20m
29s\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/copy_to_space_config_basic.ts\r\n20m
52s\r\nx-pack/test/spaces_api_integration/security_and_spaces/config_trial.ts\r\n19m
57s\r\n\r\nx-pack/test/spaces_api_integration/security_and_spaces/copy_to_space_config_trial.ts\r\n21m
5s\r\n\r\nRebalancing it with other configs should speedup CI by at
least
few\r\nminutes","sha":"424eae3f4d0f55f684a5b3c3b46847eb723233c9"}}]}]
BACKPORT-->

Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co>
 2023-05-03 01:08:29 -07:00
Kibana Machine
372d38fc1d
[8.8] [Synthetics] Adjust content (#156029) (#156451) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Synthetics] Adjust content
(#156029)](https://github.com/elastic/kibana/pull/156029)

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

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

<!--BACKPORT [{"author":{"name":"Dominique
Clarke","email":"dominique.clarke@elastic.co"},"sourceCommit":{"committedDate":"2023-05-02T21:23:04Z","message":"[Synthetics]
Adjust content (#156029)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/155936\r\nRelates to
https://github.com/elastic/kibana/issues/152915\r\nResolves
https://github.com/elastic/kibana/issues/150944\r\nResolves
https://github.com/elastic/kibana/issues/156166\r\n\r\nCopy
fixes:\r\n\r\n- Alerting config: Address
Typo\r\n(https://github.com/elastic/kibana/issues/152915#issuecomment-1516614675)\r\n-
Alerting config: Address success toast wording\r\n- Getting started
(\"Create your first monitor\") locations: Repeated text\r\nbetween
placeholder and hint text. To address this, I changed the\r\nhelptext to
give more detail\r\n- Private locations -> \"Monitors\" column: replaced
`Running` with\r\n`configured`\r\n- Overview page: Search bar
placeholder: `url` is now uppercase `URL`\r\n- Monitor status alert -
Updates text for viewer user to be consistent\r\nwith other
tooltips\r\n- Run once errors - Remove extra error toast \r\n- Run once
errors - Remove excess phrase from error\r\n- Sync errors - Made content
more user friendly\r\n- Synthetics App - replace references to Monitor
Management with\r\nSynthetics App\r\n- Enable/disable - clarify when
actions apply to all monitors\r\n- Project monitors - add reference to
enabling/disabling alerting on\r\nproject monitor page\r\n- Enablement -
Adjust content for less privileged users\r\n\r\nSome screenshots of the
fixes are below. These are not exhaustive\r\n<img width=\"1417\"
alt=\"Screen Shot 2023-04-25 at 12 12 38
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906460-529d48d4-f682-4d45-b439-7bd7189c37ea.png\">\r\n<img
width=\"772\" alt=\"Screen Shot 2023-04-25 at 12 12 31
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906462-b85d6fe0-2d32-42f0-81fb-2f528c5c0d87.png\">\r\n<img
width=\"909\" alt=\"Screen Shot 2023-04-25 at 12 12 10
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906466-49286af9-29c4-4bcb-9d10-dc84bcddd66f.png\">\r\n<img
width=\"1414\" alt=\"Screen Shot 2023-04-25 at 11 59 57
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906468-48b27002-5771-42df-9ee5-5852dabeaaeb.png\">\r\n<img
width=\"623\" alt=\"Screen Shot 2023-04-25 at 11 57 53
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906470-4ea5acf7-bff2-41af-a679-7e4b9f43c377.png\">\r\n<img
width=\"735\" alt=\"Screen Shot 2023-04-27 at 4 16 17
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234982914-128af18e-204a-4df6-a791-ac3155d8b5b9.png\">\r\n<img
width=\"1240\" alt=\"Screen Shot 2023-04-28 at 2 09 29
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223171-f2177983-f8cc-45a3-8ff8-76850508e63e.png\">\r\n<img
width=\"602\" alt=\"Screen Shot 2023-04-28 at 11 12 49
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223288-7b01dd85-2311-4b42-bb91-92e4a4f454e3.png\">\r\n<img
width=\"552\" alt=\"Screen Shot 2023-04-28 at 11 12 25
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223290-00cc6a8c-7f9c-46f1-b8ae-5c98eaeaa35d.png\">\r\n<img
width=\"1448\" alt=\"Screen Shot 2023-04-28 at 2 56 58
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235230906-093d720c-9ac9-4cf1-b04a-34a1409d7379.png\">\r\n\r\n---------\r\n\r\nCo-authored-by:
florent-leborgne <florent.leborgne@elastic.co>\r\nCo-authored-by: Kibana
Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"589ea3affc6c64ef69c81bc01da767388b246dc9","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","Team:uptime","release_note:skip","Team:Fleet","v8.8.0","v8.9.0"],"number":156029,"url":"https://github.com/elastic/kibana/pull/156029","mergeCommit":{"message":"[Synthetics]
Adjust content (#156029)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/155936\r\nRelates to
https://github.com/elastic/kibana/issues/152915\r\nResolves
https://github.com/elastic/kibana/issues/150944\r\nResolves
https://github.com/elastic/kibana/issues/156166\r\n\r\nCopy
fixes:\r\n\r\n- Alerting config: Address
Typo\r\n(https://github.com/elastic/kibana/issues/152915#issuecomment-1516614675)\r\n-
Alerting config: Address success toast wording\r\n- Getting started
(\"Create your first monitor\") locations: Repeated text\r\nbetween
placeholder and hint text. To address this, I changed the\r\nhelptext to
give more detail\r\n- Private locations -> \"Monitors\" column: replaced
`Running` with\r\n`configured`\r\n- Overview page: Search bar
placeholder: `url` is now uppercase `URL`\r\n- Monitor status alert -
Updates text for viewer user to be consistent\r\nwith other
tooltips\r\n- Run once errors - Remove extra error toast \r\n- Run once
errors - Remove excess phrase from error\r\n- Sync errors - Made content
more user friendly\r\n- Synthetics App - replace references to Monitor
Management with\r\nSynthetics App\r\n- Enable/disable - clarify when
actions apply to all monitors\r\n- Project monitors - add reference to
enabling/disabling alerting on\r\nproject monitor page\r\n- Enablement -
Adjust content for less privileged users\r\n\r\nSome screenshots of the
fixes are below. These are not exhaustive\r\n<img width=\"1417\"
alt=\"Screen Shot 2023-04-25 at 12 12 38
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906460-529d48d4-f682-4d45-b439-7bd7189c37ea.png\">\r\n<img
width=\"772\" alt=\"Screen Shot 2023-04-25 at 12 12 31
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906462-b85d6fe0-2d32-42f0-81fb-2f528c5c0d87.png\">\r\n<img
width=\"909\" alt=\"Screen Shot 2023-04-25 at 12 12 10
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906466-49286af9-29c4-4bcb-9d10-dc84bcddd66f.png\">\r\n<img
width=\"1414\" alt=\"Screen Shot 2023-04-25 at 11 59 57
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906468-48b27002-5771-42df-9ee5-5852dabeaaeb.png\">\r\n<img
width=\"623\" alt=\"Screen Shot 2023-04-25 at 11 57 53
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906470-4ea5acf7-bff2-41af-a679-7e4b9f43c377.png\">\r\n<img
width=\"735\" alt=\"Screen Shot 2023-04-27 at 4 16 17
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234982914-128af18e-204a-4df6-a791-ac3155d8b5b9.png\">\r\n<img
width=\"1240\" alt=\"Screen Shot 2023-04-28 at 2 09 29
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223171-f2177983-f8cc-45a3-8ff8-76850508e63e.png\">\r\n<img
width=\"602\" alt=\"Screen Shot 2023-04-28 at 11 12 49
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223288-7b01dd85-2311-4b42-bb91-92e4a4f454e3.png\">\r\n<img
width=\"552\" alt=\"Screen Shot 2023-04-28 at 11 12 25
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223290-00cc6a8c-7f9c-46f1-b8ae-5c98eaeaa35d.png\">\r\n<img
width=\"1448\" alt=\"Screen Shot 2023-04-28 at 2 56 58
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235230906-093d720c-9ac9-4cf1-b04a-34a1409d7379.png\">\r\n\r\n---------\r\n\r\nCo-authored-by:
florent-leborgne <florent.leborgne@elastic.co>\r\nCo-authored-by: Kibana
Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"589ea3affc6c64ef69c81bc01da767388b246dc9"}},"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/156029","number":156029,"mergeCommit":{"message":"[Synthetics]
Adjust content (#156029)\n\n## Summary\r\n\r\nResolves
https://github.com/elastic/kibana/issues/155936\r\nRelates to
https://github.com/elastic/kibana/issues/152915\r\nResolves
https://github.com/elastic/kibana/issues/150944\r\nResolves
https://github.com/elastic/kibana/issues/156166\r\n\r\nCopy
fixes:\r\n\r\n- Alerting config: Address
Typo\r\n(https://github.com/elastic/kibana/issues/152915#issuecomment-1516614675)\r\n-
Alerting config: Address success toast wording\r\n- Getting started
(\"Create your first monitor\") locations: Repeated text\r\nbetween
placeholder and hint text. To address this, I changed the\r\nhelptext to
give more detail\r\n- Private locations -> \"Monitors\" column: replaced
`Running` with\r\n`configured`\r\n- Overview page: Search bar
placeholder: `url` is now uppercase `URL`\r\n- Monitor status alert -
Updates text for viewer user to be consistent\r\nwith other
tooltips\r\n- Run once errors - Remove extra error toast \r\n- Run once
errors - Remove excess phrase from error\r\n- Sync errors - Made content
more user friendly\r\n- Synthetics App - replace references to Monitor
Management with\r\nSynthetics App\r\n- Enable/disable - clarify when
actions apply to all monitors\r\n- Project monitors - add reference to
enabling/disabling alerting on\r\nproject monitor page\r\n- Enablement -
Adjust content for less privileged users\r\n\r\nSome screenshots of the
fixes are below. These are not exhaustive\r\n<img width=\"1417\"
alt=\"Screen Shot 2023-04-25 at 12 12 38
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906460-529d48d4-f682-4d45-b439-7bd7189c37ea.png\">\r\n<img
width=\"772\" alt=\"Screen Shot 2023-04-25 at 12 12 31
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906462-b85d6fe0-2d32-42f0-81fb-2f528c5c0d87.png\">\r\n<img
width=\"909\" alt=\"Screen Shot 2023-04-25 at 12 12 10
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906466-49286af9-29c4-4bcb-9d10-dc84bcddd66f.png\">\r\n<img
width=\"1414\" alt=\"Screen Shot 2023-04-25 at 11 59 57
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906468-48b27002-5771-42df-9ee5-5852dabeaaeb.png\">\r\n<img
width=\"623\" alt=\"Screen Shot 2023-04-25 at 11 57 53
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234906470-4ea5acf7-bff2-41af-a679-7e4b9f43c377.png\">\r\n<img
width=\"735\" alt=\"Screen Shot 2023-04-27 at 4 16 17
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/234982914-128af18e-204a-4df6-a791-ac3155d8b5b9.png\">\r\n<img
width=\"1240\" alt=\"Screen Shot 2023-04-28 at 2 09 29
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223171-f2177983-f8cc-45a3-8ff8-76850508e63e.png\">\r\n<img
width=\"602\" alt=\"Screen Shot 2023-04-28 at 11 12 49
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223288-7b01dd85-2311-4b42-bb91-92e4a4f454e3.png\">\r\n<img
width=\"552\" alt=\"Screen Shot 2023-04-28 at 11 12 25
AM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235223290-00cc6a8c-7f9c-46f1-b8ae-5c98eaeaa35d.png\">\r\n<img
width=\"1448\" alt=\"Screen Shot 2023-04-28 at 2 56 58
PM\"\r\nsrc=\"https://user-images.githubusercontent.com/11356435/235230906-093d720c-9ac9-4cf1-b04a-34a1409d7379.png\">\r\n\r\n---------\r\n\r\nCo-authored-by:
florent-leborgne <florent.leborgne@elastic.co>\r\nCo-authored-by: Kibana
Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"589ea3affc6c64ef69c81bc01da767388b246dc9"}}]}]
BACKPORT-->

Co-authored-by: Dominique Clarke <dominique.clarke@elastic.co>
 2023-05-02 16:07:29 -07:00
Kibana Machine
1e2fc15eb7
[8.8] [Fleet] Fix package install with older version (#156257) (#156408) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Fleet] Fix package install with older version
(#156257)](https://github.com/elastic/kibana/pull/156257)

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

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

<!--BACKPORT [{"author":{"name":"Jill
Guyonnet","email":"jill.guyonnet@elastic.co"},"sourceCommit":{"committedDate":"2023-05-02T15:02:51Z","message":"[Fleet]
Fix package install with older version (#156257)\n\n##
Summary\r\n\r\nThis PR fixes a bug where an older version of a package
cannot be\r\ninstalled when creating a new agent policy.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/152095\r\n\r\n### Reproducing
the bug\r\n\r\n1. Run Kibana off the `main` branch.\r\n2. Install a
package of your choice for the first time (it should not\r\nalready be
installed) on a version lower than the latest (cf. screenshot\r\n1). In
the configuration page under `Where to add this integration?`,\r\nleave
`New hosts` selected to ensure a new agent policy is created
(cf.\r\nscreenshot 2).\r\n3. After the package is installed, go to the
package settings: notice\r\nthat the installed version is actually the
latest (cf. screenshot 3).\r\n4. Note: if you go to the `Integration
policies` tab of the package, you\r\nwill notice that the integration
policy has the version number you\r\nintended to install (cf. screenshot
4).\r\n\r\n### Cause of the bug\r\n\r\nThe `onSubmit` hook used by the
package install form [makes use the of\r\nthe
`epm/packages/_bulk`\r\nendpoint](e62581f8bf/x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/hooks/form.tsx (L272))\r\nto
bulk install multiple packages if a new agent policy is to
be\r\ncreated. The `epm/packages/_bulk` endpoint accepts an array of
packages\r\nwhich are either specified by a package name (string) or
name and\r\nversion (object). In the current implementation, this hook
only provides\r\nthe package names, which resolves to the latest version
of the package\r\nbeing installed.\r\n\r\n### How this PR fixes the
bug\r\n\r\nThis PR make the following changes:\r\n* Make the
`BulkInstallPackagesFromRegistryRequestSchema` validation\r\naccepts an
array of either strings or objects of shape `{ name: string,\r\nversion:
string }` for packages.\r\n* Modify the `sendBulkInstallPackages`
request hook to do the same.\r\n* Make the `onSubmit` hook used by the
package install form pass the\r\npackage name and version to the
`epm/packages/_bulk` endpoint.\r\n\r\n### Additional changes\r\n\r\n*
Add API integration test for bulk package install\r\n* Amend OpenAPI
definition:
[Swagger\r\nlink](a4a3209905/x-pack/plugins/fleet/common/openapi/bundled.json#/Elastic%20Package%20Manager%20(EPM)/bulk-install-packages)\r\n(cf.
screenshot 7)\r\n\r\n### Testing steps\r\n\r\n1. (Optional) Test that
the `epm/packages/_bulk` endpoint accepts\r\npackage name as strings or
package name and version as objects, or even\r\na mix of both (cf.
screenshot 6).\r\n2. Same steps as `Reproducing the bug` above on this
branch. The correct\r\nversion of the package should be installed (cf
screenshot 5).\r\n\r\n### Screenshots\r\n\r\nScreenshot 1: preparing to
install an older version of a package:\r\n<img width=\"1917\"
alt=\"Screenshot 2023-05-02 at 11 21
12\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631501-aa03d2b0-6fe8-4e9a-8e0c-5547f8fccea0.png\">\r\n\r\n\r\nScreenshot
2: creating a new agent policy when installing the package:\r\n<img
width=\"1917\" alt=\"Screenshot 2023-05-02 at 11 21
33\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631650-3d9bfc19-ace3-4488-a7c7-48078aae3e7c.png\">\r\n\r\nScreenshot
3: integration settings after installing an older version\r\nonto a new
agent policy, showing that the installed version is actually\r\nthe
latest version:\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at 11
29
07\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631920-3ca8f606-d225-464e-8094-46aeee4869df.png\">\r\n\r\n\r\nScreenshot
4: `Integration policies` tab, showing that the integration\r\npolicy
has the older version:\r\n<img width=\"1917\" alt=\"Screenshot
2023-05-02 at 11 28
43\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235632212-c82a3ddd-cb33-4179-a4ab-b57e33e7490d.png\">\r\n\r\n\r\nScreenshot
5: integration settings after installing an older version\r\nonto a new
agent policy **with the bug fix**, showing that the correct\r\nversion
was installed:\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at 11
23
09\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235632590-bb26183d-ce60-439c-9bee-eadb9fdb9654.png\">\r\n\r\n\r\nScreenshot
6: API call showing the two ways of specifying a package\r\nusing the
`epm/packages/_bulk` endpoint (package name only, or name
and\r\nversion):\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at
11 59
11\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235637532-ae32072b-ca84-48bb-9760-120a2149f0e5.png\">\r\n\r\n\r\nScreenshot
7: `epm/packages/_bulk` endpoint reference on Swagger:\r\n<img
width=\"1429\" alt=\"Screenshot 2023-05-02 at 15 13
14\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235677504-e8ba1329-1a70-44f8-92c5-0f32e5da7e46.png\">\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d71f6f3d0337a66aab755ab576fa6f4f85652a5c","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","Team:Fleet","backport:prev-minor","v8.9.0"],"number":156257,"url":"https://github.com/elastic/kibana/pull/156257","mergeCommit":{"message":"[Fleet]
Fix package install with older version (#156257)\n\n##
Summary\r\n\r\nThis PR fixes a bug where an older version of a package
cannot be\r\ninstalled when creating a new agent policy.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/152095\r\n\r\n### Reproducing
the bug\r\n\r\n1. Run Kibana off the `main` branch.\r\n2. Install a
package of your choice for the first time (it should not\r\nalready be
installed) on a version lower than the latest (cf. screenshot\r\n1). In
the configuration page under `Where to add this integration?`,\r\nleave
`New hosts` selected to ensure a new agent policy is created
(cf.\r\nscreenshot 2).\r\n3. After the package is installed, go to the
package settings: notice\r\nthat the installed version is actually the
latest (cf. screenshot 3).\r\n4. Note: if you go to the `Integration
policies` tab of the package, you\r\nwill notice that the integration
policy has the version number you\r\nintended to install (cf. screenshot
4).\r\n\r\n### Cause of the bug\r\n\r\nThe `onSubmit` hook used by the
package install form [makes use the of\r\nthe
`epm/packages/_bulk`\r\nendpoint](e62581f8bf/x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/hooks/form.tsx (L272))\r\nto
bulk install multiple packages if a new agent policy is to
be\r\ncreated. The `epm/packages/_bulk` endpoint accepts an array of
packages\r\nwhich are either specified by a package name (string) or
name and\r\nversion (object). In the current implementation, this hook
only provides\r\nthe package names, which resolves to the latest version
of the package\r\nbeing installed.\r\n\r\n### How this PR fixes the
bug\r\n\r\nThis PR make the following changes:\r\n* Make the
`BulkInstallPackagesFromRegistryRequestSchema` validation\r\naccepts an
array of either strings or objects of shape `{ name: string,\r\nversion:
string }` for packages.\r\n* Modify the `sendBulkInstallPackages`
request hook to do the same.\r\n* Make the `onSubmit` hook used by the
package install form pass the\r\npackage name and version to the
`epm/packages/_bulk` endpoint.\r\n\r\n### Additional changes\r\n\r\n*
Add API integration test for bulk package install\r\n* Amend OpenAPI
definition:
[Swagger\r\nlink](a4a3209905/x-pack/plugins/fleet/common/openapi/bundled.json#/Elastic%20Package%20Manager%20(EPM)/bulk-install-packages)\r\n(cf.
screenshot 7)\r\n\r\n### Testing steps\r\n\r\n1. (Optional) Test that
the `epm/packages/_bulk` endpoint accepts\r\npackage name as strings or
package name and version as objects, or even\r\na mix of both (cf.
screenshot 6).\r\n2. Same steps as `Reproducing the bug` above on this
branch. The correct\r\nversion of the package should be installed (cf
screenshot 5).\r\n\r\n### Screenshots\r\n\r\nScreenshot 1: preparing to
install an older version of a package:\r\n<img width=\"1917\"
alt=\"Screenshot 2023-05-02 at 11 21
12\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631501-aa03d2b0-6fe8-4e9a-8e0c-5547f8fccea0.png\">\r\n\r\n\r\nScreenshot
2: creating a new agent policy when installing the package:\r\n<img
width=\"1917\" alt=\"Screenshot 2023-05-02 at 11 21
33\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631650-3d9bfc19-ace3-4488-a7c7-48078aae3e7c.png\">\r\n\r\nScreenshot
3: integration settings after installing an older version\r\nonto a new
agent policy, showing that the installed version is actually\r\nthe
latest version:\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at 11
29
07\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631920-3ca8f606-d225-464e-8094-46aeee4869df.png\">\r\n\r\n\r\nScreenshot
4: `Integration policies` tab, showing that the integration\r\npolicy
has the older version:\r\n<img width=\"1917\" alt=\"Screenshot
2023-05-02 at 11 28
43\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235632212-c82a3ddd-cb33-4179-a4ab-b57e33e7490d.png\">\r\n\r\n\r\nScreenshot
5: integration settings after installing an older version\r\nonto a new
agent policy **with the bug fix**, showing that the correct\r\nversion
was installed:\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at 11
23
09\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235632590-bb26183d-ce60-439c-9bee-eadb9fdb9654.png\">\r\n\r\n\r\nScreenshot
6: API call showing the two ways of specifying a package\r\nusing the
`epm/packages/_bulk` endpoint (package name only, or name
and\r\nversion):\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at
11 59
11\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235637532-ae32072b-ca84-48bb-9760-120a2149f0e5.png\">\r\n\r\n\r\nScreenshot
7: `epm/packages/_bulk` endpoint reference on Swagger:\r\n<img
width=\"1429\" alt=\"Screenshot 2023-05-02 at 15 13
14\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235677504-e8ba1329-1a70-44f8-92c5-0f32e5da7e46.png\">\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d71f6f3d0337a66aab755ab576fa6f4f85652a5c"}},"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/156257","number":156257,"mergeCommit":{"message":"[Fleet]
Fix package install with older version (#156257)\n\n##
Summary\r\n\r\nThis PR fixes a bug where an older version of a package
cannot be\r\ninstalled when creating a new agent policy.\r\n\r\nCloses
https://github.com/elastic/kibana/issues/152095\r\n\r\n### Reproducing
the bug\r\n\r\n1. Run Kibana off the `main` branch.\r\n2. Install a
package of your choice for the first time (it should not\r\nalready be
installed) on a version lower than the latest (cf. screenshot\r\n1). In
the configuration page under `Where to add this integration?`,\r\nleave
`New hosts` selected to ensure a new agent policy is created
(cf.\r\nscreenshot 2).\r\n3. After the package is installed, go to the
package settings: notice\r\nthat the installed version is actually the
latest (cf. screenshot 3).\r\n4. Note: if you go to the `Integration
policies` tab of the package, you\r\nwill notice that the integration
policy has the version number you\r\nintended to install (cf. screenshot
4).\r\n\r\n### Cause of the bug\r\n\r\nThe `onSubmit` hook used by the
package install form [makes use the of\r\nthe
`epm/packages/_bulk`\r\nendpoint](e62581f8bf/x-pack/plugins/fleet/public/applications/fleet/sections/agent_policy/create_package_policy_page/single_page_layout/hooks/form.tsx (L272))\r\nto
bulk install multiple packages if a new agent policy is to
be\r\ncreated. The `epm/packages/_bulk` endpoint accepts an array of
packages\r\nwhich are either specified by a package name (string) or
name and\r\nversion (object). In the current implementation, this hook
only provides\r\nthe package names, which resolves to the latest version
of the package\r\nbeing installed.\r\n\r\n### How this PR fixes the
bug\r\n\r\nThis PR make the following changes:\r\n* Make the
`BulkInstallPackagesFromRegistryRequestSchema` validation\r\naccepts an
array of either strings or objects of shape `{ name: string,\r\nversion:
string }` for packages.\r\n* Modify the `sendBulkInstallPackages`
request hook to do the same.\r\n* Make the `onSubmit` hook used by the
package install form pass the\r\npackage name and version to the
`epm/packages/_bulk` endpoint.\r\n\r\n### Additional changes\r\n\r\n*
Add API integration test for bulk package install\r\n* Amend OpenAPI
definition:
[Swagger\r\nlink](a4a3209905/x-pack/plugins/fleet/common/openapi/bundled.json#/Elastic%20Package%20Manager%20(EPM)/bulk-install-packages)\r\n(cf.
screenshot 7)\r\n\r\n### Testing steps\r\n\r\n1. (Optional) Test that
the `epm/packages/_bulk` endpoint accepts\r\npackage name as strings or
package name and version as objects, or even\r\na mix of both (cf.
screenshot 6).\r\n2. Same steps as `Reproducing the bug` above on this
branch. The correct\r\nversion of the package should be installed (cf
screenshot 5).\r\n\r\n### Screenshots\r\n\r\nScreenshot 1: preparing to
install an older version of a package:\r\n<img width=\"1917\"
alt=\"Screenshot 2023-05-02 at 11 21
12\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631501-aa03d2b0-6fe8-4e9a-8e0c-5547f8fccea0.png\">\r\n\r\n\r\nScreenshot
2: creating a new agent policy when installing the package:\r\n<img
width=\"1917\" alt=\"Screenshot 2023-05-02 at 11 21
33\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631650-3d9bfc19-ace3-4488-a7c7-48078aae3e7c.png\">\r\n\r\nScreenshot
3: integration settings after installing an older version\r\nonto a new
agent policy, showing that the installed version is actually\r\nthe
latest version:\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at 11
29
07\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235631920-3ca8f606-d225-464e-8094-46aeee4869df.png\">\r\n\r\n\r\nScreenshot
4: `Integration policies` tab, showing that the integration\r\npolicy
has the older version:\r\n<img width=\"1917\" alt=\"Screenshot
2023-05-02 at 11 28
43\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235632212-c82a3ddd-cb33-4179-a4ab-b57e33e7490d.png\">\r\n\r\n\r\nScreenshot
5: integration settings after installing an older version\r\nonto a new
agent policy **with the bug fix**, showing that the correct\r\nversion
was installed:\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at 11
23
09\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235632590-bb26183d-ce60-439c-9bee-eadb9fdb9654.png\">\r\n\r\n\r\nScreenshot
6: API call showing the two ways of specifying a package\r\nusing the
`epm/packages/_bulk` endpoint (package name only, or name
and\r\nversion):\r\n<img width=\"1917\" alt=\"Screenshot 2023-05-02 at
11 59
11\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235637532-ae32072b-ca84-48bb-9760-120a2149f0e5.png\">\r\n\r\n\r\nScreenshot
7: `epm/packages/_bulk` endpoint reference on Swagger:\r\n<img
width=\"1429\" alt=\"Screenshot 2023-05-02 at 15 13
14\"\r\nsrc=\"https://user-images.githubusercontent.com/23701614/235677504-e8ba1329-1a70-44f8-92c5-0f32e5da7e46.png\">\r\n\r\n###
Checklist\r\n\r\n- [x] [Unit or
functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere
updated or added to match the most common
scenarios\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"d71f6f3d0337a66aab755ab576fa6f4f85652a5c"}}]}]
BACKPORT-->

Co-authored-by: Jill Guyonnet <jill.guyonnet@elastic.co>
 2023-05-02 09:11:40 -07:00
Kibana Machine
ad65768a1b
[8.8] [RAM] Apply maintenance windows privilege to UI (#156191) (#156387) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[RAM] Apply maintenance windows privilege to UI
(#156191)](https://github.com/elastic/kibana/pull/156191)

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

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

<!--BACKPORT [{"author":{"name":"Xavier
Mouligneau","email":"xavier.mouligneau@elastic.co"},"sourceCommit":{"committedDate":"2023-05-02T13:47:29Z","message":"[RAM]
Apply maintenance windows privilege to UI (#156191)\n\n##
Summary\r\n\r\nWe will have three scenarios with kibana
privileges\r\n\r\n### NONE\r\nKibana privileges form maintenance
window:\r\n<img width=\"680\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188523-acaff7de-54d4-4991-a014-05c0f449738c.png\">\r\n\r\n`The
expected result is to not see maintenance window at all`\r\n\r\n<img
width=\"1481\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188658-6a53b463-4856-42c7-916e-aa8e6d7e326b.png\">\r\n\r\n###
READ\r\nKibana privileges form maintenance window:\r\n<img width=\"677\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188908-623d32ac-39a7-484e-bd5c-f858e04d16b2.png\">\r\n\r\n`The
expected result is to only see the table with window maintenance\r\nand
you can not edit them`\r\n\r\n<img width=\"1487\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189169-f71422bf-6394-4574-87fb-14c653ca1e79.png\">\r\n<img
width=\"1484\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235192048-149519ba-0505-46e3-b737-2703560eb3d6.png\">\r\n\r\n\r\n###
ALL\r\nKibana privileges form maintenance window:\r\n<img width=\"668\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189384-e71d9138-221c-4024-91bb-2ae32da1bd3b.png\">\r\n\r\n`The
expected result is to be able to create/edit/etc on any
maintenance\r\nwindows`\r\n\r\n<img width=\"1484\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189974-e36c1e65-0586-4840-ace5-32caf06455c6.png\">\r\n<img
width=\"1481\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235192269-0f8d1922-d48f-494c-9979-2288bf142286.png\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [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\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"3c9da2cd296f9e23b5052e8bf624ddd062bcbcd0","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","impact:high","Team:ResponseOps","v8.8.0","v8.9.0"],"number":156191,"url":"https://github.com/elastic/kibana/pull/156191","mergeCommit":{"message":"[RAM]
Apply maintenance windows privilege to UI (#156191)\n\n##
Summary\r\n\r\nWe will have three scenarios with kibana
privileges\r\n\r\n### NONE\r\nKibana privileges form maintenance
window:\r\n<img width=\"680\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188523-acaff7de-54d4-4991-a014-05c0f449738c.png\">\r\n\r\n`The
expected result is to not see maintenance window at all`\r\n\r\n<img
width=\"1481\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188658-6a53b463-4856-42c7-916e-aa8e6d7e326b.png\">\r\n\r\n###
READ\r\nKibana privileges form maintenance window:\r\n<img width=\"677\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188908-623d32ac-39a7-484e-bd5c-f858e04d16b2.png\">\r\n\r\n`The
expected result is to only see the table with window maintenance\r\nand
you can not edit them`\r\n\r\n<img width=\"1487\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189169-f71422bf-6394-4574-87fb-14c653ca1e79.png\">\r\n<img
width=\"1484\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235192048-149519ba-0505-46e3-b737-2703560eb3d6.png\">\r\n\r\n\r\n###
ALL\r\nKibana privileges form maintenance window:\r\n<img width=\"668\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189384-e71d9138-221c-4024-91bb-2ae32da1bd3b.png\">\r\n\r\n`The
expected result is to be able to create/edit/etc on any
maintenance\r\nwindows`\r\n\r\n<img width=\"1484\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189974-e36c1e65-0586-4840-ace5-32caf06455c6.png\">\r\n<img
width=\"1481\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235192269-0f8d1922-d48f-494c-9979-2288bf142286.png\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [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\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"3c9da2cd296f9e23b5052e8bf624ddd062bcbcd0"}},"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/156191","number":156191,"mergeCommit":{"message":"[RAM]
Apply maintenance windows privilege to UI (#156191)\n\n##
Summary\r\n\r\nWe will have three scenarios with kibana
privileges\r\n\r\n### NONE\r\nKibana privileges form maintenance
window:\r\n<img width=\"680\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188523-acaff7de-54d4-4991-a014-05c0f449738c.png\">\r\n\r\n`The
expected result is to not see maintenance window at all`\r\n\r\n<img
width=\"1481\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188658-6a53b463-4856-42c7-916e-aa8e6d7e326b.png\">\r\n\r\n###
READ\r\nKibana privileges form maintenance window:\r\n<img width=\"677\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235188908-623d32ac-39a7-484e-bd5c-f858e04d16b2.png\">\r\n\r\n`The
expected result is to only see the table with window maintenance\r\nand
you can not edit them`\r\n\r\n<img width=\"1487\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189169-f71422bf-6394-4574-87fb-14c653ca1e79.png\">\r\n<img
width=\"1484\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235192048-149519ba-0505-46e3-b737-2703560eb3d6.png\">\r\n\r\n\r\n###
ALL\r\nKibana privileges form maintenance window:\r\n<img width=\"668\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189384-e71d9138-221c-4024-91bb-2ae32da1bd3b.png\">\r\n\r\n`The
expected result is to be able to create/edit/etc on any
maintenance\r\nwindows`\r\n\r\n<img width=\"1484\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235189974-e36c1e65-0586-4840-ace5-32caf06455c6.png\">\r\n<img
width=\"1481\"
alt=\"image\"\r\nsrc=\"https://user-images.githubusercontent.com/189600/235192269-0f8d1922-d48f-494c-9979-2288bf142286.png\">\r\n\r\n\r\n\r\n###
Checklist\r\n\r\nDelete any items that are not applicable to this
PR.\r\n\r\n- [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\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"3c9da2cd296f9e23b5052e8bf624ddd062bcbcd0"}}]}]
BACKPORT-->

Co-authored-by: Xavier Mouligneau <xavier.mouligneau@elastic.co>
 2023-05-02 08:26:07 -07:00
Kibana Machine
595cc3fbd0
[8.8] [Infarstructure UI] Fix hosts view functional test (#155772) (#156360) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Infarstructure UI] Fix hosts view functional test
(#155772)](https://github.com/elastic/kibana/pull/155772)

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

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

<!--BACKPORT [{"author":{"name":"Carlos
Crespo","email":"crespocarlos@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-02T11:40:48Z","message":"[Infarstructure
UI] Fix hosts view functional test (#155772)\n\ncloses
https://github.com/elastic/kibana/issues/155429\r\ncloses
https://github.com/elastic/kibana/issues/155293\r\n\r\n##
Summary\r\n\r\n\r\nThis PR fixes the hosts view functional test,
stabilizing the flaky test\r\ncases that started to fail after changes
were made to the page\r\n\r\n\r\n### How to test\r\n\r\n- `yarn
test:ftr:server
--config\r\nx-pack/test/functional/apps/infra/config.ts`\r\n- `yarn
test:ftr:runner --config\r\nx-pack/test/functional/apps/infra/config.ts
--include\r\nx-pack/test/functional/apps/infra/hosts_view.ts`\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"c4669323f7a1a781eaa2eaddab74971c480c80e8","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Metrics
UI","Team:Infra Monitoring
UI","release_note:skip","backport:prev-minor","Feature:ObsHosts","v8.9.0"],"number":155772,"url":"https://github.com/elastic/kibana/pull/155772","mergeCommit":{"message":"[Infarstructure
UI] Fix hosts view functional test (#155772)\n\ncloses
https://github.com/elastic/kibana/issues/155429\r\ncloses
https://github.com/elastic/kibana/issues/155293\r\n\r\n##
Summary\r\n\r\n\r\nThis PR fixes the hosts view functional test,
stabilizing the flaky test\r\ncases that started to fail after changes
were made to the page\r\n\r\n\r\n### How to test\r\n\r\n- `yarn
test:ftr:server
--config\r\nx-pack/test/functional/apps/infra/config.ts`\r\n- `yarn
test:ftr:runner --config\r\nx-pack/test/functional/apps/infra/config.ts
--include\r\nx-pack/test/functional/apps/infra/hosts_view.ts`\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"c4669323f7a1a781eaa2eaddab74971c480c80e8"}},"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/155772","number":155772,"mergeCommit":{"message":"[Infarstructure
UI] Fix hosts view functional test (#155772)\n\ncloses
https://github.com/elastic/kibana/issues/155429\r\ncloses
https://github.com/elastic/kibana/issues/155293\r\n\r\n##
Summary\r\n\r\n\r\nThis PR fixes the hosts view functional test,
stabilizing the flaky test\r\ncases that started to fail after changes
were made to the page\r\n\r\n\r\n### How to test\r\n\r\n- `yarn
test:ftr:server
--config\r\nx-pack/test/functional/apps/infra/config.ts`\r\n- `yarn
test:ftr:runner --config\r\nx-pack/test/functional/apps/infra/config.ts
--include\r\nx-pack/test/functional/apps/infra/hosts_view.ts`\r\n\r\n---------\r\n\r\nCo-authored-by:
Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"c4669323f7a1a781eaa2eaddab74971c480c80e8"}}]}]
BACKPORT-->

Co-authored-by: Carlos Crespo <crespocarlos@users.noreply.github.com>
 2023-05-02 05:52:38 -07:00
Kibana Machine
a675560774
[8.8] [Lens][TSVB] Add TSDB field checks functional tests (#156165) (#156333) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Lens][TSVB] Add TSDB field checks functional tests
(#156165)](https://github.com/elastic/kibana/pull/156165)

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

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

<!--BACKPORT [{"author":{"name":"Marco
Liberati","email":"dej611@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-05-02T07:58:07Z","message":"[Lens][TSVB]
Add TSDB field checks functional tests (#156165)\n\n##
Summary\r\n\r\nFix #155830 \r\n\r\nAdd basic checks for both Lens and
TSVB editors.\r\nIn Lens more advanced tests are performed to check for
compatible and\r\nuncompatible operations for specific TSDB field
types.\r\nIn TSVB the check is only performed to verify that the editor
and\r\nvisualization doesn't crash and when unsupported the right error
message\r\nis shown.\r\n\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":"3c261237b07450ceee4877705bd8f843f0a51eca","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:TSVB","Team:Visualizations","release_note:skip","Feature:Lens","v8.8.0","v8.9.0"],"number":156165,"url":"https://github.com/elastic/kibana/pull/156165","mergeCommit":{"message":"[Lens][TSVB]
Add TSDB field checks functional tests (#156165)\n\n##
Summary\r\n\r\nFix #155830 \r\n\r\nAdd basic checks for both Lens and
TSVB editors.\r\nIn Lens more advanced tests are performed to check for
compatible and\r\nuncompatible operations for specific TSDB field
types.\r\nIn TSVB the check is only performed to verify that the editor
and\r\nvisualization doesn't crash and when unsupported the right error
message\r\nis shown.\r\n\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":"3c261237b07450ceee4877705bd8f843f0a51eca"}},"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/156165","number":156165,"mergeCommit":{"message":"[Lens][TSVB]
Add TSDB field checks functional tests (#156165)\n\n##
Summary\r\n\r\nFix #155830 \r\n\r\nAdd basic checks for both Lens and
TSVB editors.\r\nIn Lens more advanced tests are performed to check for
compatible and\r\nuncompatible operations for specific TSDB field
types.\r\nIn TSVB the check is only performed to verify that the editor
and\r\nvisualization doesn't crash and when unsupported the right error
message\r\nis shown.\r\n\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":"3c261237b07450ceee4877705bd8f843f0a51eca"}}]}]
BACKPORT-->

Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
 2023-05-02 01:57:23 -07:00
Kibana Machine
52c79188e3
[8.8] [Cases] Fix lens visualization in comment and description markdown (#155897) (#156189) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Cases] Fix lens visualization in comment and description markdown
(#155897)](https://github.com/elastic/kibana/pull/155897)

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

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

<!--BACKPORT [{"author":{"name":"Janki
Salvi","email":"117571355+js-jankisalvi@users.noreply.github.com"},"sourceCommit":{"committedDate":"2023-04-28T15:21:00Z","message":"[Cases]
Fix lens visualization in comment and description markdown
(#155897)\n\n## Summary\r\n\r\nThis PR fixes issues with lens
visualization in case view page for\r\ncomment and
description.\r\n\r\nFixes:
#155631\r\n\r\n**Description:**\r\n\r\n\r\n234858215-feaac6c7-5579-4a00-bb97-00e0b23f5cfe.mov\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**Flakey Test
runner:**\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2182\r\n\r\nNext
one after
update:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2183\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"0c0e02277f6c0d52dd4906e7421edcbd4c0dd962","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","Team:ResponseOps","Feature:Cases","v8.7.0","v8.8.0","v8.9.0"],"number":155897,"url":"https://github.com/elastic/kibana/pull/155897","mergeCommit":{"message":"[Cases]
Fix lens visualization in comment and description markdown
(#155897)\n\n## Summary\r\n\r\nThis PR fixes issues with lens
visualization in case view page for\r\ncomment and
description.\r\n\r\nFixes:
#155631\r\n\r\n**Description:**\r\n\r\n\r\n234858215-feaac6c7-5579-4a00-bb97-00e0b23f5cfe.mov\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**Flakey Test
runner:**\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2182\r\n\r\nNext
one after
update:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2183\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"0c0e02277f6c0d52dd4906e7421edcbd4c0dd962"}},"sourceBranch":"main","suggestedTargetBranches":["8.7","8.8"],"targetPullRequestStates":[{"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/155897","number":155897,"mergeCommit":{"message":"[Cases]
Fix lens visualization in comment and description markdown
(#155897)\n\n## Summary\r\n\r\nThis PR fixes issues with lens
visualization in case view page for\r\ncomment and
description.\r\n\r\nFixes:
#155631\r\n\r\n**Description:**\r\n\r\n\r\n234858215-feaac6c7-5579-4a00-bb97-00e0b23f5cfe.mov\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**Flakey Test
runner:**\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2182\r\n\r\nNext
one after
update:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2183\r\n\r\n---------\r\n\r\nCo-authored-by:
kibanamachine
<42973632+kibanamachine@users.noreply.github.com>","sha":"0c0e02277f6c0d52dd4906e7421edcbd4c0dd962"}}]}]
BACKPORT-->

Co-authored-by: Janki Salvi <117571355+js-jankisalvi@users.noreply.github.com>
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
 2023-05-01 18:13:54 -07:00
Kibana Machine
5a93cdf4f5
[8.8] [Discover] Fix flaky Discover security functional test (#156221) (#156292) 
# Backport

This will backport the following commits from `main` to `8.8`:
- [[Discover] Fix flaky Discover security functional test
(#156221)](https://github.com/elastic/kibana/pull/156221)

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

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

<!--BACKPORT [{"author":{"name":"Davis
McPhee","email":"davis.mcphee@elastic.co"},"sourceCommit":{"committedDate":"2023-05-01T18:23:30Z","message":"[Discover]
Fix flaky Discover security functional test (#156221)\n\n##
Summary\r\n\r\nFixes #153796.\r\n\r\nFlaky test runner x
100:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2196\r\n\r\n###
Checklist\r\n\r\n- [ ] ~Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)~\r\n-
[
]\r\n~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials~\r\n- [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- [ ] ~Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard\r\naccessibility](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###
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":"5035be85060df015eaeb75ef9d5f8a43f6727498","branchLabelMapping":{"^v8.9.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Discover","release_note:skip","Team:DataDiscovery","v8.8.0","v8.9.0"],"number":156221,"url":"https://github.com/elastic/kibana/pull/156221","mergeCommit":{"message":"[Discover]
Fix flaky Discover security functional test (#156221)\n\n##
Summary\r\n\r\nFixes #153796.\r\n\r\nFlaky test runner x
100:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2196\r\n\r\n###
Checklist\r\n\r\n- [ ] ~Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)~\r\n-
[
]\r\n~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials~\r\n- [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- [ ] ~Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard\r\naccessibility](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###
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":"5035be85060df015eaeb75ef9d5f8a43f6727498"}},"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/156221","number":156221,"mergeCommit":{"message":"[Discover]
Fix flaky Discover security functional test (#156221)\n\n##
Summary\r\n\r\nFixes #153796.\r\n\r\nFlaky test runner x
100:\r\nhttps://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/2196\r\n\r\n###
Checklist\r\n\r\n- [ ] ~Any text added follows [EUI's
writing\r\nguidelines](https://elastic.github.io/eui/#/guidelines/writing),
uses\r\nsentence case text and includes
[i18n\r\nsupport](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)~\r\n-
[
]\r\n~[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\r\nwas
added for features that require explanation or tutorials~\r\n- [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- [ ] ~Any UI
touched in this PR is usable by keyboard only (learn more\r\nabout
[keyboard\r\naccessibility](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###
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":"5035be85060df015eaeb75ef9d5f8a43f6727498"}}]}]
BACKPORT-->

---------

Co-authored-by: Davis McPhee <davis.mcphee@elastic.co>
 2023-05-01 13:06:31 -07:00