[Search][ES3] Enable Inference Management UI in ES3 #200109
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Samiul-TheSoccerFan
force-pushed
the
fix-index-management-link-in-es3
branch
from
76ccafb to
613f4c1
Compare
Samiul-TheSoccerFan
added
release_note:skip
Samiul-TheSoccerFan
added
the
backport:version
|
@elasticmachine merge upstream |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#7414[✅] x-pack/test_serverless/functional/test_suites/search/config.ts: 25/25 tests passed. |
TattdCodeMonkey
requested changes
Nov 18, 2024
| @@ -47,5 +47,15 @@ export function SvlSearchNavigationServiceProvider({ | |||
| }); | |||
| await testSubjects.existOrFail('searchIndicesDetailsPage', { timeout: 2000 }); | |||
| }, | |||
| async navigateToInferenceManagementPage(expectRedirect: boolean = false) { | |||
| await retry.tryForTime(60 * 1000, async () => { | |||
| await PageObjects.common.navigateToApp('searchInferenceEndpoints', { | |||
There was a problem hiding this comment.
I do not see searchInferenceEndpoints in either the base.config or search config
for this navigateToApp() to work you need to define the app in the config.
There was a problem hiding this comment.
There is no need to wrap PageObjects.common.navigateToApp with retry because it is already has retry inside with 2 times timeouts.try (4 minutes total)
https://github.com/elastic/kibana/blob/main/test/functional/page_objects/common_page.ts#L263-L373
x-pack/test_serverless/functional/page_objects/svl_search_inference_management_page.ts
Outdated
Show resolved
Hide resolved
...ck/plugins/search_inference_endpoints/public/components/all_inference_endpoints/constants.ts
Show resolved
Hide resolved
...all_inference_endpoints/render_table_columns/render_actions/actions/component/index_item.tsx
Outdated
Show resolved
Hide resolved
...all_inference_endpoints/render_table_columns/render_actions/actions/component/index_item.tsx
Show resolved
Hide resolved
...all_inference_endpoints/render_table_columns/render_actions/actions/component/index_item.tsx
Outdated
Show resolved
Hide resolved
..._inference_endpoints/render_table_columns/render_actions/actions/component/pipeline_item.tsx
Outdated
Show resolved
Hide resolved
...rence_endpoints/render_table_columns/render_actions/actions/component/scan_usage_results.tsx
Show resolved
Hide resolved
Samiul-TheSoccerFan
force-pushed
the
fix-index-management-link-in-es3
branch
from
ceffc7a to
499c3fa
Compare
jloleysens
added
the
ci:project-deploy-elasticsearch
jloleysens
approved these changes
Nov 19, 2024
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#7432[✅] x-pack/test_serverless/functional/test_suites/search/config.ts: 25/25 tests passed. |
|
@elasticmachine merge upstream |
dmlemeshko
approved these changes
Nov 20, 2024
elena-shostak
approved these changes
Nov 20, 2024
|
@jloleysens : Do you know how I can access the QA deployment for this PR? I never done that so it would be great if you can share any knowledge or documentation on that. |
TattdCodeMonkey
approved these changes
Nov 20, 2024
...rence_endpoints/render_table_columns/render_actions/actions/component/scan_usage_results.tsx
Show resolved
Hide resolved
x-pack/test_serverless/functional/services/svl_search_navigation.ts
Outdated
Show resolved
Hide resolved
Samiul-TheSoccerFan
force-pushed
the
fix-index-management-link-in-es3
branch
from
73c9b6c to
4b757e1
Compare
| @@ -45,5 +45,8 @@ export default createTestConfig({ | |||
| elasticsearchIndices: { | |||
| pathname: '/app/elasticsearch/indices', | |||
| }, | |||
| searchInferenceEndpoints: { | |||
| pathname: '/app/search_inference_endpoints', | |||
There was a problem hiding this comment.
this URL needs to be updated along with the URL alignment
Sure, This PR is already a little big. I will unskip these tests in a separate PR. |
|
Hey @Samiul-TheSoccerFan, you can check the latest buildkite job, there is a section "Elasticsearch Serverless Deployment" with a link and instructions on how to log in. |
ryankeairns
approved these changes
Nov 22, 2024
💚 Build Succeeded
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
miscellaneous assets size
History
|
|
Tested in QA Serverless-in-qa.mov |
|
Starting backport for target branches: 8.17 |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 22, 2024
## Summary This PR: - Enables Inference Management in ES3 - Fixes small issues to make sure it works in ES3. - Added FTR tests. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [X] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [X] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [X] The PR description includes the appropriate Release Notes section, and the correct `release_node:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit 37a0861)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Nov 22, 2024
…201464) # Backport This will backport the following commits from `main` to `8.17`: - [[Search][ES3] Enable Inference Management UI in ES3 (#200109)](#200109) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Samiul Monir","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-22T19:10:45Z","message":"[Search][ES3] Enable Inference Management UI in ES3 (#200109)\n\n## Summary\r\n\r\nThis PR:\r\n- Enables Inference Management in ES3\r\n- Fixes small issues to make sure it works in ES3.\r\n- Added FTR tests.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"37a0861d28aa3fe9e1a35db0c37aa463226b870b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","ci:project-deploy-elasticsearch","backport:version","v8.17.0"],"title":"[Search][ES3] Enable Inference Management UI in ES3","number":200109,"url":"https://github.com/elastic/kibana/pull/200109","mergeCommit":{"message":"[Search][ES3] Enable Inference Management UI in ES3 (#200109)\n\n## Summary\r\n\r\nThis PR:\r\n- Enables Inference Management in ES3\r\n- Fixes small issues to make sure it works in ES3.\r\n- Added FTR tests.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"37a0861d28aa3fe9e1a35db0c37aa463226b870b"}},"sourceBranch":"main","suggestedTargetBranches":["8.17"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200109","number":200109,"mergeCommit":{"message":"[Search][ES3] Enable Inference Management UI in ES3 (#200109)\n\n## Summary\r\n\r\nThis PR:\r\n- Enables Inference Management in ES3\r\n- Fixes small issues to make sure it works in ES3.\r\n- Added FTR tests.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"37a0861d28aa3fe9e1a35db0c37aa463226b870b"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Samiul Monir <[email protected]>
pheyos
added
backport:version
|
Starting backport for target branches: 8.17, 8.x |
kibanamachine
pushed a commit
to kibanamachine/kibana
that referenced
this pull request
Nov 23, 2024
## Summary This PR: - Enables Inference Management in ES3 - Fixes small issues to make sure it works in ES3. - Added FTR tests. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [X] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [X] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [X] The PR description includes the appropriate Release Notes section, and the correct `release_node:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit 37a0861)
💔 Some backports could not be created
Note: Successful backport PRs will be merged automatically after passing CI. Manual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
Nov 23, 2024
…201496) # Backport This will backport the following commits from `main` to `8.x`: - [[Search][ES3] Enable Inference Management UI in ES3 (#200109)](#200109) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Samiul Monir","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-11-22T19:10:45Z","message":"[Search][ES3] Enable Inference Management UI in ES3 (#200109)\n\n## Summary\r\n\r\nThis PR:\r\n- Enables Inference Management in ES3\r\n- Fixes small issues to make sure it works in ES3.\r\n- Added FTR tests.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"37a0861d28aa3fe9e1a35db0c37aa463226b870b","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Search","ci:project-deploy-elasticsearch","backport:version","v8.17.0","v8.18.0"],"title":"[Search][ES3] Enable Inference Management UI in ES3","number":200109,"url":"https://github.com/elastic/kibana/pull/200109","mergeCommit":{"message":"[Search][ES3] Enable Inference Management UI in ES3 (#200109)\n\n## Summary\r\n\r\nThis PR:\r\n- Enables Inference Management in ES3\r\n- Fixes small issues to make sure it works in ES3.\r\n- Added FTR tests.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"37a0861d28aa3fe9e1a35db0c37aa463226b870b"}},"sourceBranch":"main","suggestedTargetBranches":["8.x"],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/200109","number":200109,"mergeCommit":{"message":"[Search][ES3] Enable Inference Management UI in ES3 (#200109)\n\n## Summary\r\n\r\nThis PR:\r\n- Enables Inference Management in ES3\r\n- Fixes small issues to make sure it works in ES3.\r\n- Added FTR tests.\r\n\r\n\r\n### Checklist\r\n\r\nCheck the PR satisfies following conditions. \r\n\r\nReviewers should verify this PR satisfies this list as well.\r\n\r\n- [X] [Unit or functional\r\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\r\nwere updated or added to match the most common scenarios\r\n- [X] This was checked for breaking HTTP API changes, and any breaking\r\nchanges have been approved by the breaking-change committee. The\r\n`release_note:breaking` label should be applied in these situations.\r\n- [X] [Flaky Test\r\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was\r\nused on any tests changed\r\n- [X] The PR description includes the appropriate Release Notes section,\r\nand the correct `release_node:*` label is applied per the\r\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\r\n\r\n---------\r\n\r\nCo-authored-by: kibanamachine <[email protected]>","sha":"37a0861d28aa3fe9e1a35db0c37aa463226b870b"}},{"branch":"8.17","label":"v8.17.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"url":"https://github.com/elastic/kibana/pull/201464","number":201464,"state":"MERGED","mergeCommit":{"sha":"5d8b8eb46a6e91b3edd5804158924994d1cce70f","message":"[8.17] [Search][ES3] Enable Inference Management UI in ES3 (#200109) (#201464)\n\n# Backport\n\nThis will backport the following commits from `main` to `8.17`:\n- [[Search][ES3] Enable Inference Management UI in ES3\n(#200109)](https://github.com/elastic/kibana/pull/200109)\n\n<!--- Backport version: 9.4.3 -->\n\n### Questions ?\nPlease refer to the [Backport tool\ndocumentation](https://github.com/sqren/backport)\n\n<!--BACKPORT [{\"author\":{\"name\":\"Samiul\nMonir\",\"email\":\"[email protected]\"},\"sourceCommit\":{\"committedDate\":\"2024-11-22T19:10:45Z\",\"message\":\"[Search][ES3]\nEnable Inference Management UI in ES3 (#200109)\\n\\n##\nSummary\\r\\n\\r\\nThis PR:\\r\\n- Enables Inference Management in ES3\\r\\n-\nFixes small issues to make sure it works in ES3.\\r\\n- Added FTR\ntests.\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nCheck the PR satisfies following\nconditions. \\r\\n\\r\\nReviewers should verify this PR satisfies this list\nas well.\\r\\n\\r\\n- [X] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [X] This was\nchecked for breaking HTTP API changes, and any breaking\\r\\nchanges have\nbeen approved by the breaking-change committee.\nThe\\r\\n`release_note:breaking` label should be applied in these\nsituations.\\r\\n- [X] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n- [X] The PR description includes\nthe appropriate Release Notes section,\\r\\nand the correct\n`release_node:*` label is applied per\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<[email protected]>\",\"sha\":\"37a0861d28aa3fe9e1a35db0c37aa463226b870b\",\"branchLabelMapping\":{\"^v9.0.0$\":\"main\",\"^v8.18.0$\":\"8.x\",\"^v(\\\\d+).(\\\\d+).\\\\d+$\":\"$1.$2\"}},\"sourcePullRequest\":{\"labels\":[\"release_note:skip\",\"v9.0.0\",\"Team:Search\",\"ci:project-deploy-elasticsearch\",\"backport:version\",\"v8.17.0\"],\"title\":\"[Search][ES3]\nEnable Inference Management UI in\nES3\",\"number\":200109,\"url\":\"https://github.com/elastic/kibana/pull/200109\",\"mergeCommit\":{\"message\":\"[Search][ES3]\nEnable Inference Management UI in ES3 (#200109)\\n\\n##\nSummary\\r\\n\\r\\nThis PR:\\r\\n- Enables Inference Management in ES3\\r\\n-\nFixes small issues to make sure it works in ES3.\\r\\n- Added FTR\ntests.\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nCheck the PR satisfies following\nconditions. \\r\\n\\r\\nReviewers should verify this PR satisfies this list\nas well.\\r\\n\\r\\n- [X] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [X] This was\nchecked for breaking HTTP API changes, and any breaking\\r\\nchanges have\nbeen approved by the breaking-change committee.\nThe\\r\\n`release_note:breaking` label should be applied in these\nsituations.\\r\\n- [X] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n- [X] The PR description includes\nthe appropriate Release Notes section,\\r\\nand the correct\n`release_node:*` label is applied per\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<[email protected]>\",\"sha\":\"37a0861d28aa3fe9e1a35db0c37aa463226b870b\"}},\"sourceBranch\":\"main\",\"suggestedTargetBranches\":[\"8.17\"],\"targetPullRequestStates\":[{\"branch\":\"main\",\"label\":\"v9.0.0\",\"branchLabelMappingKey\":\"^v9.0.0$\",\"isSourceBranch\":true,\"state\":\"MERGED\",\"url\":\"https://github.com/elastic/kibana/pull/200109\",\"number\":200109,\"mergeCommit\":{\"message\":\"[Search][ES3]\nEnable Inference Management UI in ES3 (#200109)\\n\\n##\nSummary\\r\\n\\r\\nThis PR:\\r\\n- Enables Inference Management in ES3\\r\\n-\nFixes small issues to make sure it works in ES3.\\r\\n- Added FTR\ntests.\\r\\n\\r\\n\\r\\n### Checklist\\r\\n\\r\\nCheck the PR satisfies following\nconditions. \\r\\n\\r\\nReviewers should verify this PR satisfies this list\nas well.\\r\\n\\r\\n- [X] [Unit or\nfunctional\\r\\ntests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)\\r\\nwere\nupdated or added to match the most common scenarios\\r\\n- [X] This was\nchecked for breaking HTTP API changes, and any breaking\\r\\nchanges have\nbeen approved by the breaking-change committee.\nThe\\r\\n`release_note:breaking` label should be applied in these\nsituations.\\r\\n- [X] [Flaky\nTest\\r\\nRunner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1)\nwas\\r\\nused on any tests changed\\r\\n- [X] The PR description includes\nthe appropriate Release Notes section,\\r\\nand the correct\n`release_node:*` label is applied per\nthe\\r\\n[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)\\r\\n\\r\\n---------\\r\\n\\r\\nCo-authored-by:\nkibanamachine\n<[email protected]>\",\"sha\":\"37a0861d28aa3fe9e1a35db0c37aa463226b870b\"}},{\"branch\":\"8.17\",\"label\":\"v8.17.0\",\"branchLabelMappingKey\":\"^v(\\\\d+).(\\\\d+).\\\\d+$\",\"isSourceBranch\":false,\"state\":\"NOT_CREATED\"}]}]\nBACKPORT-->\n\nCo-authored-by: Samiul Monir <[email protected]>"}},{"branch":"8.x","label":"v8.18.0","branchLabelMappingKey":"^v8.18.0$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> Co-authored-by: Samiul Monir <[email protected]>
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this pull request
Nov 26, 2024
## Summary This PR: - Enables Inference Management in ES3 - Fixes small issues to make sure it works in ES3. - Added FTR tests. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [X] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [X] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [X] The PR description includes the appropriate Release Notes section, and the correct `release_node:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <[email protected]>
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Dec 12, 2024
## Summary This PR: - Enables Inference Management in ES3 - Fixes small issues to make sure it works in ES3. - Added FTR tests. ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [X] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [X] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [X] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [X] The PR description includes the appropriate Release Notes section, and the correct `release_node:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) --------- Co-authored-by: kibanamachine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR:
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_node:*label is applied per the guidelines