mirror of
https://github.com/elastic/kibana.git
synced 2025-04-20 07:48:52 -04:00
84501 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
Kibana Machine
|
33f9a660ca
|
[9.0] [Console] Fix auto-indentation issues (#214358) (#215461)
# Backport This will backport the following commits from `main` to `9.0`: - [[Console] Fix auto-indentation issues (#214358)](https://github.com/elastic/kibana/pull/214358) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T10:23:43Z","message":"[Console] Fix auto-indentation issues (#214358)\n\nFixes https://github.com/elastic/kibana/issues/210231\nFixes https://github.com/elastic/kibana/issues/212499\n\n## Summary\nTest request:\n\n```\nGET _ingest/pipeline/_simulate\n{\n \"docs\": [\n {\n \"_source\": {\n \"trace\": {\n \"name\": \"GET /actuator/health/**\"\n },\n \"transaction\": {\n \"outcome\": \"success\"\n }\n }\n },\n {\n \"_source\": {\n \"vulnerability\": {\n \"reference\": [\n \"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15778\"\n ]\n }\n }\n }\n ]\n}\n```","sha":"18aa055a6a65ebbe1957258c8044c420bd98c123","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v9.1.0","v8.19.0"],"title":"[Console] Fix auto-indentation issues","number":214358,"url":"https://github.com/elastic/kibana/pull/214358","mergeCommit":{"message":"[Console] Fix auto-indentation issues (#214358)\n\nFixes https://github.com/elastic/kibana/issues/210231\nFixes https://github.com/elastic/kibana/issues/212499\n\n## Summary\nTest request:\n\n```\nGET _ingest/pipeline/_simulate\n{\n \"docs\": [\n {\n \"_source\": {\n \"trace\": {\n \"name\": \"GET /actuator/health/**\"\n },\n \"transaction\": {\n \"outcome\": \"success\"\n }\n }\n },\n {\n \"_source\": {\n \"vulnerability\": {\n \"reference\": [\n \"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15778\"\n ]\n }\n }\n }\n ]\n}\n```","sha":"18aa055a6a65ebbe1957258c8044c420bd98c123"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214358","number":214358,"mergeCommit":{"message":"[Console] Fix auto-indentation issues (#214358)\n\nFixes https://github.com/elastic/kibana/issues/210231\nFixes https://github.com/elastic/kibana/issues/212499\n\n## Summary\nTest request:\n\n```\nGET _ingest/pipeline/_simulate\n{\n \"docs\": [\n {\n \"_source\": {\n \"trace\": {\n \"name\": \"GET /actuator/health/**\"\n },\n \"transaction\": {\n \"outcome\": \"success\"\n }\n }\n },\n {\n \"_source\": {\n \"vulnerability\": {\n \"reference\": [\n \"https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15778\"\n ]\n }\n }\n }\n ]\n}\n```","sha":"18aa055a6a65ebbe1957258c8044c420bd98c123"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Kibana Machine
|
138adbd6f1
|
[9.0] [Security Solution] Siem migration copy changes (#215220) (#215386)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] Siem migration copy changes (#215220)](https://github.com/elastic/kibana/pull/215220) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Massaneda","email":"sergi.massaneda@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T18:02:57Z","message":"[Security Solution] Siem migration copy changes (#215220)\n\n## Summary\n\nLast-minute copy changes\n\n<img width=\"788\" alt=\"task\"\nsrc=\"https://github.com/user-attachments/assets/839b4d9c-67f6-43b9-a62e-4f1f974215ca\"\n/>","sha":"108716dce8d097a94b09e486c5876940c57158bd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Threat Hunting","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution] Siem migration copy changes","number":215220,"url":"https://github.com/elastic/kibana/pull/215220","mergeCommit":{"message":"[Security Solution] Siem migration copy changes (#215220)\n\n## Summary\n\nLast-minute copy changes\n\n<img width=\"788\" alt=\"task\"\nsrc=\"https://github.com/user-attachments/assets/839b4d9c-67f6-43b9-a62e-4f1f974215ca\"\n/>","sha":"108716dce8d097a94b09e486c5876940c57158bd"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215220","number":215220,"mergeCommit":{"message":"[Security Solution] Siem migration copy changes (#215220)\n\n## Summary\n\nLast-minute copy changes\n\n<img width=\"788\" alt=\"task\"\nsrc=\"https://github.com/user-attachments/assets/839b4d9c-67f6-43b9-a62e-4f1f974215ca\"\n/>","sha":"108716dce8d097a94b09e486c5876940c57158bd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com> |
||
elastic-vault-github-plugin-prod[bot]
|
62e3f54db9
|
[9.0] Sync bundled packages with Package Storage (#215374)
Automated by https://buildkite.com/elastic/package-storage-infra-kibana-discover-release-branches/builds/2486 Co-authored-by: elasticmachine <elasticmachine@elastic.co> Co-authored-by: Julia Bardi <90178898+juliaElastic@users.noreply.github.com> |
||
|
Kibana Machine
|
85c2277236
|
[9.0] Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232) (#215436)
# Backport This will backport the following commits from `main` to `9.0`: - [Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)](https://github.com/elastic/kibana/pull/215232) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"elastic-renovate-prod[bot]","email":"174716857+elastic-renovate-prod[bot]@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-21T06:57:46Z","message":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​openfeature/launchdarkly-client-provider | dependencies |\npatch | [`^0.3.1` ->\n`^0.3.2`](https://renovatebot.com/diffs/npm/@openfeature%2flaunchdarkly-client-provider/0.3.1/0.3.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"933564d713c3f6c090702cdca97a76073d437419","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","Team:Security","release_note:skip","backport:prev-minor","backport:prev-major","v9.1.0"],"title":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main)","number":215232,"url":"https://github.com/elastic/kibana/pull/215232","mergeCommit":{"message":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​openfeature/launchdarkly-client-provider | dependencies |\npatch | [`^0.3.1` ->\n`^0.3.2`](https://renovatebot.com/diffs/npm/@openfeature%2flaunchdarkly-client-provider/0.3.1/0.3.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"933564d713c3f6c090702cdca97a76073d437419"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215232","number":215232,"mergeCommit":{"message":"Update dependency @openfeature/launchdarkly-client-provider to ^0.3.2 (main) (#215232)\n\nThis PR contains the following updates:\n\n| Package | Type | Update | Change |\n|---|---|---|---|\n| @​openfeature/launchdarkly-client-provider | dependencies |\npatch | [`^0.3.1` ->\n`^0.3.2`](https://renovatebot.com/diffs/npm/@openfeature%2flaunchdarkly-client-provider/0.3.1/0.3.2)\n|\n\n---\n\n### Configuration\n\n📅 **Schedule**: Branch creation - At any time (no schedule defined),\nAutomerge - At any time (no schedule defined).\n\n🚦 **Automerge**: Disabled by config. Please merge this manually once you\nare satisfied.\n\n♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the\nrebase/retry checkbox.\n\n🔕 **Ignore**: Close this PR and you won't be reminded about this update\nagain.\n\n---\n\n- [ ] If you want to rebase/retry this PR, check\nthis box\n\n---\n\nThis PR has been generated by [Renovate\nBot](https://redirect.github.com/renovatebot/renovate).\n\n\n\nCo-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>","sha":"933564d713c3f6c090702cdca97a76073d437419"}}]}] BACKPORT--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
c68acf243e
|
[9.0] [Console] Add autocomplete for data streams (#214465) (#215407)
# Backport This will backport the following commits from `main` to `9.0`: - [[Console] Add autocomplete for data streams (#214465)](https://github.com/elastic/kibana/pull/214465) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Stoeva","email":"59341489+ElenaStoeva@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-20T19:43:15Z","message":"[Console] Add autocomplete for data streams (#214465)\n\nCloses https://github.com/elastic/kibana/issues/212905\n\n## Summary\n\nThis PR adds autocompletion for data-stream related endpoints.\nPreviously, it didn't work because the generated spec definitions that\nwere extracted from the Es specs repo were using the generic `{name}`\npattern instead of `{data_stream}`. In this PR, we override those\ndefinition files and specify the correct pattern.\n\n### How to test:\n\nTest the following endpoints and make sure that data stream names are\nsuggested:\n\n`GET _data_stream/{data_stream}/_stats`\n`DELETE _data_stream/{data_stream}/_lifecycle`\n`DELETE _data_stream/{data_stream}`\n`GET _data_stream/{dataStream}/_lifecycle`\n`GET _data_stream/{data_stream}`\n`POST _data_stream/_migrate/{data_stream}`\n`POST _data_stream/_promote/{data_stream}`\n`PUT _data_stream/{data_stream}/_lifecycle`","sha":"f89e03c286a7a7b1d26a7c4e5e6aeec6e3c2624c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Console","Team:Kibana Management","release_note:skip","v9.0.0","backport:prev-minor","v9.1.0","v8.19.0","v9.0.1"],"title":"[Console] Add autocomplete for data streams","number":214465,"url":"https://github.com/elastic/kibana/pull/214465","mergeCommit":{"message":"[Console] Add autocomplete for data streams (#214465)\n\nCloses https://github.com/elastic/kibana/issues/212905\n\n## Summary\n\nThis PR adds autocompletion for data-stream related endpoints.\nPreviously, it didn't work because the generated spec definitions that\nwere extracted from the Es specs repo were using the generic `{name}`\npattern instead of `{data_stream}`. In this PR, we override those\ndefinition files and specify the correct pattern.\n\n### How to test:\n\nTest the following endpoints and make sure that data stream names are\nsuggested:\n\n`GET _data_stream/{data_stream}/_stats`\n`DELETE _data_stream/{data_stream}/_lifecycle`\n`DELETE _data_stream/{data_stream}`\n`GET _data_stream/{dataStream}/_lifecycle`\n`GET _data_stream/{data_stream}`\n`POST _data_stream/_migrate/{data_stream}`\n`POST _data_stream/_promote/{data_stream}`\n`PUT _data_stream/{data_stream}/_lifecycle`","sha":"f89e03c286a7a7b1d26a7c4e5e6aeec6e3c2624c"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214465","number":214465,"mergeCommit":{"message":"[Console] Add autocomplete for data streams (#214465)\n\nCloses https://github.com/elastic/kibana/issues/212905\n\n## Summary\n\nThis PR adds autocompletion for data-stream related endpoints.\nPreviously, it didn't work because the generated spec definitions that\nwere extracted from the Es specs repo were using the generic `{name}`\npattern instead of `{data_stream}`. In this PR, we override those\ndefinition files and specify the correct pattern.\n\n### How to test:\n\nTest the following endpoints and make sure that data stream names are\nsuggested:\n\n`GET _data_stream/{data_stream}/_stats`\n`DELETE _data_stream/{data_stream}/_lifecycle`\n`DELETE _data_stream/{data_stream}`\n`GET _data_stream/{dataStream}/_lifecycle`\n`GET _data_stream/{data_stream}`\n`POST _data_stream/_migrate/{data_stream}`\n`POST _data_stream/_promote/{data_stream}`\n`PUT _data_stream/{data_stream}/_lifecycle`","sha":"f89e03c286a7a7b1d26a7c4e5e6aeec6e3c2624c"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Stoeva <59341489+ElenaStoeva@users.noreply.github.com> |
||
|
Kibana Machine
|
3d44c1d207
|
[9.0] [APM] remove unnecessary field service.environment from top dependency spans endpoint (#215321) (#215361)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM] remove unnecessary field service.environment from top dependency spans endpoint (#215321)](https://github.com/elastic/kibana/pull/215321) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T15:31:36Z","message":"[APM] remove unnecessary field service.environment from top dependency spans endpoint (#215321)\n\n## Summary\n\nFixes #215106\n\nThis PR removes `service.environment` as a required field for\n`getTopDependencySpans` endpoint.\nIt was not used at all, so it can be safely removed without adapting the\nUI.","sha":"8193e56970757edc96fef17b18c6accbc1fad0dd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","apm","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[APM] remove unnecessary field service.environment from top dependency spans endpoint","number":215321,"url":"https://github.com/elastic/kibana/pull/215321","mergeCommit":{"message":"[APM] remove unnecessary field service.environment from top dependency spans endpoint (#215321)\n\n## Summary\n\nFixes #215106\n\nThis PR removes `service.environment` as a required field for\n`getTopDependencySpans` endpoint.\nIt was not used at all, so it can be safely removed without adapting the\nUI.","sha":"8193e56970757edc96fef17b18c6accbc1fad0dd"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215321","number":215321,"mergeCommit":{"message":"[APM] remove unnecessary field service.environment from top dependency spans endpoint (#215321)\n\n## Summary\n\nFixes #215106\n\nThis PR removes `service.environment` as a required field for\n`getTopDependencySpans` endpoint.\nIt was not used at all, so it can be safely removed without adapting the\nUI.","sha":"8193e56970757edc96fef17b18c6accbc1fad0dd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co> |
||
|
Kibana Machine
|
da3bedee1c
|
[9.0] [Detection Engine] Rule Data View select uses Data View name for display (#214495) (#215355)
# Backport This will backport the following commits from `main` to `9.0`: - [[Detection Engine] Rule Data View select uses Data View name for display (#214495)](https://github.com/elastic/kibana/pull/214495) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Ryland Herrick","email":"ryalnd@gmail.com"},"sourceCommit":{"committedDate":"2025-03-20T15:01:26Z","message":"[Detection Engine] Rule Data View select uses Data View name for display (#214495)\n\n## Summary\n\nSupersedes #190936, and also addresses\nhttps://github.com/elastic/kibana/issues/137823. This mainly just\nrebases the changes introduced there to the latest `main`. I also\nnoticed that it originally had some unit tests, so I resurrected those\nas well. ~~I modified the copy as well, so nota bene @ARWNightingale~~\nAfter some discussion, we determined that an explicit UI note about this\nbehavior was unnecessary.\n\n\n## Screenshots\n\n<kbd>\n<img width=\"979\" alt=\"Screenshot 2025-03-13 at 5 24 42 PM\"\nsrc=\"https://github.com/user-attachments/assets/69da29bf-5504-461e-b797-d016adcd4b59\"\n/></kbd>\n\n<kbd><img width=\"1052\" alt=\"Screenshot 2025-03-18 at 4 37 58 PM\"\nsrc=\"https://github.com/user-attachments/assets/8ee5e55e-2413-4936-aa87-7dadb3d7cbb1\"\n/></kbd>\n\n\n\n\n### Checklist\n\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Yara Tercero <yara.tercero@elastic.co>","sha":"07acd2480aea52d22a5c5454740cd2a1fa7a70e8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Feature:Rule Creation","backport:all-open","Team:Detection Engine","Feature:Rule Edit","v9.1.0"],"title":"[Detection Engine] Rule Data View select uses Data View name for display","number":214495,"url":"https://github.com/elastic/kibana/pull/214495","mergeCommit":{"message":"[Detection Engine] Rule Data View select uses Data View name for display (#214495)\n\n## Summary\n\nSupersedes #190936, and also addresses\nhttps://github.com/elastic/kibana/issues/137823. This mainly just\nrebases the changes introduced there to the latest `main`. I also\nnoticed that it originally had some unit tests, so I resurrected those\nas well. ~~I modified the copy as well, so nota bene @ARWNightingale~~\nAfter some discussion, we determined that an explicit UI note about this\nbehavior was unnecessary.\n\n\n## Screenshots\n\n<kbd>\n<img width=\"979\" alt=\"Screenshot 2025-03-13 at 5 24 42 PM\"\nsrc=\"https://github.com/user-attachments/assets/69da29bf-5504-461e-b797-d016adcd4b59\"\n/></kbd>\n\n<kbd><img width=\"1052\" alt=\"Screenshot 2025-03-18 at 4 37 58 PM\"\nsrc=\"https://github.com/user-attachments/assets/8ee5e55e-2413-4936-aa87-7dadb3d7cbb1\"\n/></kbd>\n\n\n\n\n### Checklist\n\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Yara Tercero <yara.tercero@elastic.co>","sha":"07acd2480aea52d22a5c5454740cd2a1fa7a70e8"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214495","number":214495,"mergeCommit":{"message":"[Detection Engine] Rule Data View select uses Data View name for display (#214495)\n\n## Summary\n\nSupersedes #190936, and also addresses\nhttps://github.com/elastic/kibana/issues/137823. This mainly just\nrebases the changes introduced there to the latest `main`. I also\nnoticed that it originally had some unit tests, so I resurrected those\nas well. ~~I modified the copy as well, so nota bene @ARWNightingale~~\nAfter some discussion, we determined that an explicit UI note about this\nbehavior was unnecessary.\n\n\n## Screenshots\n\n<kbd>\n<img width=\"979\" alt=\"Screenshot 2025-03-13 at 5 24 42 PM\"\nsrc=\"https://github.com/user-attachments/assets/69da29bf-5504-461e-b797-d016adcd4b59\"\n/></kbd>\n\n<kbd><img width=\"1052\" alt=\"Screenshot 2025-03-18 at 4 37 58 PM\"\nsrc=\"https://github.com/user-attachments/assets/8ee5e55e-2413-4936-aa87-7dadb3d7cbb1\"\n/></kbd>\n\n\n\n\n### Checklist\n\n\n- [x] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n\n---------\n\nCo-authored-by: Yara Tercero <yara.tercero@elastic.co>","sha":"07acd2480aea52d22a5c5454740cd2a1fa7a70e8"}}]}] BACKPORT--> Co-authored-by: Ryland Herrick <ryalnd@gmail.com> |
||
|
Kibana Machine
|
bc9c01a0e0
|
[9.0] [SecuritySolution] Fix Data view refresh does not support the indexPattern parameter (#215151) (#215348)
# Backport This will backport the following commits from `main` to `9.0`: - [[SecuritySolution] Fix Data view refresh does not support the indexPattern parameter (#215151)](https://github.com/elastic/kibana/pull/215151) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T14:41:54Z","message":"[SecuritySolution] Fix Data view refresh does not support the indexPattern parameter (#215151)\n\n## Summary\n\nWhen the data view refresh API or task was executed, it was overwriting\nthe engine's additional `indexPattern`.\n\nThis PR updates the code to support `indexPattern` and ensures the user\nhas privileges for all indices.\n\nI extracted the merge function to add deduplicate logic.\n\n### How to reproduce it?\n* Create an entity store using the indexPatterns param\n* Call refresh dataview API (`POST\nkbn:api/entity_store/engines/apply_dataview_indices`)\n* It will apply the dataview and ignore the indexPatterns param\n\nAfter the fix, we should be able to update the indexPatterns param, and\nthe task that refreshes the index pattern should pick up the change\nproperly.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"42183d6039c1bb71b42642747f88493fbe591c2e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team: SecuritySolution","Theme: entity_analytics","Feature:Entity Analytics","Team:Entity Analytics","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[SecuritySolution] Fix Data view refresh does not support the indexPattern parameter","number":215151,"url":"https://github.com/elastic/kibana/pull/215151","mergeCommit":{"message":"[SecuritySolution] Fix Data view refresh does not support the indexPattern parameter (#215151)\n\n## Summary\n\nWhen the data view refresh API or task was executed, it was overwriting\nthe engine's additional `indexPattern`.\n\nThis PR updates the code to support `indexPattern` and ensures the user\nhas privileges for all indices.\n\nI extracted the merge function to add deduplicate logic.\n\n### How to reproduce it?\n* Create an entity store using the indexPatterns param\n* Call refresh dataview API (`POST\nkbn:api/entity_store/engines/apply_dataview_indices`)\n* It will apply the dataview and ignore the indexPatterns param\n\nAfter the fix, we should be able to update the indexPatterns param, and\nthe task that refreshes the index pattern should pick up the change\nproperly.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"42183d6039c1bb71b42642747f88493fbe591c2e"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215151","number":215151,"mergeCommit":{"message":"[SecuritySolution] Fix Data view refresh does not support the indexPattern parameter (#215151)\n\n## Summary\n\nWhen the data view refresh API or task was executed, it was overwriting\nthe engine's additional `indexPattern`.\n\nThis PR updates the code to support `indexPattern` and ensures the user\nhas privileges for all indices.\n\nI extracted the merge function to add deduplicate logic.\n\n### How to reproduce it?\n* Create an entity store using the indexPatterns param\n* Call refresh dataview API (`POST\nkbn:api/entity_store/engines/apply_dataview_indices`)\n* It will apply the dataview and ignore the indexPatterns param\n\nAfter the fix, we should be able to update the indexPatterns param, and\nthe task that refreshes the index pattern should pick up the change\nproperly.\n\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios","sha":"42183d6039c1bb71b42642747f88493fbe591c2e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Pablo Machado <pablo.nevesmachado@elastic.co> |
||
|
Kibana Machine
|
9ee8417961
|
[9.0] [Search] Fix code examples (#215286) (#215339)
# Backport This will backport the following commits from `main` to `9.0`: - [[Search] Fix code examples (#215286)](https://github.com/elastic/kibana/pull/215286) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sander Philipse","email":"94373878+sphilipse@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-20T13:46:10Z","message":"[Search] Fix code examples (#215286)\n\n## Summary\n\nThis fixes a couple small bugs in some of our Curl examples.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"9b6d1aa35d840eff8a211784966cba36aca5cf80","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","backport:prev-minor","v9.1.0"],"title":"[Search] Fix code examples","number":215286,"url":"https://github.com/elastic/kibana/pull/215286","mergeCommit":{"message":"[Search] Fix code examples (#215286)\n\n## Summary\n\nThis fixes a couple small bugs in some of our Curl examples.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"9b6d1aa35d840eff8a211784966cba36aca5cf80"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215286","number":215286,"mergeCommit":{"message":"[Search] Fix code examples (#215286)\n\n## Summary\n\nThis fixes a couple small bugs in some of our Curl examples.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nDoes this PR introduce any risks? For example, consider risks like hard\nto test bugs, performance regression, potential of data loss.\n\nDescribe the risk, its severity, and mitigation for each identified\nrisk. Invite stakeholders and evaluate how to proceed before merging.\n\n- [ ] [See some risk\nexamples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx)\n- [ ] ...","sha":"9b6d1aa35d840eff8a211784966cba36aca5cf80"}}]}] BACKPORT--> Co-authored-by: Sander Philipse <94373878+sphilipse@users.noreply.github.com> |
||
|
Kibana Machine
|
4c2a4b43d2
|
[9.0] [Synthetics] Retries journeys on failures !! (#215264) (#215311)
# Backport This will backport the following commits from `main` to `9.0`: - [[Synthetics] Retries journeys on failures !! (#215264)](https://github.com/elastic/kibana/pull/215264) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Shahzad","email":"shahzad31comp@gmail.com"},"sourceCommit":{"committedDate":"2025-03-20T10:53:55Z","message":"[Synthetics] Retries journeys on failures !! (#215264)\n\n## Summary\n\nRetries journeys on failures !!","sha":"0dad68dce78a21b74e5a946e494f8d2bf81c6822","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","ci:synthetics-runner-suites","v9.1.0","v8.19.0"],"title":"[Synthetics] Retries journeys on failures !!","number":215264,"url":"https://github.com/elastic/kibana/pull/215264","mergeCommit":{"message":"[Synthetics] Retries journeys on failures !! (#215264)\n\n## Summary\n\nRetries journeys on failures !!","sha":"0dad68dce78a21b74e5a946e494f8d2bf81c6822"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215264","number":215264,"mergeCommit":{"message":"[Synthetics] Retries journeys on failures !! (#215264)\n\n## Summary\n\nRetries journeys on failures !!","sha":"0dad68dce78a21b74e5a946e494f8d2bf81c6822"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Shahzad <shahzad31comp@gmail.com> |
||
|
Kibana Machine
|
2a9f2fabed
|
[9.0] Upgrade axios 1.8.3 in buildkite (#215203) (#215298)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade axios 1.8.3 in buildkite (#215203)](https://github.com/elastic/kibana/pull/215203) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Alex Szabo","email":"alex.szabo@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T09:58:41Z","message":"Upgrade axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to 1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in axios clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:all-open","v9.1.0"],"title":"Upgrade axios 1.8.3 in buildkite","number":215203,"url":"https://github.com/elastic/kibana/pull/215203","mergeCommit":{"message":"Upgrade axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to 1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in axios clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215203","number":215203,"mergeCommit":{"message":"Upgrade axios 1.8.3 in buildkite (#215203)\n\n## Summary\nUpgrade `axios` to 1.8.3 in Kibana's `.buildkite` subproject; disallow\nabsolute URLs in axios clients.","sha":"d8f6bd694b5004547623f506b3a3497bb556c2a1"}}]}] BACKPORT--> Co-authored-by: Alex Szabo <alex.szabo@elastic.co> |
||
|
Kibana Machine
|
e946fa76a2
|
[9.0] chore(security,codeql): exclude more dev/test folders from CodeQL scans (#215303) (#215317)
# Backport This will backport the following commits from `main` to `9.0`: - [chore(security,codeql): exclude more dev/test folders from CodeQL scans (#215303)](https://github.com/elastic/kibana/pull/215303) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Aleh Zasypkin","email":"aleh.zasypkin@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T11:05:16Z","message":"chore(security,codeql): exclude more dev/test folders from CodeQL scans (#215303)\n\n## Summary\n\nExclude more dev/test folders from CodeQL scans","sha":"38de01504bac45f793d59b9c135dc18b2ecf7199","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","release_note:skip","security","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"chore(security,codeql): exclude more dev/test folders from CodeQL scans","number":215303,"url":"https://github.com/elastic/kibana/pull/215303","mergeCommit":{"message":"chore(security,codeql): exclude more dev/test folders from CodeQL scans (#215303)\n\n## Summary\n\nExclude more dev/test folders from CodeQL scans","sha":"38de01504bac45f793d59b9c135dc18b2ecf7199"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215303","number":215303,"mergeCommit":{"message":"chore(security,codeql): exclude more dev/test folders from CodeQL scans (#215303)\n\n## Summary\n\nExclude more dev/test folders from CodeQL scans","sha":"38de01504bac45f793d59b9c135dc18b2ecf7199"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Aleh Zasypkin <aleh.zasypkin@elastic.co> |
||
|
Kibana Machine
|
838c33ec0f
|
[9.0] [Security Solution][Defend Workflows] Enables endpoint integrations FTR tests (#214120) (#215290)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Defend Workflows] Enables endpoint integrations FTR tests (#214120)](https://github.com/elastic/kibana/pull/214120) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Sánchez","email":"david.sanchezsoler@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T09:37:11Z","message":"[Security Solution][Defend Workflows] Enables endpoint integrations FTR tests (#214120)\n\n## Summary\n\nEnables endpoint integrations ftr test.\n\ncloses: https://github.com/elastic/kibana/issues/203916\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1119bf187dc04e130c3df610b5fdeb7301e40311","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Defend Workflows","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Solution][Defend Workflows] Enables endpoint integrations FTR tests","number":214120,"url":"https://github.com/elastic/kibana/pull/214120","mergeCommit":{"message":"[Security Solution][Defend Workflows] Enables endpoint integrations FTR tests (#214120)\n\n## Summary\n\nEnables endpoint integrations ftr test.\n\ncloses: https://github.com/elastic/kibana/issues/203916\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1119bf187dc04e130c3df610b5fdeb7301e40311"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214120","number":214120,"mergeCommit":{"message":"[Security Solution][Defend Workflows] Enables endpoint integrations FTR tests (#214120)\n\n## Summary\n\nEnables endpoint integrations ftr test.\n\ncloses: https://github.com/elastic/kibana/issues/203916\n\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"1119bf187dc04e130c3df610b5fdeb7301e40311"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: David Sánchez <david.sanchezsoler@elastic.co> |
||
|
Kibana Machine
|
5c23184786
|
[9.0] Fix APM URLs in doc link service (#215261) (#215284)
# Backport This will backport the following commits from `main` to `9.0`: - [Fix APM URLs in doc link service (#215261)](https://github.com/elastic/kibana/pull/215261) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-20T09:00:12Z","message":"Fix APM URLs in doc link service (#215261)","sha":"dcbefc3b27fc6733d0776ad371f5b2e4b0ad9e6e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"Fix APM URLs in doc link service","number":215261,"url":"https://github.com/elastic/kibana/pull/215261","mergeCommit":{"message":"Fix APM URLs in doc link service (#215261)","sha":"dcbefc3b27fc6733d0776ad371f5b2e4b0ad9e6e"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215261","number":215261,"mergeCommit":{"message":"Fix APM URLs in doc link service (#215261)","sha":"dcbefc3b27fc6733d0776ad371f5b2e4b0ad9e6e"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
Alex Szabo
|
3f408fcd5f | skip failing suite (#209024) | ||
|
Kibana Machine
|
a043700f59
|
[9.0] [Security Solution][Risk Score]Code changes for limiting the transformID length to 36 characters (#213405) (#215267)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Risk Score]Code changes for limiting the transformID length to 36 characters (#213405)](https://github.com/elastic/kibana/pull/213405) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-20T05:53:55Z","message":"[Security Solution][Risk Score]Code changes for limiting the transformID length to 36 characters (#213405)\n\n## Summary\n\nThe code changes in this PR ensure that the transform ID is limited to\n36 characters when creating or updating the transform for risk-score.\n\nThis adjustment aligns with ES constraint on transform ID length.\n\n\n## Test Steps\n\n1. Create a new namespace with a very long name. Ex :\n`namespace_that_stretches_farther_than_the_universe_and_beyond_like_buzz`\n🚀\n2. Enable the Risk Score in the new namespace. It should successfully\nget enabled.\n3. Check the transform that was created (using dev tools)\n\n```\nGET _transform/risk_score_latest_transform_*?filter_path=transforms.id,transforms._meta.space_id\n```\n\nOutput \n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Mark Hopkin <mark.hopkin@elastic.co>","sha":"a3f89ec2c25b1ca6a75a7bf41ac0360a3a887806","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Entity Analytics","backport:version","v9.1.0"],"title":"[Security Solution][Risk Score]Code changes for limiting the transformID length to 36 characters","number":213405,"url":"https://github.com/elastic/kibana/pull/213405","mergeCommit":{"message":"[Security Solution][Risk Score]Code changes for limiting the transformID length to 36 characters (#213405)\n\n## Summary\n\nThe code changes in this PR ensure that the transform ID is limited to\n36 characters when creating or updating the transform for risk-score.\n\nThis adjustment aligns with ES constraint on transform ID length.\n\n\n## Test Steps\n\n1. Create a new namespace with a very long name. Ex :\n`namespace_that_stretches_farther_than_the_universe_and_beyond_like_buzz`\n🚀\n2. Enable the Risk Score in the new namespace. It should successfully\nget enabled.\n3. Check the transform that was created (using dev tools)\n\n```\nGET _transform/risk_score_latest_transform_*?filter_path=transforms.id,transforms._meta.space_id\n```\n\nOutput \n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Mark Hopkin <mark.hopkin@elastic.co>","sha":"a3f89ec2c25b1ca6a75a7bf41ac0360a3a887806"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213405","number":213405,"mergeCommit":{"message":"[Security Solution][Risk Score]Code changes for limiting the transformID length to 36 characters (#213405)\n\n## Summary\n\nThe code changes in this PR ensure that the transform ID is limited to\n36 characters when creating or updating the transform for risk-score.\n\nThis adjustment aligns with ES constraint on transform ID length.\n\n\n## Test Steps\n\n1. Create a new namespace with a very long name. Ex :\n`namespace_that_stretches_farther_than_the_universe_and_beyond_like_buzz`\n🚀\n2. Enable the Risk Score in the new namespace. It should successfully\nget enabled.\n3. Check the transform that was created (using dev tools)\n\n```\nGET _transform/risk_score_latest_transform_*?filter_path=transforms.id,transforms._meta.space_id\n```\n\nOutput \n\n\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n---------\n\nCo-authored-by: Mark Hopkin <mark.hopkin@elastic.co>","sha":"a3f89ec2c25b1ca6a75a7bf41ac0360a3a887806"}}]}] BACKPORT--> Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com> |
||
|
Kibana Machine
|
12a8f3062c
|
[9.0] Added more request validation to entity store enablement (#212657) (#215257)
# Backport This will backport the following commits from `main` to `9.0`: - [Added more request validation to entity store enablement (#212657)](https://github.com/elastic/kibana/pull/212657) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jared Burgett","email":"147995946+jaredburgettelastic@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-19T23:31:31Z","message":"Added more request validation to entity store enablement (#212657)\n\n# Purpose\n\nThis change introduces new validations that ensure no loss of data is\npossible if a user accidentally sets the Security Entity Store enrich\npolicy execution interval to a value that “doesn’t play nicely” with the\nlookback period value.\n\nThe specific logic (greater than or equal to half the value) was chosen\nto not only ensure no loss of data, but also provide extra resiliency in\ncase of a failed enrich policy execution.\n\n(Note that this is not considered a breaking change, as the parameters\nare not yet available on any version of Elastic, including Serverless.)\n\n# How to test\n\n1. Load appropriate entity log data to your Kibana instance (for\nexample, using the\n[security-documents-generator](https://github.com/elastic/security-documents-generator))\n2. Navigate to the Developer console\n3. Attempt to enable the Entity Store via the /enable or /init routes\n(examples below), and pass in values that are expected to error. For\nexample, “lookbackPeriod”: “24h” and “enrichPolicyExecutionInterval”:\n“24h” should fail, because of the validation logic\n4. Expect results similar to those shown below, specifically a 400\nerror, or else a success message\n\n<img width=\"1902\" alt=\"Screenshot 2025-02-27 at 12 57 45 AM\"\nsrc=\"https://github.com/user-attachments/assets/a7f4b0fb-9899-4e00-a0ae-d172245bd506\"\n/>\n<img width=\"1909\" alt=\"Screenshot 2025-02-27 at 12 58 06 AM\"\nsrc=\"https://github.com/user-attachments/assets/372acde2-9d7b-4c75-8596-af8374088f79\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"64743b3a820e3af4478d78bb643fa3531b302aa6","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"Added more request validation to entity store enablement","number":212657,"url":"https://github.com/elastic/kibana/pull/212657","mergeCommit":{"message":"Added more request validation to entity store enablement (#212657)\n\n# Purpose\n\nThis change introduces new validations that ensure no loss of data is\npossible if a user accidentally sets the Security Entity Store enrich\npolicy execution interval to a value that “doesn’t play nicely” with the\nlookback period value.\n\nThe specific logic (greater than or equal to half the value) was chosen\nto not only ensure no loss of data, but also provide extra resiliency in\ncase of a failed enrich policy execution.\n\n(Note that this is not considered a breaking change, as the parameters\nare not yet available on any version of Elastic, including Serverless.)\n\n# How to test\n\n1. Load appropriate entity log data to your Kibana instance (for\nexample, using the\n[security-documents-generator](https://github.com/elastic/security-documents-generator))\n2. Navigate to the Developer console\n3. Attempt to enable the Entity Store via the /enable or /init routes\n(examples below), and pass in values that are expected to error. For\nexample, “lookbackPeriod”: “24h” and “enrichPolicyExecutionInterval”:\n“24h” should fail, because of the validation logic\n4. Expect results similar to those shown below, specifically a 400\nerror, or else a success message\n\n<img width=\"1902\" alt=\"Screenshot 2025-02-27 at 12 57 45 AM\"\nsrc=\"https://github.com/user-attachments/assets/a7f4b0fb-9899-4e00-a0ae-d172245bd506\"\n/>\n<img width=\"1909\" alt=\"Screenshot 2025-02-27 at 12 58 06 AM\"\nsrc=\"https://github.com/user-attachments/assets/372acde2-9d7b-4c75-8596-af8374088f79\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"64743b3a820e3af4478d78bb643fa3531b302aa6"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/212657","number":212657,"mergeCommit":{"message":"Added more request validation to entity store enablement (#212657)\n\n# Purpose\n\nThis change introduces new validations that ensure no loss of data is\npossible if a user accidentally sets the Security Entity Store enrich\npolicy execution interval to a value that “doesn’t play nicely” with the\nlookback period value.\n\nThe specific logic (greater than or equal to half the value) was chosen\nto not only ensure no loss of data, but also provide extra resiliency in\ncase of a failed enrich policy execution.\n\n(Note that this is not considered a breaking change, as the parameters\nare not yet available on any version of Elastic, including Serverless.)\n\n# How to test\n\n1. Load appropriate entity log data to your Kibana instance (for\nexample, using the\n[security-documents-generator](https://github.com/elastic/security-documents-generator))\n2. Navigate to the Developer console\n3. Attempt to enable the Entity Store via the /enable or /init routes\n(examples below), and pass in values that are expected to error. For\nexample, “lookbackPeriod”: “24h” and “enrichPolicyExecutionInterval”:\n“24h” should fail, because of the validation logic\n4. Expect results similar to those shown below, specifically a 400\nerror, or else a success message\n\n<img width=\"1902\" alt=\"Screenshot 2025-02-27 at 12 57 45 AM\"\nsrc=\"https://github.com/user-attachments/assets/a7f4b0fb-9899-4e00-a0ae-d172245bd506\"\n/>\n<img width=\"1909\" alt=\"Screenshot 2025-02-27 at 12 58 06 AM\"\nsrc=\"https://github.com/user-attachments/assets/372acde2-9d7b-4c75-8596-af8374088f79\"\n/>\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>","sha":"64743b3a820e3af4478d78bb643fa3531b302aa6"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Jared Burgett <147995946+jaredburgettelastic@users.noreply.github.com> |
||
|
Kibana Machine
|
f6876a4349
|
[9.0] [UII] Allow creating a new agentless integration to open status flyout automatically (#214503) (#214670)
# Backport This will backport the following commits from `main` to `9.0`: - [[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)](https://github.com/elastic/kibana/pull/214503) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jen Huang","email":"its.jenetic@gmail.com"},"sourceCommit":{"committedDate":"2025-03-14T22:10:38Z","message":"[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213958.\nRelated to https://github.com/elastic/kibana/pull/199567.\n\nThis PR makes it so that after adding an agentless integration, the\nagentless status flyout is opened automatically on the policies page.\nThis is done by passing the query parameter\n`?openEnrollmentFlyout=<agent policy id>` after successful creation:\n\n<img width=\"1440\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/720caab3-10dc-4c1e-bb9a-6a65eb5b5a48\"\n/>\n\n## Testing\n1. Add the following to kibana.dev.yml:\n```\nxpack.cloud.id: 'anything-to-pass-cloud-validation-checks'\nxpack.fleet.agentless.enabled: true\nxpack.fleet.agentless.api.url: 'https://localhost:8443'\nxpack.fleet.agentless.api.tls.certificate: './config/certs/ess-client.crt'\nxpack.fleet.agentless.api.tls.key: './config/certs/ess-client.key'\nxpack.fleet.agentless.api.tls.ca: './config/certs/ca.crt'\n```\n2. Apply [this\npatch](https://gist.github.com/jen-huang/dfc3e02ceb63976ad54bd1f50c524cb4)\nto prevent attempt to create agentless pod\n3. Enroll a Fleet Server as usual\n4. Go to CSPM integration, select agentless deployment mode\n5. After saving, you should be redirected to CSPM integration > Policies\ntable with the agentless status flyout open for the one that you just\ncreated\n\nDo some regression testing around other redirect scenarios, such as:\n* Agent-based CSPM -> manual (not cloudformation) should redirect to\nagent policy details page with enrollment flyout open after clicking\n\"Add agent now\"\n* Editing various integration policies redirect as expected (from\nintegration > policies table should redirect back to integration page,\nfrom agent policy details should redirect back to agent policy)\n* Creating various integration policies with none/one/multiple agent\npolicies should redirect as expected (none should redirect to\nintegrations page, one/multiple should redirect back to first agent\npolicy)","sha":"eb9e8173784aeecbcb4e6ab0828dd58a75b8ddb1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","v9.0.0","backport:version","v8.18.0","v9.1.0"],"title":"[UII] Allow creating a new agentless integration to open status flyout automatically","number":214503,"url":"https://github.com/elastic/kibana/pull/214503","mergeCommit":{"message":"[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213958.\nRelated to https://github.com/elastic/kibana/pull/199567.\n\nThis PR makes it so that after adding an agentless integration, the\nagentless status flyout is opened automatically on the policies page.\nThis is done by passing the query parameter\n`?openEnrollmentFlyout=<agent policy id>` after successful creation:\n\n<img width=\"1440\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/720caab3-10dc-4c1e-bb9a-6a65eb5b5a48\"\n/>\n\n## Testing\n1. Add the following to kibana.dev.yml:\n```\nxpack.cloud.id: 'anything-to-pass-cloud-validation-checks'\nxpack.fleet.agentless.enabled: true\nxpack.fleet.agentless.api.url: 'https://localhost:8443'\nxpack.fleet.agentless.api.tls.certificate: './config/certs/ess-client.crt'\nxpack.fleet.agentless.api.tls.key: './config/certs/ess-client.key'\nxpack.fleet.agentless.api.tls.ca: './config/certs/ca.crt'\n```\n2. Apply [this\npatch](https://gist.github.com/jen-huang/dfc3e02ceb63976ad54bd1f50c524cb4)\nto prevent attempt to create agentless pod\n3. Enroll a Fleet Server as usual\n4. Go to CSPM integration, select agentless deployment mode\n5. After saving, you should be redirected to CSPM integration > Policies\ntable with the agentless status flyout open for the one that you just\ncreated\n\nDo some regression testing around other redirect scenarios, such as:\n* Agent-based CSPM -> manual (not cloudformation) should redirect to\nagent policy details page with enrollment flyout open after clicking\n\"Add agent now\"\n* Editing various integration policies redirect as expected (from\nintegration > policies table should redirect back to integration page,\nfrom agent policy details should redirect back to agent policy)\n* Creating various integration policies with none/one/multiple agent\npolicies should redirect as expected (none should redirect to\nintegrations page, one/multiple should redirect back to first agent\npolicy)","sha":"eb9e8173784aeecbcb4e6ab0828dd58a75b8ddb1"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214503","number":214503,"mergeCommit":{"message":"[UII] Allow creating a new agentless integration to open status flyout automatically (#214503)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213958.\nRelated to https://github.com/elastic/kibana/pull/199567.\n\nThis PR makes it so that after adding an agentless integration, the\nagentless status flyout is opened automatically on the policies page.\nThis is done by passing the query parameter\n`?openEnrollmentFlyout=<agent policy id>` after successful creation:\n\n<img width=\"1440\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/720caab3-10dc-4c1e-bb9a-6a65eb5b5a48\"\n/>\n\n## Testing\n1. Add the following to kibana.dev.yml:\n```\nxpack.cloud.id: 'anything-to-pass-cloud-validation-checks'\nxpack.fleet.agentless.enabled: true\nxpack.fleet.agentless.api.url: 'https://localhost:8443'\nxpack.fleet.agentless.api.tls.certificate: './config/certs/ess-client.crt'\nxpack.fleet.agentless.api.tls.key: './config/certs/ess-client.key'\nxpack.fleet.agentless.api.tls.ca: './config/certs/ca.crt'\n```\n2. Apply [this\npatch](https://gist.github.com/jen-huang/dfc3e02ceb63976ad54bd1f50c524cb4)\nto prevent attempt to create agentless pod\n3. Enroll a Fleet Server as usual\n4. Go to CSPM integration, select agentless deployment mode\n5. After saving, you should be redirected to CSPM integration > Policies\ntable with the agentless status flyout open for the one that you just\ncreated\n\nDo some regression testing around other redirect scenarios, such as:\n* Agent-based CSPM -> manual (not cloudformation) should redirect to\nagent policy details page with enrollment flyout open after clicking\n\"Add agent now\"\n* Editing various integration policies redirect as expected (from\nintegration > policies table should redirect back to integration page,\nfrom agent policy details should redirect back to agent policy)\n* Creating various integration policies with none/one/multiple agent\npolicies should redirect as expected (none should redirect to\nintegrations page, one/multiple should redirect back to first agent\npolicy)","sha":"eb9e8173784aeecbcb4e6ab0828dd58a75b8ddb1"}}]}] BACKPORT--> Co-authored-by: Jen Huang <its.jenetic@gmail.com> |
||
|
Kibana Machine
|
1c10748cf4
|
[9.0] [Detection Engine][FTRs] Unskip some FTRs (#213605) (#214661)
# Backport This will backport the following commits from `main` to `9.0`: - [[Detection Engine][FTRs] Unskip some FTRs (#213605)](https://github.com/elastic/kibana/pull/213605) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Yara Tercero","email":"yctercero@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T20:28:48Z","message":"[Detection Engine][FTRs] Unskip some FTRs (#213605)\n\nAddresses https://github.com/elastic/kibana/issues/182878\n\nFixes some alert assignment RBAC tests so that they can be unskipped in\nMKI. Also adds some manual run tests to MKI that were skipped due to\nfeature flags not being supported, but feature is no longer behind\nfeature flag.","sha":"448a0364d1d329879e4e569d094e9072d558a3e3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Detection Engine","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[Detection Engine][FTRs] Unskip some FTRs","number":213605,"url":"https://github.com/elastic/kibana/pull/213605","mergeCommit":{"message":"[Detection Engine][FTRs] Unskip some FTRs (#213605)\n\nAddresses https://github.com/elastic/kibana/issues/182878\n\nFixes some alert assignment RBAC tests so that they can be unskipped in\nMKI. Also adds some manual run tests to MKI that were skipped due to\nfeature flags not being supported, but feature is no longer behind\nfeature flag.","sha":"448a0364d1d329879e4e569d094e9072d558a3e3"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213605","number":213605,"mergeCommit":{"message":"[Detection Engine][FTRs] Unskip some FTRs (#213605)\n\nAddresses https://github.com/elastic/kibana/issues/182878\n\nFixes some alert assignment RBAC tests so that they can be unskipped in\nMKI. Also adds some manual run tests to MKI that were skipped due to\nfeature flags not being supported, but feature is no longer behind\nfeature flag.","sha":"448a0364d1d329879e4e569d094e9072d558a3e3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Yara Tercero <yctercero@users.noreply.github.com> |
||
|
Kibana Machine
|
f993510052
|
[9.0] [ResponseOps] mustache lambdas for EncodeURI and EncodeURIComponent, take 2 (#213859) (#215235)
# Backport This will backport the following commits from `main` to `9.0`: - [[ResponseOps] mustache lambdas for EncodeURI and EncodeURIComponent, take 2 (#213859)](https://github.com/elastic/kibana/pull/213859) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patrick Mueller","email":"patrick.mueller@elastic.co"},"sourceCommit":{"committedDate":"2025-03-19T18:54:03Z","message":"[ResponseOps] mustache lambdas for EncodeURI and EncodeURIComponent, take 2 (#213859)\n\nresolves https://github.com/elastic/kibana/issues/168728\n\n## Release note\n\nAdds Mustache lambdas for alerting actions to encode URLs with\n`{{#EncodeURI}}` and `{{#EncodeURIComponent}}` using `encodeURI()` and\n`encodeURIComponent()`.\n\ndoc to update, in a separate PR:\nhttps://github.com/elastic/docs-content/issues/735","sha":"a3aaa04eba457e8d1696275c1bf6942b8e1544dd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:enhancement","Team:ResponseOps","backport:version","v9.1.0","v8.19.0","v8.18.1","v9.0.1"],"title":"[ResponseOps] mustache lambdas for EncodeURI and EncodeURIComponent, take 2","number":213859,"url":"https://github.com/elastic/kibana/pull/213859","mergeCommit":{"message":"[ResponseOps] mustache lambdas for EncodeURI and EncodeURIComponent, take 2 (#213859)\n\nresolves https://github.com/elastic/kibana/issues/168728\n\n## Release note\n\nAdds Mustache lambdas for alerting actions to encode URLs with\n`{{#EncodeURI}}` and `{{#EncodeURIComponent}}` using `encodeURI()` and\n`encodeURIComponent()`.\n\ndoc to update, in a separate PR:\nhttps://github.com/elastic/docs-content/issues/735","sha":"a3aaa04eba457e8d1696275c1bf6942b8e1544dd"}},"sourceBranch":"main","suggestedTargetBranches":["8.x","8.18","9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213859","number":213859,"mergeCommit":{"message":"[ResponseOps] mustache lambdas for EncodeURI and EncodeURIComponent, take 2 (#213859)\n\nresolves https://github.com/elastic/kibana/issues/168728\n\n## Release note\n\nAdds Mustache lambdas for alerting actions to encode URLs with\n`{{#EncodeURI}}` and `{{#EncodeURIComponent}}` using `encodeURI()` and\n`encodeURIComponent()`.\n\ndoc to update, in a separate PR:\nhttps://github.com/elastic/docs-content/issues/735","sha":"a3aaa04eba457e8d1696275c1bf6942b8e1544dd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Patrick Mueller <patrick.mueller@elastic.co> |
||
Brad White
|
1c41d899ca
|
[9.0] Upgrade to Storybook 8 (#195148) (#214680)
# Backport This will backport the following commits from `main` to `9.0`: - [Upgrade to Storybook 8 (#195148)](https://github.com/elastic/kibana/pull/195148) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Brad White","email":"Ikuni17@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-14T22:41:03Z","message":"Upgrade to Storybook 8 (#195148)\n\n## Summary\n\nDepends on #191106\nCloses #171591\n\nThis PR migrates Storybook from `6.x` to `8.x`. Please see the\n[migration\nguide](https://storybook.js.org/docs/migration-guide/from-older-version)\nfor an overview of the changes because there are many breaking changes\nwhich effect Kibana. The TODO list below is not inclusive of all the\nchanges.\n\n## Reviewers\n### Each commit contains all files changed for a specific codeowner,\nplease find your respective commit to make review easier.\n\nA **first step before code review** should be checking the [`Storybooks\nPreview`](https://ci-artifacts.kibana.dev/storybooks/pr-195148/index.html)\nfrom CI for any runtime or style issues which were missed. The preview\ncan be compared to a build from `main`\n[here](https://ci-artifacts.kibana.dev/storybooks/pr-212585/index.html).\nIt is worth noting that some stories have runtime issues which existed\nbefore this migration.\n\nMost stories appear to have been migrated properly, but the Operations\nteam does not have prior knowledge into every story. Some of the\nmigration was able to be automated through Storybook provided scripts.\nIt is possible this wasn't entirely correct due to the structure of some\nstories. Additionally, part of this migration is moving Storybook to\nWebpack 5 which changed how styles are being loaded.\n\n#### TODO\n- [x] Migrate `stories.mdx`\n- [x] storyshots\n- [x] [Migrate\npackages](https://storybook.js.org/docs/migration-guide/from-older-version#package-structure-changes)\nwhich were removed in `8.0`\n- [x] `react-doc-gen` resolution\n- [x] [Migrate\nblocks](https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#addon-docs-removed-deprecated-blocksjs-entry)\n- [x] Migrate deprecated `addon-knobs` to\n[addon-controls](https://www.npmjs.com/package/@storybook/addon-controls)\n- [x] React Fast Refresh support\n- [x] Watch flag callback\n- [x] `canvas` webpack\n- [x] Rerun CSF migrations for new stories\n- [x] Handle ESM import for `addon-docs`\n- [x] `'@storybook/addon-actions' should be listed in the project's\ndependencies. Run 'npm i -S @storybook/addon-actions' to add\niteslint[import/no-extraneous-dependencies](https://github.com/import-js/eslint-plugin-import/blob/v2.28.0/docs/rules/no-extraneous-dependencies.md)`\n- [x] `addDecorator` migration \n- [x] `addParameter` migration\n- [x] static build\n- [ ] determine if #176500 is solved or push to followup PR\n - This will need to be fixed separately\n- [x] revert `.buildkite/pipelines/pull_request/base.yml` &\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to `main`\n\n---------\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Clint Andrew Hall <clint@clintandrewhall.com>","sha":"403b5f23636d61809d23851f856ff0e26235b22f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","Team:Fleet","v9.0.0","ci:build-storybooks","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"Upgrade to Storybook 8","number":195148,"url":"https://github.com/elastic/kibana/pull/195148","mergeCommit":{"message":"Upgrade to Storybook 8 (#195148)\n\n## Summary\n\nDepends on #191106\nCloses #171591\n\nThis PR migrates Storybook from `6.x` to `8.x`. Please see the\n[migration\nguide](https://storybook.js.org/docs/migration-guide/from-older-version)\nfor an overview of the changes because there are many breaking changes\nwhich effect Kibana. The TODO list below is not inclusive of all the\nchanges.\n\n## Reviewers\n### Each commit contains all files changed for a specific codeowner,\nplease find your respective commit to make review easier.\n\nA **first step before code review** should be checking the [`Storybooks\nPreview`](https://ci-artifacts.kibana.dev/storybooks/pr-195148/index.html)\nfrom CI for any runtime or style issues which were missed. The preview\ncan be compared to a build from `main`\n[here](https://ci-artifacts.kibana.dev/storybooks/pr-212585/index.html).\nIt is worth noting that some stories have runtime issues which existed\nbefore this migration.\n\nMost stories appear to have been migrated properly, but the Operations\nteam does not have prior knowledge into every story. Some of the\nmigration was able to be automated through Storybook provided scripts.\nIt is possible this wasn't entirely correct due to the structure of some\nstories. Additionally, part of this migration is moving Storybook to\nWebpack 5 which changed how styles are being loaded.\n\n#### TODO\n- [x] Migrate `stories.mdx`\n- [x] storyshots\n- [x] [Migrate\npackages](https://storybook.js.org/docs/migration-guide/from-older-version#package-structure-changes)\nwhich were removed in `8.0`\n- [x] `react-doc-gen` resolution\n- [x] [Migrate\nblocks](https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#addon-docs-removed-deprecated-blocksjs-entry)\n- [x] Migrate deprecated `addon-knobs` to\n[addon-controls](https://www.npmjs.com/package/@storybook/addon-controls)\n- [x] React Fast Refresh support\n- [x] Watch flag callback\n- [x] `canvas` webpack\n- [x] Rerun CSF migrations for new stories\n- [x] Handle ESM import for `addon-docs`\n- [x] `'@storybook/addon-actions' should be listed in the project's\ndependencies. Run 'npm i -S @storybook/addon-actions' to add\niteslint[import/no-extraneous-dependencies](https://github.com/import-js/eslint-plugin-import/blob/v2.28.0/docs/rules/no-extraneous-dependencies.md)`\n- [x] `addDecorator` migration \n- [x] `addParameter` migration\n- [x] static build\n- [ ] determine if #176500 is solved or push to followup PR\n - This will need to be fixed separately\n- [x] revert `.buildkite/pipelines/pull_request/base.yml` &\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to `main`\n\n---------\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Clint Andrew Hall <clint@clintandrewhall.com>","sha":"403b5f23636d61809d23851f856ff0e26235b22f"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/195148","number":195148,"mergeCommit":{"message":"Upgrade to Storybook 8 (#195148)\n\n## Summary\n\nDepends on #191106\nCloses #171591\n\nThis PR migrates Storybook from `6.x` to `8.x`. Please see the\n[migration\nguide](https://storybook.js.org/docs/migration-guide/from-older-version)\nfor an overview of the changes because there are many breaking changes\nwhich effect Kibana. The TODO list below is not inclusive of all the\nchanges.\n\n## Reviewers\n### Each commit contains all files changed for a specific codeowner,\nplease find your respective commit to make review easier.\n\nA **first step before code review** should be checking the [`Storybooks\nPreview`](https://ci-artifacts.kibana.dev/storybooks/pr-195148/index.html)\nfrom CI for any runtime or style issues which were missed. The preview\ncan be compared to a build from `main`\n[here](https://ci-artifacts.kibana.dev/storybooks/pr-212585/index.html).\nIt is worth noting that some stories have runtime issues which existed\nbefore this migration.\n\nMost stories appear to have been migrated properly, but the Operations\nteam does not have prior knowledge into every story. Some of the\nmigration was able to be automated through Storybook provided scripts.\nIt is possible this wasn't entirely correct due to the structure of some\nstories. Additionally, part of this migration is moving Storybook to\nWebpack 5 which changed how styles are being loaded.\n\n#### TODO\n- [x] Migrate `stories.mdx`\n- [x] storyshots\n- [x] [Migrate\npackages](https://storybook.js.org/docs/migration-guide/from-older-version#package-structure-changes)\nwhich were removed in `8.0`\n- [x] `react-doc-gen` resolution\n- [x] [Migrate\nblocks](https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#addon-docs-removed-deprecated-blocksjs-entry)\n- [x] Migrate deprecated `addon-knobs` to\n[addon-controls](https://www.npmjs.com/package/@storybook/addon-controls)\n- [x] React Fast Refresh support\n- [x] Watch flag callback\n- [x] `canvas` webpack\n- [x] Rerun CSF migrations for new stories\n- [x] Handle ESM import for `addon-docs`\n- [x] `'@storybook/addon-actions' should be listed in the project's\ndependencies. Run 'npm i -S @storybook/addon-actions' to add\niteslint[import/no-extraneous-dependencies](https://github.com/import-js/eslint-plugin-import/blob/v2.28.0/docs/rules/no-extraneous-dependencies.md)`\n- [x] `addDecorator` migration \n- [x] `addParameter` migration\n- [x] static build\n- [ ] determine if #176500 is solved or push to followup PR\n - This will need to be fixed separately\n- [x] revert `.buildkite/pipelines/pull_request/base.yml` &\n`.buildkite/scripts/pipelines/pull_request/pipeline.ts` to `main`\n\n---------\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>\nCo-authored-by: Jacek Kolezynski <jacek.kolezynski@elastic.co>\nCo-authored-by: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>\nCo-authored-by: Clint Andrew Hall <clint@clintandrewhall.com>","sha":"403b5f23636d61809d23851f856ff0e26235b22f"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> |
||
|
Kibana Machine
|
5acd953a80
|
[9.0] Small fixes for alert & actions yaml file (#215218) (#215231)
# Backport This will backport the following commits from `main` to `9.0`: - [Small fixes for alert & actions yaml file (#215218)](https://github.com/elastic/kibana/pull/215218) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"David Kilfoyle","email":"41695641+kilfoyle@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-19T18:19:53Z","message":"Small fixes for alert & actions yaml file (#215218)\n\nThis updates the versioning tags in the Alert and Action settings yaml\nfile to use `all` instead of `ga`. I guess the former makes more sense\nsince these settings aren't newly GAed.\n\n\nThe PR also makes a couple of very minor content changes based on\nhttps://github.com/elastic/kibana/pull/214934","sha":"5d6bed8479bfad14b7ac5c0b98cb535527dcf94b","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","v9.0.0","backport:version","v9.1.0","v9.0.1"],"title":"Small fixes for alert & actions yaml file","number":215218,"url":"https://github.com/elastic/kibana/pull/215218","mergeCommit":{"message":"Small fixes for alert & actions yaml file (#215218)\n\nThis updates the versioning tags in the Alert and Action settings yaml\nfile to use `all` instead of `ga`. I guess the former makes more sense\nsince these settings aren't newly GAed.\n\n\nThe PR also makes a couple of very minor content changes based on\nhttps://github.com/elastic/kibana/pull/214934","sha":"5d6bed8479bfad14b7ac5c0b98cb535527dcf94b"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215218","number":215218,"mergeCommit":{"message":"Small fixes for alert & actions yaml file (#215218)\n\nThis updates the versioning tags in the Alert and Action settings yaml\nfile to use `all` instead of `ga`. I guess the former makes more sense\nsince these settings aren't newly GAed.\n\n\nThe PR also makes a couple of very minor content changes based on\nhttps://github.com/elastic/kibana/pull/214934","sha":"5d6bed8479bfad14b7ac5c0b98cb535527dcf94b"}}]}] BACKPORT--> Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> |
||
|
Kibana Machine
|
d10a4a0112
|
[9.0] [data.search] Add APM instrumentation to search route (#214280) (#215214)
# Backport This will backport the following commits from `main` to `9.0`: - [[data.search] Add APM instrumentation to search route (#214280)](https://github.com/elastic/kibana/pull/214280) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lukas Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-19T16:37:54Z","message":"[data.search] Add APM instrumentation to search route (#214280)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/208219.\n\nAdds APM instrumentation to the search route called by `data.search`\nservices. This was part of `bsearch` before it was removed but for some\nreason was never added to the search routes directly.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"423d331b3b8b333d71b7cbcf41e09158c83a9108","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Search","release_note:skip","Team:DataDiscovery","backport:prev-minor","apm:instrumentation","v9.1.0"],"title":"[data.search] Add APM instrumentation to search route","number":214280,"url":"https://github.com/elastic/kibana/pull/214280","mergeCommit":{"message":"[data.search] Add APM instrumentation to search route (#214280)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/208219.\n\nAdds APM instrumentation to the search route called by `data.search`\nservices. This was part of `bsearch` before it was removed but for some\nreason was never added to the search routes directly.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"423d331b3b8b333d71b7cbcf41e09158c83a9108"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214280","number":214280,"mergeCommit":{"message":"[data.search] Add APM instrumentation to search route (#214280)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/208219.\n\nAdds APM instrumentation to the search route called by `data.search`\nservices. This was part of `bsearch` before it was removed but for some\nreason was never added to the search routes directly.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"423d331b3b8b333d71b7cbcf41e09158c83a9108"}}]}] BACKPORT--> Co-authored-by: Lukas Olson <lukas@elastic.co> |
||
|
Kibana Machine
|
483f5ecffa
|
[9.0] [Custom threshold] Use createLazy instead of create when initializing searchSource (#213904) (#215211)
# Backport This will backport the following commits from `main` to `9.0`: - [[Custom threshold] Use createLazy instead of create when initializing searchSource (#213904)](https://github.com/elastic/kibana/pull/213904) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Maryam Saeidi","email":"maryam.saeidi@elastic.co"},"sourceCommit":{"committedDate":"2025-03-19T16:23:26Z","message":"[Custom threshold] Use createLazy instead of create when initializing searchSource (#213904)\n\n## Summary\n\nIn this PR, we use a similar approach as was introduced in the ES Query\nrule in this [PR](https://github.com/elastic/kibana/pull/183694) for the\ncustom threshold rule to reduce the field_caps traffic using createLazy.\n(Thanks @mikecote for pointing this out!)\n\n||Screenshot|\n|---|---|\n|Create (796\nms)||\n|CreateLazy (321\nms)||\n\n### 🧪 How to test\n- Enable APM locally\n```\nelastic.apm.active: true\nelastic.apm.transactionSampleRate: 1.0\nelastic.apm.environment: username\n```\n- Create a custom threshold rule and check its execution in\n[traces](https://kibana-cloud-apm.elastic.dev/app/apm/traces?rangeFrom=now-15m&rangeTo=now)\nfiltered for your `username` as the environment. There should be one\nwith your rule name:\n<img\nsrc=\"https://github.com/user-attachments/assets/59274acc-3edf-4de7-8870-3b175af73523\"\nwidth=500 />\n \nThe timing for `_field_caps` would be more if you replace the\n`createLazy` with the `create` function.","sha":"cc9494ccb057414d1eea9e27c51308854e521f05","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:obs-ux-management","backport:version","v9.1.0","v8.19.0","v8.18.1","v8.17.4"],"title":"[Custom threshold] Use createLazy instead of create when initializing searchSource","number":213904,"url":"https://github.com/elastic/kibana/pull/213904","mergeCommit":{"message":"[Custom threshold] Use createLazy instead of create when initializing searchSource (#213904)\n\n## Summary\n\nIn this PR, we use a similar approach as was introduced in the ES Query\nrule in this [PR](https://github.com/elastic/kibana/pull/183694) for the\ncustom threshold rule to reduce the field_caps traffic using createLazy.\n(Thanks @mikecote for pointing this out!)\n\n||Screenshot|\n|---|---|\n|Create (796\nms)||\n|CreateLazy (321\nms)||\n\n### 🧪 How to test\n- Enable APM locally\n```\nelastic.apm.active: true\nelastic.apm.transactionSampleRate: 1.0\nelastic.apm.environment: username\n```\n- Create a custom threshold rule and check its execution in\n[traces](https://kibana-cloud-apm.elastic.dev/app/apm/traces?rangeFrom=now-15m&rangeTo=now)\nfiltered for your `username` as the environment. There should be one\nwith your rule name:\n<img\nsrc=\"https://github.com/user-attachments/assets/59274acc-3edf-4de7-8870-3b175af73523\"\nwidth=500 />\n \nThe timing for `_field_caps` would be more if you replace the\n`createLazy` with the `create` function.","sha":"cc9494ccb057414d1eea9e27c51308854e521f05"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x","8.18","8.17"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213904","number":213904,"mergeCommit":{"message":"[Custom threshold] Use createLazy instead of create when initializing searchSource (#213904)\n\n## Summary\n\nIn this PR, we use a similar approach as was introduced in the ES Query\nrule in this [PR](https://github.com/elastic/kibana/pull/183694) for the\ncustom threshold rule to reduce the field_caps traffic using createLazy.\n(Thanks @mikecote for pointing this out!)\n\n||Screenshot|\n|---|---|\n|Create (796\nms)||\n|CreateLazy (321\nms)||\n\n### 🧪 How to test\n- Enable APM locally\n```\nelastic.apm.active: true\nelastic.apm.transactionSampleRate: 1.0\nelastic.apm.environment: username\n```\n- Create a custom threshold rule and check its execution in\n[traces](https://kibana-cloud-apm.elastic.dev/app/apm/traces?rangeFrom=now-15m&rangeTo=now)\nfiltered for your `username` as the environment. There should be one\nwith your rule name:\n<img\nsrc=\"https://github.com/user-attachments/assets/59274acc-3edf-4de7-8870-3b175af73523\"\nwidth=500 />\n \nThe timing for `_field_caps` would be more if you replace the\n`createLazy` with the `create` function.","sha":"cc9494ccb057414d1eea9e27c51308854e521f05"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.4","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Maryam Saeidi <maryam.saeidi@elastic.co> |
||
|
Kibana Machine
|
943300d05e
|
[9.0] [Security Solution][Endpoint] Adjust Artifacts policy assignment component in support of spaces (#214487) (#215194)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Endpoint] Adjust Artifacts policy assignment component in support of spaces (#214487)](https://github.com/elastic/kibana/pull/214487) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Paul Tavares","email":"56442535+paul-tavares@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-19T15:12:59Z","message":"[Security Solution][Endpoint] Adjust Artifacts policy assignment component in support of spaces (#214487)\n\n## Summary\n\n\n### Fleet\n\n- Exposed API route for bulk get package policies via the routes service\n- Created and exposed type `BulkGetPackagePoliciesRequestBody`\n\n<br/>\n\n\n### Security Solution\n\nThe following changes were made to Endpoint Artifacts in support of\nspaces:\n\n> [!NOTE]\n> Space awareness is currently behind feature flag:\n`endpointManagementSpaceAwarenessEnabled`\n\n\n- The policy assignment component, which is displayed on artifact's\nCreate and Update forms, now:\n- Displays the count of policies (if any) that are associated with the\nartifact, but not currently accessible in the active space (screen\ncapture 1️⃣ )\n- When a user does NOT have the Global Artifact privilege, the `Global`\ntoggle selection will be disabled and a tooltip is displayed. This\nchange also applies to the create form where the default selection will\nbe per-policy and the global button will be disabled. (screen capture\n2️⃣ )\n- Artifact policy assignments that are not accessible in active space\nare preserved when submitting an update to the artifact\n- The component was also refactored a bit to simplify its list of props\n- Artifact card policy assignment menu was adjusted to show any policy\nthat is not accessible to the user as \"disabled\" along with a tooltip\n(screen capture 3️⃣ )\n- The update artifact API was changed (via server-side extension point)\nto not error when validating policies that are not accessible in active\nspace if they were already associated with the item being updated.\n- Fixes a bug in the Find artifacts API (impact only when spaces was\nenabled) where an invalid filter was created when there was no policies\ncurrently shared with active space.","sha":"e11c3ecea5119202800d121a73765e26a41ff0a1","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","Team:Fleet","Team:Defend Workflows","backport:prev-minor","v9.1.0"],"title":"[Security Solution][Endpoint] Adjust Artifacts policy assignment component in support of spaces","number":214487,"url":"https://github.com/elastic/kibana/pull/214487","mergeCommit":{"message":"[Security Solution][Endpoint] Adjust Artifacts policy assignment component in support of spaces (#214487)\n\n## Summary\n\n\n### Fleet\n\n- Exposed API route for bulk get package policies via the routes service\n- Created and exposed type `BulkGetPackagePoliciesRequestBody`\n\n<br/>\n\n\n### Security Solution\n\nThe following changes were made to Endpoint Artifacts in support of\nspaces:\n\n> [!NOTE]\n> Space awareness is currently behind feature flag:\n`endpointManagementSpaceAwarenessEnabled`\n\n\n- The policy assignment component, which is displayed on artifact's\nCreate and Update forms, now:\n- Displays the count of policies (if any) that are associated with the\nartifact, but not currently accessible in the active space (screen\ncapture 1️⃣ )\n- When a user does NOT have the Global Artifact privilege, the `Global`\ntoggle selection will be disabled and a tooltip is displayed. This\nchange also applies to the create form where the default selection will\nbe per-policy and the global button will be disabled. (screen capture\n2️⃣ )\n- Artifact policy assignments that are not accessible in active space\nare preserved when submitting an update to the artifact\n- The component was also refactored a bit to simplify its list of props\n- Artifact card policy assignment menu was adjusted to show any policy\nthat is not accessible to the user as \"disabled\" along with a tooltip\n(screen capture 3️⃣ )\n- The update artifact API was changed (via server-side extension point)\nto not error when validating policies that are not accessible in active\nspace if they were already associated with the item being updated.\n- Fixes a bug in the Find artifacts API (impact only when spaces was\nenabled) where an invalid filter was created when there was no policies\ncurrently shared with active space.","sha":"e11c3ecea5119202800d121a73765e26a41ff0a1"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214487","number":214487,"mergeCommit":{"message":"[Security Solution][Endpoint] Adjust Artifacts policy assignment component in support of spaces (#214487)\n\n## Summary\n\n\n### Fleet\n\n- Exposed API route for bulk get package policies via the routes service\n- Created and exposed type `BulkGetPackagePoliciesRequestBody`\n\n<br/>\n\n\n### Security Solution\n\nThe following changes were made to Endpoint Artifacts in support of\nspaces:\n\n> [!NOTE]\n> Space awareness is currently behind feature flag:\n`endpointManagementSpaceAwarenessEnabled`\n\n\n- The policy assignment component, which is displayed on artifact's\nCreate and Update forms, now:\n- Displays the count of policies (if any) that are associated with the\nartifact, but not currently accessible in the active space (screen\ncapture 1️⃣ )\n- When a user does NOT have the Global Artifact privilege, the `Global`\ntoggle selection will be disabled and a tooltip is displayed. This\nchange also applies to the create form where the default selection will\nbe per-policy and the global button will be disabled. (screen capture\n2️⃣ )\n- Artifact policy assignments that are not accessible in active space\nare preserved when submitting an update to the artifact\n- The component was also refactored a bit to simplify its list of props\n- Artifact card policy assignment menu was adjusted to show any policy\nthat is not accessible to the user as \"disabled\" along with a tooltip\n(screen capture 3️⃣ )\n- The update artifact API was changed (via server-side extension point)\nto not error when validating policies that are not accessible in active\nspace if they were already associated with the item being updated.\n- Fixes a bug in the Find artifacts API (impact only when spaces was\nenabled) where an invalid filter was created when there was no policies\ncurrently shared with active space.","sha":"e11c3ecea5119202800d121a73765e26a41ff0a1"}}]}] BACKPORT--> Co-authored-by: Paul Tavares <56442535+paul-tavares@users.noreply.github.com> |
||
|
Kibana Machine
|
0d226d39c9
|
[9.0] [ObsUX] [APM] [OTel] Reduce python runtime metrics dashboard to otel_native (#215005) (#215191)
# Backport This will backport the following commits from `main` to `9.0`: - [[ObsUX] [APM] [OTel] Reduce python runtime metrics dashboard to otel_native (#215005)](https://github.com/elastic/kibana/pull/215005) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Riccardo Magliocchetti","email":"riccardo.magliocchetti@gmail.com"},"sourceCommit":{"committedDate":"2025-03-19T14:58:38Z","message":"[ObsUX] [APM] [OTel] Reduce python runtime metrics dashboard to otel_native (#215005)\n\n## Summary\n\nSince the GA supported path is the native OTel one, start simple with\njust that one.\nThis also renames the dashboard to match the dashboard triplet.\n\nThis is a follow up from #213599\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nThis reduce risks since it reduces the surface of changes from #213599","sha":"ea73a1aa1c5bf91cfe0f583678421f3bd8abbd12","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:prev-minor","backport:prev-major","Team:obs-ux-infra_services","v9.1.0"],"title":"[ObsUX] [APM] [OTel] Reduce python runtime metrics dashboard to otel_native","number":215005,"url":"https://github.com/elastic/kibana/pull/215005","mergeCommit":{"message":"[ObsUX] [APM] [OTel] Reduce python runtime metrics dashboard to otel_native (#215005)\n\n## Summary\n\nSince the GA supported path is the native OTel one, start simple with\njust that one.\nThis also renames the dashboard to match the dashboard triplet.\n\nThis is a follow up from #213599\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nThis reduce risks since it reduces the surface of changes from #213599","sha":"ea73a1aa1c5bf91cfe0f583678421f3bd8abbd12"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215005","number":215005,"mergeCommit":{"message":"[ObsUX] [APM] [OTel] Reduce python runtime metrics dashboard to otel_native (#215005)\n\n## Summary\n\nSince the GA supported path is the native OTel one, start simple with\njust that one.\nThis also renames the dashboard to match the dashboard triplet.\n\nThis is a follow up from #213599\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [ ] Any text added follows [EUI's writing\nguidelines](https://elastic.github.io/eui/#/guidelines/writing), uses\nsentence case text and includes [i18n\nsupport](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md)\n- [ ]\n[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)\nwas added for features that require explanation or tutorials\n- [ ] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] If a plugin configuration key changed, check if it needs to be\nallowlisted in the cloud and added to the [docker\nlist](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker)\n- [ ] This was checked for breaking HTTP API changes, and any breaking\nchanges have been approved by the breaking-change committee. The\n`release_note:breaking` label should be applied in these situations.\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [ ] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\n### Identify risks\n\nThis reduce risks since it reduces the surface of changes from #213599","sha":"ea73a1aa1c5bf91cfe0f583678421f3bd8abbd12"}}]}] BACKPORT--> Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com> |
||
elastic-renovate-prod[bot]
|
583ff275aa
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to c4e10ec (9.0) (#215078)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `5ba5def` -> `c4e10ec` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
06f444a197
|
[9.0] [Security Solution] [Detections] Use preview route for testing EQL shard failure (#214284) (#215166)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution] [Detections] Use preview route for testing EQL shard failure (#214284)](https://github.com/elastic/kibana/pull/214284) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Devin W. Hurley","email":"devin.hurley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-19T13:12:38Z","message":"[Security Solution] [Detections] Use preview route for testing EQL shard failure (#214284)\n\nfixes flakey test https://github.com/elastic/kibana/issues/209024\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"cd491c34e79b65641e00f95cf8120557a407a338","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["review","release_note:skip","v9.0.0","Team:Detection Engine","backport:version","v9.1.0","v9.0.1"],"title":"[Security Solution] [Detections] Use preview route for testing EQL shard failure","number":214284,"url":"https://github.com/elastic/kibana/pull/214284","mergeCommit":{"message":"[Security Solution] [Detections] Use preview route for testing EQL shard failure (#214284)\n\nfixes flakey test https://github.com/elastic/kibana/issues/209024\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"cd491c34e79b65641e00f95cf8120557a407a338"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214284","number":214284,"mergeCommit":{"message":"[Security Solution] [Detections] Use preview route for testing EQL shard failure (#214284)\n\nfixes flakey test https://github.com/elastic/kibana/issues/209024\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed","sha":"cd491c34e79b65641e00f95cf8120557a407a338"}}]}] BACKPORT--> Co-authored-by: Devin W. Hurley <devin.hurley@elastic.co> |
||
|
Kibana Machine
|
6c0c502e8e
|
[9.0] [APM] Prevent getChildrenGroupedByParentId to include the parent in the children list (#214957) (#215153)
# Backport This will backport the following commits from `main` to `9.0`: - [[APM] Prevent `getChildrenGroupedByParentId` to include the parent in the children list (#214957)](https://github.com/elastic/kibana/pull/214957) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Sergi Romeu","email":"sergi.romeu@elastic.co"},"sourceCommit":{"committedDate":"2025-03-19T12:28:20Z","message":"[APM] Prevent `getChildrenGroupedByParentId` to include the parent in the children list (#214957)\n\n## Summary\n\nCloses #213074\n\nThis PR prevents `getChildrenGroupedByParentId` to include the parent\nitem in the children list, as this was causing some duplication.\n\n| Before | After |\n\n|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|\n<img width=\"1433\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/788684a8-21d7-48a6-820c-07b1fb3d0045\"\n/>|<img width=\"858\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b68129e1-137d-42fe-a7ce-70373447ece9\"\n/>|\n|<img width=\"1372\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ff6a5ac8-b46a-4eea-9c4c-638f4b479dc8\"\n/>|<img width=\"844\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/31ef881c-a6d0-41ea-80d4-aebd587e76cd\"\n/>|","sha":"0ee664a555d860b045291b5757bafce33decedb3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:obs-ux-infra_services","backport:version","v9.1.0","v8.19.0","v9.0.1"],"title":"[APM] Prevent `getChildrenGroupedByParentId` to include the parent in the children list","number":214957,"url":"https://github.com/elastic/kibana/pull/214957","mergeCommit":{"message":"[APM] Prevent `getChildrenGroupedByParentId` to include the parent in the children list (#214957)\n\n## Summary\n\nCloses #213074\n\nThis PR prevents `getChildrenGroupedByParentId` to include the parent\nitem in the children list, as this was causing some duplication.\n\n| Before | After |\n\n|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|\n<img width=\"1433\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/788684a8-21d7-48a6-820c-07b1fb3d0045\"\n/>|<img width=\"858\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b68129e1-137d-42fe-a7ce-70373447ece9\"\n/>|\n|<img width=\"1372\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ff6a5ac8-b46a-4eea-9c4c-638f4b479dc8\"\n/>|<img width=\"844\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/31ef881c-a6d0-41ea-80d4-aebd587e76cd\"\n/>|","sha":"0ee664a555d860b045291b5757bafce33decedb3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214957","number":214957,"mergeCommit":{"message":"[APM] Prevent `getChildrenGroupedByParentId` to include the parent in the children list (#214957)\n\n## Summary\n\nCloses #213074\n\nThis PR prevents `getChildrenGroupedByParentId` to include the parent\nitem in the children list, as this was causing some duplication.\n\n| Before | After |\n\n|-------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------|\n<img width=\"1433\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/788684a8-21d7-48a6-820c-07b1fb3d0045\"\n/>|<img width=\"858\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/b68129e1-137d-42fe-a7ce-70373447ece9\"\n/>|\n|<img width=\"1372\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/ff6a5ac8-b46a-4eea-9c4c-638f4b479dc8\"\n/>|<img width=\"844\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/31ef881c-a6d0-41ea-80d4-aebd587e76cd\"\n/>|","sha":"0ee664a555d860b045291b5757bafce33decedb3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Sergi Romeu <sergi.romeu@elastic.co> |
||
|
Kibana Machine
|
d6aebc9561
|
[9.0] [Security Solution][Entity Analytics][Bug][Risk Score]Changes to replace 30m to 30d for Risk score lookback period (#215093) (#215147)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Entity Analytics][Bug][Risk Score]Changes to replace 30m to 30d for Risk score lookback period (#215093)](https://github.com/elastic/kibana/pull/215093) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Abhishek Bhatia","email":"117628830+abhishekbhatia1710@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-19T11:46:24Z","message":"[Security Solution][Entity Analytics][Bug][Risk Score]Changes to replace 30m to 30d for Risk score lookback period (#215093)\n\n## Summary\n\nThe PR updates the code to extend the lookback period for Risk scoring\ncalculations from `now-30m` to `now-30d`.\n\nThis change impacts: \n- Risk score UI (date picker)\n- The preview API \n- The enable API (for Risk Score Saved Object configuration)\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\nScreenshots : \n\n## UI and Preview API payload\n\n\n\n\n## Risk Engine configuration SO\n\n\n\n\n\n## Testing Steps:\n\n1. Navigate to the Entity Analytics management page (Entity Risk Score\nwebpage).\n2. Ensure the default text in the date picker displays **\"Last 30\ndays\"**.\n3. Open the **Network** tab in Developer Tools and verify that the\n**\"preview\"** API request reflects a 30-day difference between the\n`from` and `to` values.\n4. If the **Risk Engine** is enabled, disable it and open a window\ndisplaying Kibana logs.\n5. Re-enable the **Risk Engine** and check the logs for the\nconfiguration message: **\"Risk engine running with configuration\"**. The\nexpected range should be:\n ```json\n \"range\": {\n \"start\": \"now/M\",\n \"end\": \"now\"\n }\n ```\n\n\n## Advanced Testing Steps \n\n1. The date picker should default to **\"Last 30 days\"**. If you change\nit to **\"Yesterday\"** without clicking **Save changes**, the **Preview\nAPI** should reflect \"Yesterday,\" but the **Saved Object (SO)** should\n**not** update its range.\n2. Upon refreshing the page without saving the changes, the date picker\nshould reset to its default value, **\"Last 30 days\"**.","sha":"90dd368e71f3fce950607df3ec486289b408a6af","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","v9.0.0","Team:Entity Analytics","backport:version","v8.17.0","v8.18.0","v9.1.0"],"title":"[Security Solution][Entity Analytics][Bug][Risk Score]Changes to replace 30m to 30d for Risk score lookback period","number":215093,"url":"https://github.com/elastic/kibana/pull/215093","mergeCommit":{"message":"[Security Solution][Entity Analytics][Bug][Risk Score]Changes to replace 30m to 30d for Risk score lookback period (#215093)\n\n## Summary\n\nThe PR updates the code to extend the lookback period for Risk scoring\ncalculations from `now-30m` to `now-30d`.\n\nThis change impacts: \n- Risk score UI (date picker)\n- The preview API \n- The enable API (for Risk Score Saved Object configuration)\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\nScreenshots : \n\n## UI and Preview API payload\n\n\n\n\n## Risk Engine configuration SO\n\n\n\n\n\n## Testing Steps:\n\n1. Navigate to the Entity Analytics management page (Entity Risk Score\nwebpage).\n2. Ensure the default text in the date picker displays **\"Last 30\ndays\"**.\n3. Open the **Network** tab in Developer Tools and verify that the\n**\"preview\"** API request reflects a 30-day difference between the\n`from` and `to` values.\n4. If the **Risk Engine** is enabled, disable it and open a window\ndisplaying Kibana logs.\n5. Re-enable the **Risk Engine** and check the logs for the\nconfiguration message: **\"Risk engine running with configuration\"**. The\nexpected range should be:\n ```json\n \"range\": {\n \"start\": \"now/M\",\n \"end\": \"now\"\n }\n ```\n\n\n## Advanced Testing Steps \n\n1. The date picker should default to **\"Last 30 days\"**. If you change\nit to **\"Yesterday\"** without clicking **Save changes**, the **Preview\nAPI** should reflect \"Yesterday,\" but the **Saved Object (SO)** should\n**not** update its range.\n2. Upon refreshing the page without saving the changes, the date picker\nshould reset to its default value, **\"Last 30 days\"**.","sha":"90dd368e71f3fce950607df3ec486289b408a6af"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.17","8.18"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215093","number":215093,"mergeCommit":{"message":"[Security Solution][Entity Analytics][Bug][Risk Score]Changes to replace 30m to 30d for Risk score lookback period (#215093)\n\n## Summary\n\nThe PR updates the code to extend the lookback period for Risk scoring\ncalculations from `now-30m` to `now-30d`.\n\nThis change impacts: \n- Risk score UI (date picker)\n- The preview API \n- The enable API (for Risk Score Saved Object configuration)\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\n\nScreenshots : \n\n## UI and Preview API payload\n\n\n\n\n## Risk Engine configuration SO\n\n\n\n\n\n## Testing Steps:\n\n1. Navigate to the Entity Analytics management page (Entity Risk Score\nwebpage).\n2. Ensure the default text in the date picker displays **\"Last 30\ndays\"**.\n3. Open the **Network** tab in Developer Tools and verify that the\n**\"preview\"** API request reflects a 30-day difference between the\n`from` and `to` values.\n4. If the **Risk Engine** is enabled, disable it and open a window\ndisplaying Kibana logs.\n5. Re-enable the **Risk Engine** and check the logs for the\nconfiguration message: **\"Risk engine running with configuration\"**. The\nexpected range should be:\n ```json\n \"range\": {\n \"start\": \"now/M\",\n \"end\": \"now\"\n }\n ```\n\n\n## Advanced Testing Steps \n\n1. The date picker should default to **\"Last 30 days\"**. If you change\nit to **\"Yesterday\"** without clicking **Save changes**, the **Preview\nAPI** should reflect \"Yesterday,\" but the **Saved Object (SO)** should\n**not** update its range.\n2. Upon refreshing the page without saving the changes, the date picker\nshould reset to its default value, **\"Last 30 days\"**.","sha":"90dd368e71f3fce950607df3ec486289b408a6af"}}]}] BACKPORT--> Co-authored-by: Abhishek Bhatia <117628830+abhishekbhatia1710@users.noreply.github.com> |
||
|
Kibana Machine
|
d6ad0ec48f
|
[9.0] Add strip unkowns to nested objects in maps, arrays and records (#214978) (#215129)
# Backport This will backport the following commits from `main` to `9.0`: - [Add strip unkowns to nested objects in maps, arrays and records (#214978)](https://github.com/elastic/kibana/pull/214978) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Jesus Wahrman","email":"41008968+jesuswr@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-19T10:38:31Z","message":"Add strip unkowns to nested objects in maps, arrays and records (#214978)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/210617\n\nAdded strip unkowns to nested objects in map, array and record. Added a\nlot of test cases to cover things like objects inside maps, objects\ninside records, objects inside maps inside records, ...\n\nOne thing to note is that we can't apply `stripUnkowns` to\n`schema.oneOf` since it's using `joi.alternatives` and you can't use it\nthere.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"e14369edabf3d4160dc777e3ab190c8a62aeab7e","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","release_note:skip","backport:prev-major","kbn/config-schema","backport:current-major","v9.1.0"],"title":"Add strip unkowns to nested objects in maps, arrays and records","number":214978,"url":"https://github.com/elastic/kibana/pull/214978","mergeCommit":{"message":"Add strip unkowns to nested objects in maps, arrays and records (#214978)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/210617\n\nAdded strip unkowns to nested objects in map, array and record. Added a\nlot of test cases to cover things like objects inside maps, objects\ninside records, objects inside maps inside records, ...\n\nOne thing to note is that we can't apply `stripUnkowns` to\n`schema.oneOf` since it's using `joi.alternatives` and you can't use it\nthere.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"e14369edabf3d4160dc777e3ab190c8a62aeab7e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214978","number":214978,"mergeCommit":{"message":"Add strip unkowns to nested objects in maps, arrays and records (#214978)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/210617\n\nAdded strip unkowns to nested objects in map, array and record. Added a\nlot of test cases to cover things like objects inside maps, objects\ninside records, objects inside maps inside records, ...\n\nOne thing to note is that we can't apply `stripUnkowns` to\n`schema.oneOf` since it's using `joi.alternatives` and you can't use it\nthere.\n\n\n### Checklist\n\nCheck the PR satisfies following conditions. \n\nReviewers should verify this PR satisfies this list as well.\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"e14369edabf3d4160dc777e3ab190c8a62aeab7e"}}]}] BACKPORT--> Co-authored-by: Jesus Wahrman <41008968+jesuswr@users.noreply.github.com> |
||
|
Kibana Machine
|
35100fdb73
|
[9.0] [scout] add 'apiServices' fixture to group Kibana API helpers (#214470) (#215123)
# Backport This will backport the following commits from `main` to `9.0`: - [[scout] add 'apiServices' fixture to group Kibana API helpers (#214470)](https://github.com/elastic/kibana/pull/214470) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T11:34:25Z","message":"[scout] add 'apiServices' fixture to group Kibana API helpers (#214470)\n\n## Summary\n\nWe decided to group `Kibana API helpers` under a single fixture:\n`apiServices` instead of individual fixtures. It should simplify the\nsearch of existing helpers and reduce a risk for Teams to create the\nsame helper like we see today with FTR.\nAdding just `apiServices` in test context and adding dot will expand a\nlist of all available API helpers + it can be extended for individual\nsolution (e.g. @kbn/scout-oblt) and directly in plugin (if there is no\nchance to re-use it in other plugins)\n\n<img width=\"699\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34a76659-04af-48c4-ab69-abda0c950206\"\n/>\n\n\nBefore:\n\n```\ntest('should create something', async ({\n fleetApi,\n onboardingApi,\n alertingApi,\n }) => {\n await fleetApi.integration.install(integrationName);\n await onboardingApi.updateInstallationStepStatus(\n onboardingId,\n 'ea-download',\n 'complete'\n );\n await alertingApi.waitForAlert(alertId);\n```\n\nAfter:\n\n```\ntest('should create something', async ({\n apiServices,\n }) => {\n await apiServices.fleet.integration.install(integrationName);\n await apiServices.onboarding.updateInstallationStepStatus(\n onboardingId,\n 'ea-download',\n 'complete'\n );\n await apiServices.alerting.waitForAlert(alertId);\n```","sha":"48cd2075f75386b515e19567095c03a8ca73fe20","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] add 'apiServices' fixture to group Kibana API helpers","number":214470,"url":"https://github.com/elastic/kibana/pull/214470","mergeCommit":{"message":"[scout] add 'apiServices' fixture to group Kibana API helpers (#214470)\n\n## Summary\n\nWe decided to group `Kibana API helpers` under a single fixture:\n`apiServices` instead of individual fixtures. It should simplify the\nsearch of existing helpers and reduce a risk for Teams to create the\nsame helper like we see today with FTR.\nAdding just `apiServices` in test context and adding dot will expand a\nlist of all available API helpers + it can be extended for individual\nsolution (e.g. @kbn/scout-oblt) and directly in plugin (if there is no\nchance to re-use it in other plugins)\n\n<img width=\"699\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34a76659-04af-48c4-ab69-abda0c950206\"\n/>\n\n\nBefore:\n\n```\ntest('should create something', async ({\n fleetApi,\n onboardingApi,\n alertingApi,\n }) => {\n await fleetApi.integration.install(integrationName);\n await onboardingApi.updateInstallationStepStatus(\n onboardingId,\n 'ea-download',\n 'complete'\n );\n await alertingApi.waitForAlert(alertId);\n```\n\nAfter:\n\n```\ntest('should create something', async ({\n apiServices,\n }) => {\n await apiServices.fleet.integration.install(integrationName);\n await apiServices.onboarding.updateInstallationStepStatus(\n onboardingId,\n 'ea-download',\n 'complete'\n );\n await apiServices.alerting.waitForAlert(alertId);\n```","sha":"48cd2075f75386b515e19567095c03a8ca73fe20"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214470","number":214470,"mergeCommit":{"message":"[scout] add 'apiServices' fixture to group Kibana API helpers (#214470)\n\n## Summary\n\nWe decided to group `Kibana API helpers` under a single fixture:\n`apiServices` instead of individual fixtures. It should simplify the\nsearch of existing helpers and reduce a risk for Teams to create the\nsame helper like we see today with FTR.\nAdding just `apiServices` in test context and adding dot will expand a\nlist of all available API helpers + it can be extended for individual\nsolution (e.g. @kbn/scout-oblt) and directly in plugin (if there is no\nchance to re-use it in other plugins)\n\n<img width=\"699\" alt=\"image\"\nsrc=\"https://github.com/user-attachments/assets/34a76659-04af-48c4-ab69-abda0c950206\"\n/>\n\n\nBefore:\n\n```\ntest('should create something', async ({\n fleetApi,\n onboardingApi,\n alertingApi,\n }) => {\n await fleetApi.integration.install(integrationName);\n await onboardingApi.updateInstallationStepStatus(\n onboardingId,\n 'ea-download',\n 'complete'\n );\n await alertingApi.waitForAlert(alertId);\n```\n\nAfter:\n\n```\ntest('should create something', async ({\n apiServices,\n }) => {\n await apiServices.fleet.integration.install(integrationName);\n await apiServices.onboarding.updateInstallationStepStatus(\n onboardingId,\n 'ea-download',\n 'complete'\n );\n await apiServices.alerting.waitForAlert(alertId);\n```","sha":"48cd2075f75386b515e19567095c03a8ca73fe20"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
|
Kibana Machine
|
882c4cd297
|
[9.0] [scout] support login with a custom role (#213798) (#215118)
# Backport This will backport the following commits from `main` to `9.0`: - [[scout] support login with a custom role (#213798)](https://github.com/elastic/kibana/pull/213798) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-19T09:50:32Z","message":"[scout] support login with a custom role (#213798)\n\n## Summary\n\nAdding custom roles support in Scout UI tests\n\nExample:\n\n```\n test.beforeEach(async ({ browserAuth, pageObjects }) => {\n await browserAuth.loginWithCustomRole({\n elasticsearch: {\n cluster: ['manage'],\n indices: [\n {\n names: ['.siem-signals*', '.lists-*', '.items-*'],\n privileges: ['read', 'view_index_metadata'],\n allow_restricted_indices: false,\n },\n {\n names: ['.alerts*', '.preview.alerts*'],\n privileges: ['read', 'view_index_metadata'],\n allow_restricted_indices: false,\n },\n ],\n },\n kibana: [\n {\n base: [],\n feature: {\n siemV2: ['read', 'read_alerts'],\n },\n spaces: ['*'],\n },\n ],\n });\n await pageObjects.dashboard.goto();\n```\n\nIn `kbn/scout-security` to login as `platform_engineer` we will need to\noverride browser auth fixture with smth like:\n\n```ts\nconst resourcePath = path.resolve(SERVERLESS_ROLES_ROOT_PATH, 'security', 'roles.yml');\nconst svlRoleDescriptors = new Map<string, any>(\n Object.entries(readRolesDescriptorsFromResource(resourcePath) as Record<string, unknown>)\n);\n\nconst loginAsPlatformEngineer = async () => {\n const roleName = 'platform_engineer';\n if (!serverless) {\n const roleDesciptor = svlRoleDescriptors?.get(roleName) as ElasticsearchRoleDescriptor;\n if (!roleDesciptor) {\n throw new Error(`No role descriptors found for ${roleName}`);\n }\n await samlAuth.setCustomRole(roleDesciptor);\n return loginAs(samlAuth.customRoleName);\n } else {\n await loginAs(roleName);\n }\n}\n```\n\nThis way we gonna use custom role to replicate serverless default roles\nin Stateful run (and support deployment agnostic approach)\n\n---------\n\nCo-authored-by: Cesare de Cal <cesare.decal@elastic.co>","sha":"ef32357d80162e873095a279a1552f29f30ed9f3","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:version","test:scout","v9.1.0","v8.19.0"],"title":"[scout] support login with a custom role","number":213798,"url":"https://github.com/elastic/kibana/pull/213798","mergeCommit":{"message":"[scout] support login with a custom role (#213798)\n\n## Summary\n\nAdding custom roles support in Scout UI tests\n\nExample:\n\n```\n test.beforeEach(async ({ browserAuth, pageObjects }) => {\n await browserAuth.loginWithCustomRole({\n elasticsearch: {\n cluster: ['manage'],\n indices: [\n {\n names: ['.siem-signals*', '.lists-*', '.items-*'],\n privileges: ['read', 'view_index_metadata'],\n allow_restricted_indices: false,\n },\n {\n names: ['.alerts*', '.preview.alerts*'],\n privileges: ['read', 'view_index_metadata'],\n allow_restricted_indices: false,\n },\n ],\n },\n kibana: [\n {\n base: [],\n feature: {\n siemV2: ['read', 'read_alerts'],\n },\n spaces: ['*'],\n },\n ],\n });\n await pageObjects.dashboard.goto();\n```\n\nIn `kbn/scout-security` to login as `platform_engineer` we will need to\noverride browser auth fixture with smth like:\n\n```ts\nconst resourcePath = path.resolve(SERVERLESS_ROLES_ROOT_PATH, 'security', 'roles.yml');\nconst svlRoleDescriptors = new Map<string, any>(\n Object.entries(readRolesDescriptorsFromResource(resourcePath) as Record<string, unknown>)\n);\n\nconst loginAsPlatformEngineer = async () => {\n const roleName = 'platform_engineer';\n if (!serverless) {\n const roleDesciptor = svlRoleDescriptors?.get(roleName) as ElasticsearchRoleDescriptor;\n if (!roleDesciptor) {\n throw new Error(`No role descriptors found for ${roleName}`);\n }\n await samlAuth.setCustomRole(roleDesciptor);\n return loginAs(samlAuth.customRoleName);\n } else {\n await loginAs(roleName);\n }\n}\n```\n\nThis way we gonna use custom role to replicate serverless default roles\nin Stateful run (and support deployment agnostic approach)\n\n---------\n\nCo-authored-by: Cesare de Cal <cesare.decal@elastic.co>","sha":"ef32357d80162e873095a279a1552f29f30ed9f3"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213798","number":213798,"mergeCommit":{"message":"[scout] support login with a custom role (#213798)\n\n## Summary\n\nAdding custom roles support in Scout UI tests\n\nExample:\n\n```\n test.beforeEach(async ({ browserAuth, pageObjects }) => {\n await browserAuth.loginWithCustomRole({\n elasticsearch: {\n cluster: ['manage'],\n indices: [\n {\n names: ['.siem-signals*', '.lists-*', '.items-*'],\n privileges: ['read', 'view_index_metadata'],\n allow_restricted_indices: false,\n },\n {\n names: ['.alerts*', '.preview.alerts*'],\n privileges: ['read', 'view_index_metadata'],\n allow_restricted_indices: false,\n },\n ],\n },\n kibana: [\n {\n base: [],\n feature: {\n siemV2: ['read', 'read_alerts'],\n },\n spaces: ['*'],\n },\n ],\n });\n await pageObjects.dashboard.goto();\n```\n\nIn `kbn/scout-security` to login as `platform_engineer` we will need to\noverride browser auth fixture with smth like:\n\n```ts\nconst resourcePath = path.resolve(SERVERLESS_ROLES_ROOT_PATH, 'security', 'roles.yml');\nconst svlRoleDescriptors = new Map<string, any>(\n Object.entries(readRolesDescriptorsFromResource(resourcePath) as Record<string, unknown>)\n);\n\nconst loginAsPlatformEngineer = async () => {\n const roleName = 'platform_engineer';\n if (!serverless) {\n const roleDesciptor = svlRoleDescriptors?.get(roleName) as ElasticsearchRoleDescriptor;\n if (!roleDesciptor) {\n throw new Error(`No role descriptors found for ${roleName}`);\n }\n await samlAuth.setCustomRole(roleDesciptor);\n return loginAs(samlAuth.customRoleName);\n } else {\n await loginAs(roleName);\n }\n}\n```\n\nThis way we gonna use custom role to replicate serverless default roles\nin Stateful run (and support deployment agnostic approach)\n\n---------\n\nCo-authored-by: Cesare de Cal <cesare.decal@elastic.co>","sha":"ef32357d80162e873095a279a1552f29f30ed9f3"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Dzmitry Lemechko <dzmitry.lemechko@elastic.co> |
||
Pablo Machado
|
d696038882
|
[9.0] [SecuritySolution] Add index privileges check to applyDataViewIndices (#214803) (#215090)
# Backport This will backport the following commits from `main` to `9.0`: - [[SecuritySolution] Add index privileges check to applyDataViewIndices (#214803)](https://github.com/elastic/kibana/pull/214803) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Pablo Machado","email":"pablo.nevesmachado@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T15:37:39Z","message":"[SecuritySolution] Add index privileges check to applyDataViewIndices (#214803)\n\n## Summary\n\nAdd a new privileges check before executing `applyDataViewIndices`.\n\nThis change impacts the API call `applyDataViewIndices` and the job. \n`applyDataViewIndices` updates the transforms. Executing without\nprivileges generates a silence error because the transform can't run.\n\nI also added some extra unit tests for `applyDataViewIndices`.\n\nRequired privileges\n['read', 'view_index_metadata'] for all security solution dataview +\nasset_criticality and risk_score indices.\n\n\n### How to test it\n1. **API call with unprivileged user scenario**\n* Enable the entity store with a superuser\n* Create an unprivileged user\n* Call `POST kbn:api/entity_store/engines/apply_dataview_indices`\n* It should return an error\n* Add the required privileges\n* It executes successfully\n\n2. **Task execution with an unprivileged user scenario**\n* Create a user and add privileges only for the required Entity Store\nindices\n* Login with the new user\n* Enable the entity store\n* Add a new index to the security data view (the new user shouldn't have\naccess to the new index)\n* Wait for 30min for the job to run, or update the [source\ncode]( |
||
Dzmitry Lemechko
|
270867bac6
|
[9.0] [Space time] extending Scout with perfTracker fixture (#212397) (#215016)
# Backport This will backport the following commits from `main` to `9.0`: - [[Space time] extending Scout with perfTracker fixture (#212397)](https://github.com/elastic/kibana/pull/212397) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Dzmitry Lemechko","email":"dzmitry.lemechko@elastic.co"},"sourceCommit":{"committedDate":"2025-03-14T17:35:31Z","message":"[Space time] extending Scout with perfTracker fixture (#212397)\n\n## Summary\n\nOn-Week project \"Client-side performance insights with Playwright &\nLighthouse\"\n\nrevisiting old PR #66224\n\nThis PR extends Scout with `perfTracker` fixture designed to analyze\nJavaScript bundle performance and page-level performance metrics in\nKibana by leveraging Chrome DevTools Protocol (CDP).\n\nIt intercepts network requests, filters static bundles, and computes\nbundle size statistics per page load. Additionally, it collects CDP\nPerformance Domain Metrics, allowing in-depth analysis of rendering and\nscript execution times.\n\n\n[README]( |
||
Paul Tavares
|
c04009575a
|
[9.0] [Security Solution][Endpoint] Disable Artifact card menu under space awareness conditions where user is not allowed to edit item under active space (#213820) (#214992)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Solution][Endpoint] Disable Artifact card menu under space awareness conditions where user is not allowed to edit item under active space (#213820)](https://github.com/elastic/kibana/pull/213820) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Paul Tavares","email":"56442535+paul-tavares@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-13T12:52:33Z","message":"[Security Solution][Endpoint] Disable Artifact card menu under space awareness conditions where user is not allowed to edit item under active space (#213820)\n\n## Summary\n\nThe following changes are being done to Artifact Card's Menu (which\ndisplays the option to Delete or Update the artifact) in support of\nspace awareness feature (currently behind Feature Flag:\n`endpointManagementSpaceAwarenessEnabled`):\n\n- Global Artifacts: If displaying a global artifact and user does not\nhave the new Global Artifact Management privilege - disable the Edit\nmenu icon and display a tooltip on hover\n- Per-Policy Artifacts: if displaying a per-policy artifact in a space\nother than one of the `ownerSpaceId` spaces that the artifact is\nassociated with and the user does not have the new Global Artifact\nManagement privilege - disable the Edit menu icon and display a tooltip\nwhen the user hover over that button\n\n\n> [!NOTE]\n> Changes were **NOT** done to Endpoint Exceptions with this PR.","sha":"2b9d2cff6cb9edd0fe639e82f8fe2e46591c7f0c","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport missing","Team:Defend Workflows","backport:prev-minor","v9.1.0"],"title":"[Security Solution][Endpoint] Disable Artifact card menu under space awareness conditions where user is not allowed to edit item under active space","number":213820,"url":"https://github.com/elastic/kibana/pull/213820","mergeCommit":{"message":"[Security Solution][Endpoint] Disable Artifact card menu under space awareness conditions where user is not allowed to edit item under active space (#213820)\n\n## Summary\n\nThe following changes are being done to Artifact Card's Menu (which\ndisplays the option to Delete or Update the artifact) in support of\nspace awareness feature (currently behind Feature Flag:\n`endpointManagementSpaceAwarenessEnabled`):\n\n- Global Artifacts: If displaying a global artifact and user does not\nhave the new Global Artifact Management privilege - disable the Edit\nmenu icon and display a tooltip on hover\n- Per-Policy Artifacts: if displaying a per-policy artifact in a space\nother than one of the `ownerSpaceId` spaces that the artifact is\nassociated with and the user does not have the new Global Artifact\nManagement privilege - disable the Edit menu icon and display a tooltip\nwhen the user hover over that button\n\n\n> [!NOTE]\n> Changes were **NOT** done to Endpoint Exceptions with this PR.","sha":"2b9d2cff6cb9edd0fe639e82f8fe2e46591c7f0c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/213820","number":213820,"mergeCommit":{"message":"[Security Solution][Endpoint] Disable Artifact card menu under space awareness conditions where user is not allowed to edit item under active space (#213820)\n\n## Summary\n\nThe following changes are being done to Artifact Card's Menu (which\ndisplays the option to Delete or Update the artifact) in support of\nspace awareness feature (currently behind Feature Flag:\n`endpointManagementSpaceAwarenessEnabled`):\n\n- Global Artifacts: If displaying a global artifact and user does not\nhave the new Global Artifact Management privilege - disable the Edit\nmenu icon and display a tooltip on hover\n- Per-Policy Artifacts: if displaying a per-policy artifact in a space\nother than one of the `ownerSpaceId` spaces that the artifact is\nassociated with and the user does not have the new Global Artifact\nManagement privilege - disable the Edit menu icon and display a tooltip\nwhen the user hover over that button\n\n\n> [!NOTE]\n> Changes were **NOT** done to Endpoint Exceptions with this PR.","sha":"2b9d2cff6cb9edd0fe639e82f8fe2e46591c7f0c"}}]}] BACKPORT--> |
||
Jonathan Budzenski
|
7f7a93e921 |
Revert "[9.0] fix(NA): retrieve_elastic_doc tests helpers import (#215051) (#215054)"
This reverts commit
|
||
|
Kibana Machine
|
576365ccc0
|
[9.0] [kbn-grid-layout] Smoother scrolling (#214512) (#215003)
# Backport This will backport the following commits from `main` to `9.0`: - [[kbn-grid-layout] Smoother scrolling (#214512)](https://github.com/elastic/kibana/pull/214512) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Devon Thomson","email":"devon.thomson@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T15:27:05Z","message":"[kbn-grid-layout] Smoother scrolling (#214512)\n\nUse `requestAnimationFrame` to make the autoscroll functionality match the refresh rate of the display.","sha":"92386266066f13cbe39f37487322d66bfe903d5f","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Presentation","loe:small","impact:low","release_note:feature","backport:prev-minor","v9.1.0"],"title":"[kbn-grid-layout] Smoother scrolling","number":214512,"url":"https://github.com/elastic/kibana/pull/214512","mergeCommit":{"message":"[kbn-grid-layout] Smoother scrolling (#214512)\n\nUse `requestAnimationFrame` to make the autoscroll functionality match the refresh rate of the display.","sha":"92386266066f13cbe39f37487322d66bfe903d5f"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214512","number":214512,"mergeCommit":{"message":"[kbn-grid-layout] Smoother scrolling (#214512)\n\nUse `requestAnimationFrame` to make the autoscroll functionality match the refresh rate of the display.","sha":"92386266066f13cbe39f37487322d66bfe903d5f"}}]}] BACKPORT--> Co-authored-by: Devon Thomson <devon.thomson@elastic.co> |
||
|
Kibana Machine
|
15b88311fe | skip failing test suite (#215065) | ||
|
Kibana Machine
|
da44113249
|
[9.0] Unauthorized route migration for routes owned by kibana-core (#214780) (#215011)
# Backport This will backport the following commits from `main` to `9.0`: - [Unauthorized route migration for routes owned by kibana-core (#214780)](https://github.com/elastic/kibana/pull/214780) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-18T16:04:01Z","message":"Unauthorized route migration for routes owned by kibana-core (#214780)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"b9d240b38b3a5408474647addd3b13d6e838def8","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Core","enhancement","release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration for routes owned by kibana-core","number":214780,"url":"https://github.com/elastic/kibana/pull/214780","mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-core (#214780)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"b9d240b38b3a5408474647addd3b13d6e838def8"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214780","number":214780,"mergeCommit":{"message":"Unauthorized route migration for routes owned by kibana-core (#214780)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"b9d240b38b3a5408474647addd3b13d6e838def8"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com> |
||
|
Kibana Machine
|
767fd33d2d
|
[9.0] Unauthorized route migration for routes owned by appex-ai-infra (#214777) (#214827)
# Backport This will backport the following commits from `main` to `9.0`: - [Unauthorized route migration for routes owned by appex-ai-infra (#214777)](https://github.com/elastic/kibana/pull/214777) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-17T16:05:32Z","message":"Unauthorized route migration for routes owned by appex-ai-infra (#214777)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"f82949698aaa0d687f4cf667079fcd15fe1927dd","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Feature:Security/Authorization","backport:prev-minor","backport:version","Team:AI Infra","Authz: API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration for routes owned by appex-ai-infra","number":214777,"url":"https://github.com/elastic/kibana/pull/214777","mergeCommit":{"message":"Unauthorized route migration for routes owned by appex-ai-infra (#214777)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"f82949698aaa0d687f4cf667079fcd15fe1927dd"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214777","number":214777,"mergeCommit":{"message":"Unauthorized route migration for routes owned by appex-ai-infra (#214777)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"f82949698aaa0d687f4cf667079fcd15fe1927dd"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com> |
||
|
Kibana Machine
|
b80b1161c8
|
[9.0] [Obs AI Assistant] Fix KB bulk import UI example (#214970) (#214988)
# Backport This will backport the following commits from `main` to `9.0`: - [[Obs AI Assistant] Fix KB bulk import UI example (#214970)](https://github.com/elastic/kibana/pull/214970) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Viduni Wickramarachchi","email":"viduni.wickramarachchi@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T14:34:21Z","message":"[Obs AI Assistant] Fix KB bulk import UI example (#214970)\n\nCloses https://github.com/elastic/kibana/issues/214849\n\n## Summary\n\nThe KB bulk import UI example has a missing property `title`.\nThis PR adds the missing property so that the users know which format is\nexpected when bulk importing.\n\n\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"69e8dcf59bd91aaa79f3c85490e6181c747455ac","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:fix","v9.0.0","Team:Obs AI Assistant","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Obs AI Assistant] Fix KB bulk import UI example","number":214970,"url":"https://github.com/elastic/kibana/pull/214970","mergeCommit":{"message":"[Obs AI Assistant] Fix KB bulk import UI example (#214970)\n\nCloses https://github.com/elastic/kibana/issues/214849\n\n## Summary\n\nThe KB bulk import UI example has a missing property `title`.\nThis PR adds the missing property so that the users know which format is\nexpected when bulk importing.\n\n\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"69e8dcf59bd91aaa79f3c85490e6181c747455ac"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214970","number":214970,"mergeCommit":{"message":"[Obs AI Assistant] Fix KB bulk import UI example (#214970)\n\nCloses https://github.com/elastic/kibana/issues/214849\n\n## Summary\n\nThe KB bulk import UI example has a missing property `title`.\nThis PR adds the missing property so that the users know which format is\nexpected when bulk importing.\n\n\n\n\n### Checklist\n\n- [x] The PR description includes the appropriate Release Notes section,\nand the correct `release_note:*` label is applied per the\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)","sha":"69e8dcf59bd91aaa79f3c85490e6181c747455ac"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Viduni Wickramarachchi <viduni.wickramarachchi@elastic.co> |
||
|
Kibana Machine
|
bf858b1bac
|
[9.0] fix(NA): retrieve_elastic_doc tests helpers import (#215051) (#215054)
# Backport This will backport the following commits from `main` to `9.0`: - [fix(NA): retrieve_elastic_doc tests helpers import (#215051)](https://github.com/elastic/kibana/pull/215051) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T19:20:40Z","message":"fix(NA): retrieve_elastic_doc tests helpers import (#215051)\n\nThis PR fixes https://github.com/elastic/kibana/pull/214880 as it\nincluded a non existent import","sha":"1f3cbf110527266b8c91d99d5384cbd68d4a3a98","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","v9.0.0","backport:version","v9.1.0","v8.19.0"],"title":"fix(NA): retrieve_elastic_doc tests helpers import","number":215051,"url":"https://github.com/elastic/kibana/pull/215051","mergeCommit":{"message":"fix(NA): retrieve_elastic_doc tests helpers import (#215051)\n\nThis PR fixes https://github.com/elastic/kibana/pull/214880 as it\nincluded a non existent import","sha":"1f3cbf110527266b8c91d99d5384cbd68d4a3a98"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/215051","number":215051,"mergeCommit":{"message":"fix(NA): retrieve_elastic_doc tests helpers import (#215051)\n\nThis PR fixes https://github.com/elastic/kibana/pull/214880 as it\nincluded a non existent import","sha":"1f3cbf110527266b8c91d99d5384cbd68d4a3a98"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Tiago Costa <tiago.costa@elastic.co> |
||
|
Kibana Machine
|
5b91cbf2d8
|
[9.0] [Security Assistant] Fix inference rollover (#214718) (#215043)
# Backport This will backport the following commits from `main` to `9.0`: - [[Security Assistant] Fix inference rollover (#214718)](https://github.com/elastic/kibana/pull/214718) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Patryk Kopyciński","email":"contact@patrykkopycinski.com"},"sourceCommit":{"committedDate":"2025-03-18T17:47:45Z","message":"[Security Assistant] Fix inference rollover (#214718)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/214709#event-16799922233\n\nThe issue was caused by the rollover of the Knowledge Base Data stream\nto use default inference endpoint.\nDuring the rollover it first got to this branch\nhttps://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/elastic_assistant/server/ai_assistant_service/index.ts#L347-L369\nwhere it went through all the steps and continued, but it didn't\noverride `this.knowledgeBaseStream`, so the next time someone hit API it\nwas going through this path calling `getInitializedResources` to make\nsure all data streams were configured properly, but because we didn't\nupdate `this.knowledgeBaseStream` it was failing, because the original\nconfiguration that was created in service constructor was not called,\nthat's why it was returning an error","sha":"be777cf44f8313c995379a5bc4485ab1e26b14ac","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:skip","v9.0.0","backport:version","v8.18.0","v9.1.0","v8.19.0"],"title":"[Security Assistant] Fix inference rollover","number":214718,"url":"https://github.com/elastic/kibana/pull/214718","mergeCommit":{"message":"[Security Assistant] Fix inference rollover (#214718)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/214709#event-16799922233\n\nThe issue was caused by the rollover of the Knowledge Base Data stream\nto use default inference endpoint.\nDuring the rollover it first got to this branch\nhttps://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/elastic_assistant/server/ai_assistant_service/index.ts#L347-L369\nwhere it went through all the steps and continued, but it didn't\noverride `this.knowledgeBaseStream`, so the next time someone hit API it\nwas going through this path calling `getInitializedResources` to make\nsure all data streams were configured properly, but because we didn't\nupdate `this.knowledgeBaseStream` it was failing, because the original\nconfiguration that was created in service constructor was not called,\nthat's why it was returning an error","sha":"be777cf44f8313c995379a5bc4485ab1e26b14ac"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.18","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214718","number":214718,"mergeCommit":{"message":"[Security Assistant] Fix inference rollover (#214718)\n\n## Summary\nFixes https://github.com/elastic/kibana/issues/214709#event-16799922233\n\nThe issue was caused by the rollover of the Knowledge Base Data stream\nto use default inference endpoint.\nDuring the rollover it first got to this branch\nhttps://github.com/elastic/kibana/blob/main/x-pack/solutions/security/plugins/elastic_assistant/server/ai_assistant_service/index.ts#L347-L369\nwhere it went through all the steps and continued, but it didn't\noverride `this.knowledgeBaseStream`, so the next time someone hit API it\nwas going through this path calling `getInitializedResources` to make\nsure all data streams were configured properly, but because we didn't\nupdate `this.knowledgeBaseStream` it was failing, because the original\nconfiguration that was created in service constructor was not called,\nthat's why it was returning an error","sha":"be777cf44f8313c995379a5bc4485ab1e26b14ac"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Patryk Kopyciński <contact@patrykkopycinski.com> |
||
|
elastic-renovate-prod[bot]
|
807a36c8c9
|
Update docker.elastic.co/wolfi/chainguard-base:latest Docker digest to 5ba5def (9.0) (#214946)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | docker.elastic.co/wolfi/chainguard-base | digest | `66d427a` -> `5ba5def` | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://redirect.github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4xMDcuMCIsInVwZGF0ZWRJblZlciI6IjM5LjEwNy4wIiwidGFyZ2V0QnJhbmNoIjoiOS4wIiwibGFiZWxzIjpbIlRlYW06T3BlcmF0aW9ucyIsImJhY2twb3J0OnNraXAiLCJyZWxlYXNlX25vdGU6c2tpcCJdfQ==--> Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> |
||
|
Kibana Machine
|
1ce4663582
|
[9.0] Fix sort for rollup data views (#214656) (#215041)
# Backport This will backport the following commits from `main` to `9.0`: - [Fix sort for rollup data views (#214656)](https://github.com/elastic/kibana/pull/214656) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lukas Olson","email":"lukas@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T17:17:53Z","message":"Fix sort for rollup data views (#214656)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213629.\n\nSince https://github.com/elastic/kibana/pull/163784 we have included a\n`format` parameter in the `sort` that we send to Elasticsearch. This\nworked for everything except rollup data views, which break when the\n`format` parameter is provided.\n\nThis restores the behavior prior to that PR (we still send the `sort`\nbut don't include the `format` parameter). Ideally we would probably not\nsend the timestamp field at all for rollup data views since we treat\nthem as if they are non-time-based, but this would require a bit of a\nrefactor, and rollups are deprecated anyway.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n### Release notes\n\nFixes opening a rollup data view in Discover.\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"2de4b331d334454c4b3bb17b75dcdb83207ee9f9","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Feature:Search","release_note:fix","Feature:Data Views","Feature:Rollups","Team:DataDiscovery","backport:all-open","v9.1.0"],"title":"Fix sort for rollup data views","number":214656,"url":"https://github.com/elastic/kibana/pull/214656","mergeCommit":{"message":"Fix sort for rollup data views (#214656)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213629.\n\nSince https://github.com/elastic/kibana/pull/163784 we have included a\n`format` parameter in the `sort` that we send to Elasticsearch. This\nworked for everything except rollup data views, which break when the\n`format` parameter is provided.\n\nThis restores the behavior prior to that PR (we still send the `sort`\nbut don't include the `format` parameter). Ideally we would probably not\nsend the timestamp field at all for rollup data views since we treat\nthem as if they are non-time-based, but this would require a bit of a\nrefactor, and rollups are deprecated anyway.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n### Release notes\n\nFixes opening a rollup data view in Discover.\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"2de4b331d334454c4b3bb17b75dcdb83207ee9f9"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214656","number":214656,"mergeCommit":{"message":"Fix sort for rollup data views (#214656)\n\n## Summary\n\nResolves https://github.com/elastic/kibana/issues/213629.\n\nSince https://github.com/elastic/kibana/pull/163784 we have included a\n`format` parameter in the `sort` that we send to Elasticsearch. This\nworked for everything except rollup data views, which break when the\n`format` parameter is provided.\n\nThis restores the behavior prior to that PR (we still send the `sort`\nbut don't include the `format` parameter). Ideally we would probably not\nsend the timestamp field at all for rollup data views since we treat\nthem as if they are non-time-based, but this would require a bit of a\nrefactor, and rollups are deprecated anyway.\n\n### Checklist\n\n- [x] [Unit or functional\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\nwere updated or added to match the most common scenarios\n- [ ] [Flaky Test\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\nused on any tests changed\n\n### Release notes\n\nFixes opening a rollup data view in Discover.\n\nCo-authored-by: Matthew Kime <matt@mattki.me>","sha":"2de4b331d334454c4b3bb17b75dcdb83207ee9f9"}}]}] BACKPORT--> Co-authored-by: Lukas Olson <lukas@elastic.co> |
||
|
Kibana Machine
|
eb8c5c58e0
|
[9.0] Unauthorized route migration for routes owned by search-kibana (#214786) (#215036)
# Backport This will backport the following commits from `main` to `9.0`: - [Unauthorized route migration for routes owned by search-kibana (#214786)](https://github.com/elastic/kibana/pull/214786) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Elena Shostak","email":"165678770+elena-shostak@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-03-18T17:29:08Z","message":"Unauthorized route migration for routes owned by search-kibana (#214786)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"a3dd168cb1d8fb22a96e84994a6850b27a11d762","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["enhancement","release_note:skip","Feature:Security/Authorization","Team:Search","backport:prev-minor","backport:version","Authz: API migration","v9.1.0","v8.19.0"],"title":"Unauthorized route migration for routes owned by search-kibana","number":214786,"url":"https://github.com/elastic/kibana/pull/214786","mergeCommit":{"message":"Unauthorized route migration for routes owned by search-kibana (#214786)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"a3dd168cb1d8fb22a96e84994a6850b27a11d762"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214786","number":214786,"mergeCommit":{"message":"Unauthorized route migration for routes owned by search-kibana (#214786)\n\n### Authz API migration for unauthorized routes\n\nThis PR migrates last unauthorized routes owned by your team to a new\nsecurity configuration.\nPlease refer to the documentation for more information: [Authorization\nAPI](https://docs.elastic.dev/kibana-dev-docs/key-concepts/security-api-authorization)\n\n### **Before migration:**\n```ts\nrouter.get({\n path: '/api/path',\n ...\n}, handler);\n```\n\n### **After migration:**\n```ts\nrouter.get({\n path: '/api/path',\n security: {\n authz: {\n enabled: false,\n reason: 'This route is opted out from authorization because ...',\n },\n },\n ...\n}, handler);\n```","sha":"a3dd168cb1d8fb22a96e84994a6850b27a11d762"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Elena Shostak <165678770+elena-shostak@users.noreply.github.com> |
||
|
Kibana Machine
|
23c067bdb4
|
[9.0] add API retrieve_elastic_doc tests (#214880) (#214991)
# Backport This will backport the following commits from `main` to `9.0`: - [add API retrieve_elastic_doc tests (#214880)](https://github.com/elastic/kibana/pull/214880) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Arturo Lidueña","email":"arturo.liduena@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T14:45:43Z","message":"add API retrieve_elastic_doc tests (#214880)\n\nRelated: https://github.com/elastic/kibana/issues/180787\n\n- Adds test for `retrieve_elastic_doc` function","sha":"8241bd7e6c788c8ab564ecfdbb68f584d2a7374a","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Obs AI Assistant","backport:version","v9.1.0","v8.19.0"],"title":"add API retrieve_elastic_doc tests","number":214880,"url":"https://github.com/elastic/kibana/pull/214880","mergeCommit":{"message":"add API retrieve_elastic_doc tests (#214880)\n\nRelated: https://github.com/elastic/kibana/issues/180787\n\n- Adds test for `retrieve_elastic_doc` function","sha":"8241bd7e6c788c8ab564ecfdbb68f584d2a7374a"}},"sourceBranch":"main","suggestedTargetBranches":["9.0","8.x"],"targetPullRequestStates":[{"branch":"9.0","label":"v9.0.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214880","number":214880,"mergeCommit":{"message":"add API retrieve_elastic_doc tests (#214880)\n\nRelated: https://github.com/elastic/kibana/issues/180787\n\n- Adds test for `retrieve_elastic_doc` function","sha":"8241bd7e6c788c8ab564ecfdbb68f584d2a7374a"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Arturo Lidueña <arturo.liduena@elastic.co> |
||
|
Kibana Machine
|
8e250788c7
|
[9.0] [DOCS] Consolidate and clean up Kibana settings (part 1) (#214934) (#215048)
# Backport This will backport the following commits from `main` to `9.0`: - [[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)](https://github.com/elastic/kibana/pull/214934) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Lisa Cawley","email":"lcawley@elastic.co"},"sourceCommit":{"committedDate":"2025-03-18T18:37:40Z","message":"[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)","sha":"3b2df8935b7ab386a7b94df5f14737fc1b9b0307","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Docs","release_note:skip","docs","backport:version","v9.1.0","v9.0.1"],"title":"[DOCS] Consolidate and clean up Kibana settings (part 1)","number":214934,"url":"https://github.com/elastic/kibana/pull/214934","mergeCommit":{"message":"[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)","sha":"3b2df8935b7ab386a7b94df5f14737fc1b9b0307"}},"sourceBranch":"main","suggestedTargetBranches":["9.0"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/214934","number":214934,"mergeCommit":{"message":"[DOCS] Consolidate and clean up Kibana settings (part 1) (#214934)","sha":"3b2df8935b7ab386a7b94df5f14737fc1b9b0307"}},{"branch":"9.0","label":"v9.0.1","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Lisa Cawley <lcawley@elastic.co> |
||
Tiago Costa
|
02bf213f4e
|
[9.0] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#215028)
# Backport This will backport the following commits from `main` to `9.0`: - [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)](https://github.com/elastic/kibana/pull/211231) <!--- Backport version: 9.6.6 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Tiago Costa","email":"tiago.costa@elastic.co"},"sourceCommit":{"committedDate":"2025-02-14T17:07:41Z","message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb","branchLabelMapping":{"^v9.1.0$":"main","^v8.19.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["chore","Team:Operations","release_note:skip","backport:prev-major","v8.18.0","v9.1.0","v8.19.0","v8.17.3","v8.16.5"],"title":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin","number":211231,"url":"https://github.com/elastic/kibana/pull/211231","mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"8.18","label":"v8.18.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211284","number":211284,"state":"MERGED","mergeCommit":{"sha":"4bcd166b3aabbccbca03bd0a86110e29f0812171","message":"[8.18] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211284)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.18`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>"}},{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/211231","number":211231,"mergeCommit":{"message":"fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231)\n\nThis PR solves an issue detected in the populate bundle cache plugin\nafter the webpack v5 migration. On the new version webpack v5 returns a\nlot of incomplete paths when we walk over file dependencies or internal\nmodules. The heuristic logic used previously was faulty so the fixes\nturns to use a cached filesystem api instead.\n\n---------\n\nCo-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>","sha":"16a9136b93e2b9bc2e5d86ff7167a8ae0a563cdb"}},{"branch":"8.x","label":"v8.19.0","branchLabelMappingKey":"^v8.19.0$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211285","number":211285,"state":"MERGED","mergeCommit":{"sha":"73a5339547c64f9060465c4368e216744ce8d514","message":"[8.x] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211285)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.x`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n\n\nCo-authored-by: Tiago Costa <tiago.costa@elastic.co>"}},{"branch":"8.17","label":"v8.17.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211672","number":211672,"state":"MERGED","mergeCommit":{"sha":"8f8369753beb6ed6ebd6ac705948b917d5abefc4","message":"[8.17] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211672)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}},{"branch":"8.16","label":"v8.16.5","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/211674","number":211674,"state":"MERGED","mergeCommit":{"sha":"851913bd02ee74230a43a8c2788f606be0189dd2","message":"[8.16] fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache plugin (#211231) (#211674)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.16`:\n- [fix(NA): use filesystem apis on kbn/optimizer populate_bundle_cache\nplugin (#211231)](https://github.com/elastic/kibana/pull/211231)\n\n\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sorenlouv/backport)\n\n"}}]}] BACKPORT--> |