[9.1] [Security Assistant] Fixes issue preventing the creation of Knowledge Base Index Entries in deployments with a large number of indices/mappings (#231376) (#231717)

# Backport

This will backport the following commits from `main` to `9.1`:
- [[Security Assistant] Fixes issue preventing the creation of Knowledge
Base Index Entries in deployments with a large number of
indices/mappings
(#231376)](#231376)

<!--- Backport version: 10.0.1 -->

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

<!--BACKPORT [{"author":{"name":"Garrett
Spong","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-08-13T22:33:31Z","message":"[Security
Assistant] Fixes issue preventing the creation of Knowledge Base Index
Entries in deployments with a large number of indices/mappings
(#231376)\n\n## Summary\n\nThis PR fixes an issue with the Security
Assistant KB Index Entries\ninterface introduced in `9.1` where a large
number of indices/mappings\ncould result in Kibana crashing and
preventing the creation of the Index\nEntry.\n\nThis is technically a
'fix-hancement' as we are bypassing the underlying\nissue altogether by
switching to use common core API's for index/field\nsuggestions (just as
is done in the Discover 'Create a data view'\ninterface), and in turn
supporting all fields of type `text`, not just\n`semantic_text`
(https://github.com/elastic/kibana/issues/230863).\n\n### Original
Issue\nThe underlying issue here was introduced by a change to the
`field_caps`\nAPI in `9.1`
(elastic/elasticsearch#127664) that\nresulted in
the `/internal/elastic_assistant/knowledge_base/_indices`\nroute not
finding any indices with a `semantic_text` field, and
thus\ninadvertently falling back to doing a full scan of all
mappings\n([source](https://github.com/elastic/kibana/blob/b128cee4ee7ccc367e8acf159dbf58a75f081867/x-pack/solutions/security/plugins/elastic_assistant/server/routes/knowledge_base/get_knowledge_base_indices.ts#L69)).\nA
fix to this API was initially investigated, but there was no\nreasonable
API available for fetching all occurrences of `semantic_text`\nfields,
so with `match` queries adding support for `semantic_text` in\n`8.18`,
it was decided to go ahead and enable support for all
`text`\nfields.\n\n\n### Fix Details\n\nThe `Index` input field now uses
the `dataViews.getIndices()` API for\nsuggestions (instead of the
`useKnowledgeBaseIndices` hook/route), which\nis backed by the [resolve
indices
ES\nAPI](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index).\nSystem
indices are filtered out with the `*,-.*` filter. The initial\ncall will
return all indices just as the Discover 'Create a data view'\ninterface,
which is further filtered upon as the user continues to type.\nNote:
Discover makes subsequent calls upon further user input, though\nI'm not
entirely sure this is necessary here as all indices are\ninitially
returned and available for client-side filtering within the\ninput. I
will perform further stress testing with many indices/mappings\nto
confirm.\n\nThe `Field` input now uses the fields already queried for
the `Output\nfields` input suggestions (via
`dataViews.getFieldsForWildcard()`), just\nfiltered to those whose
`field.esTypes?.includes('text')`. This is\npotentially still a hot path
for client-side code with many mappings, so\nI will also confirm this
with further stress testing.\n\n\n### Docs\n\n@elastic/security-docs /
@benironside, we will need to update the\nSecurity Assistant KB
docs\n[here](https://www.elastic.co/docs/solutions/security/ai/ai-assistant-knowledge-base#knowledge-base-add-knowledge-index)\nto
indicate that any `text` field is now supported for retrieval.\n\n\n###
Testing\n\n#### Functional Testing\n\nTo confirm proper retrieval of
both `text` and `semantic_text` fields\nwe'll need to create an index,
add a document, then create the KB Index\nEntry. Then update the KB
Index Entry to reference the other field type,\nand test
again.\n\n<details><summary>Create Index</summary>\n<p>\n\n``` JSON\nPUT
project-details\n{\n \"mappings\": {\n \"properties\": {\n
\"project_issue\": {\n \"type\": \"text\"\n },\n \"project_name\": {\n
\"type\": \"text\"\n },\n \"summary\": {\n \"type\":
\"semantic_text\",\n \"inference_id\": \".elser-2-elasticsearch\",\n
\"model_settings\": {\n \"service\": \"elasticsearch\",\n \"task_type\":
\"sparse_embedding\"\n }\n }\n }\n }\n}\n```\n</p>\n</details>
\n\n<details><summary>Create Sample Doc</summary>\n<p>\n\n``` JSON\nPUT
project-details/_doc/doc1\n{\n \"project_issue\": \"The main issue at
hand is the breaking of the space plane\",\n \"project_name\": \"Issue
5\",\n \"summary\": \"This is a summary that contains the word
yellow\"\n}\n```\n</p>\n</details> \n\n<details><summary>Create KB Index
Entry (Text)</summary>\n<p>\n\n``` JSON\nPOST
kbn:api/security_ai_assistant/knowledge_base/entries\n{\n \"type\":
\"index\",\n \"name\": \"Project Details Tool\",\n \"index\":
\"project-details\",\n \"field\": \"project_issue\",\n \"outputFields\":
[],\n \"description\": \"Use this index to answer questions about any
project details.\",\n \"queryDescription\": \"Key terms to search for
from the user's prompt.\"\n}\n```\n</p>\n</details> \n\nNow you can open
the Assistant and perform a query like:\n```\nDo I have any project
details about the issue at hand?\n```\n\nWhich should result in a [trace
like\nthis](https://smith.langchain.com/public/208338a6-42f3-4a9d-bc4c-0ff38d06d34c/r)\nwhich
calls the generated tool that will then perform a _lexical
search_\nagainst the configured index. Ensure citations work as expected
for the\nreturned document.\n\nNow open the Index Entry in the KB
Settings UI and change the `field` to\nfrom `project_issue` to `summary`
for testing `semantic_text`.\n\nOpen the Assistant and perform a query
like:\n```\nDo I have any project details for Project
Yellow?\n```\n\nWhich should result in a [trace
like\nthis](https://smith.langchain.com/public/3041a48b-5dfd-4c89-9f51-0bcdffd38f63/r)\nwhich
calls the generated tool that will then perform a _semantic\nsearch_
against the configured index. Ensure citations work as expected\nfor the
returned document.\n\n\n\n\n\n\n\n#### Performance Testing\n\n⚠️ In
progress -- I will include a script for generating
many\nindices/mappings for testing, and also prepare the
`ci-cloud-deploy`\ninstance with the same setup for
confirmation.\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] 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 * Will
coordinate with @elastic/security-docs on the docs update here.\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: kibanamachine
<[email protected]>","sha":"4496b50237b5d6ff8acb105662912268717bf3f6","branchLabelMapping":{"^v9.2.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["bug","release_note:fix","needs_docs","sdh-linked","ci:cloud-deploy","Team:Security
Generative AI","backport:version","v9.2.0","v9.1.3"],"title":"[Security
Assistant] Fixes issue preventing the creation of Knowledge Base Index
Entries in deployments with a large number of
indices/mappings","number":231376,"url":"https://github.com/elastic/kibana/pull/231376","mergeCommit":{"message":"[Security
Assistant] Fixes issue preventing the creation of Knowledge Base Index
Entries in deployments with a large number of indices/mappings
(#231376)\n\n## Summary\n\nThis PR fixes an issue with the Security
Assistant KB Index Entries\ninterface introduced in `9.1` where a large
number of indices/mappings\ncould result in Kibana crashing and
preventing the creation of the Index\nEntry.\n\nThis is technically a
'fix-hancement' as we are bypassing the underlying\nissue altogether by
switching to use common core API's for index/field\nsuggestions (just as
is done in the Discover 'Create a data view'\ninterface), and in turn
supporting all fields of type `text`, not just\n`semantic_text`
(https://github.com/elastic/kibana/issues/230863).\n\n### Original
Issue\nThe underlying issue here was introduced by a change to the
`field_caps`\nAPI in `9.1`
(elastic/elasticsearch#127664) that\nresulted in
the `/internal/elastic_assistant/knowledge_base/_indices`\nroute not
finding any indices with a `semantic_text` field, and
thus\ninadvertently falling back to doing a full scan of all
mappings\n([source](https://github.com/elastic/kibana/blob/b128cee4ee7ccc367e8acf159dbf58a75f081867/x-pack/solutions/security/plugins/elastic_assistant/server/routes/knowledge_base/get_knowledge_base_indices.ts#L69)).\nA
fix to this API was initially investigated, but there was no\nreasonable
API available for fetching all occurrences of `semantic_text`\nfields,
so with `match` queries adding support for `semantic_text` in\n`8.18`,
it was decided to go ahead and enable support for all
`text`\nfields.\n\n\n### Fix Details\n\nThe `Index` input field now uses
the `dataViews.getIndices()` API for\nsuggestions (instead of the
`useKnowledgeBaseIndices` hook/route), which\nis backed by the [resolve
indices
ES\nAPI](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index).\nSystem
indices are filtered out with the `*,-.*` filter. The initial\ncall will
return all indices just as the Discover 'Create a data view'\ninterface,
which is further filtered upon as the user continues to type.\nNote:
Discover makes subsequent calls upon further user input, though\nI'm not
entirely sure this is necessary here as all indices are\ninitially
returned and available for client-side filtering within the\ninput. I
will perform further stress testing with many indices/mappings\nto
confirm.\n\nThe `Field` input now uses the fields already queried for
the `Output\nfields` input suggestions (via
`dataViews.getFieldsForWildcard()`), just\nfiltered to those whose
`field.esTypes?.includes('text')`. This is\npotentially still a hot path
for client-side code with many mappings, so\nI will also confirm this
with further stress testing.\n\n\n### Docs\n\n@elastic/security-docs /
@benironside, we will need to update the\nSecurity Assistant KB
docs\n[here](https://www.elastic.co/docs/solutions/security/ai/ai-assistant-knowledge-base#knowledge-base-add-knowledge-index)\nto
indicate that any `text` field is now supported for retrieval.\n\n\n###
Testing\n\n#### Functional Testing\n\nTo confirm proper retrieval of
both `text` and `semantic_text` fields\nwe'll need to create an index,
add a document, then create the KB Index\nEntry. Then update the KB
Index Entry to reference the other field type,\nand test
again.\n\n<details><summary>Create Index</summary>\n<p>\n\n``` JSON\nPUT
project-details\n{\n \"mappings\": {\n \"properties\": {\n
\"project_issue\": {\n \"type\": \"text\"\n },\n \"project_name\": {\n
\"type\": \"text\"\n },\n \"summary\": {\n \"type\":
\"semantic_text\",\n \"inference_id\": \".elser-2-elasticsearch\",\n
\"model_settings\": {\n \"service\": \"elasticsearch\",\n \"task_type\":
\"sparse_embedding\"\n }\n }\n }\n }\n}\n```\n</p>\n</details>
\n\n<details><summary>Create Sample Doc</summary>\n<p>\n\n``` JSON\nPUT
project-details/_doc/doc1\n{\n \"project_issue\": \"The main issue at
hand is the breaking of the space plane\",\n \"project_name\": \"Issue
5\",\n \"summary\": \"This is a summary that contains the word
yellow\"\n}\n```\n</p>\n</details> \n\n<details><summary>Create KB Index
Entry (Text)</summary>\n<p>\n\n``` JSON\nPOST
kbn:api/security_ai_assistant/knowledge_base/entries\n{\n \"type\":
\"index\",\n \"name\": \"Project Details Tool\",\n \"index\":
\"project-details\",\n \"field\": \"project_issue\",\n \"outputFields\":
[],\n \"description\": \"Use this index to answer questions about any
project details.\",\n \"queryDescription\": \"Key terms to search for
from the user's prompt.\"\n}\n```\n</p>\n</details> \n\nNow you can open
the Assistant and perform a query like:\n```\nDo I have any project
details about the issue at hand?\n```\n\nWhich should result in a [trace
like\nthis](https://smith.langchain.com/public/208338a6-42f3-4a9d-bc4c-0ff38d06d34c/r)\nwhich
calls the generated tool that will then perform a _lexical
search_\nagainst the configured index. Ensure citations work as expected
for the\nreturned document.\n\nNow open the Index Entry in the KB
Settings UI and change the `field` to\nfrom `project_issue` to `summary`
for testing `semantic_text`.\n\nOpen the Assistant and perform a query
like:\n```\nDo I have any project details for Project
Yellow?\n```\n\nWhich should result in a [trace
like\nthis](https://smith.langchain.com/public/3041a48b-5dfd-4c89-9f51-0bcdffd38f63/r)\nwhich
calls the generated tool that will then perform a _semantic\nsearch_
against the configured index. Ensure citations work as expected\nfor the
returned document.\n\n\n\n\n\n\n\n#### Performance Testing\n\n⚠️ In
progress -- I will include a script for generating
many\nindices/mappings for testing, and also prepare the
`ci-cloud-deploy`\ninstance with the same setup for
confirmation.\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] 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 * Will
coordinate with @elastic/security-docs on the docs update here.\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: kibanamachine
<[email protected]>","sha":"4496b50237b5d6ff8acb105662912268717bf3f6"}},"sourceBranch":"main","suggestedTargetBranches":["9.1"],"targetPullRequestStates":[{"branch":"main","label":"v9.2.0","branchLabelMappingKey":"^v9.2.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/231376","number":231376,"mergeCommit":{"message":"[Security
Assistant] Fixes issue preventing the creation of Knowledge Base Index
Entries in deployments with a large number of indices/mappings
(#231376)\n\n## Summary\n\nThis PR fixes an issue with the Security
Assistant KB Index Entries\ninterface introduced in `9.1` where a large
number of indices/mappings\ncould result in Kibana crashing and
preventing the creation of the Index\nEntry.\n\nThis is technically a
'fix-hancement' as we are bypassing the underlying\nissue altogether by
switching to use common core API's for index/field\nsuggestions (just as
is done in the Discover 'Create a data view'\ninterface), and in turn
supporting all fields of type `text`, not just\n`semantic_text`
(https://github.com/elastic/kibana/issues/230863).\n\n### Original
Issue\nThe underlying issue here was introduced by a change to the
`field_caps`\nAPI in `9.1`
(elastic/elasticsearch#127664) that\nresulted in
the `/internal/elastic_assistant/knowledge_base/_indices`\nroute not
finding any indices with a `semantic_text` field, and
thus\ninadvertently falling back to doing a full scan of all
mappings\n([source](https://github.com/elastic/kibana/blob/b128cee4ee7ccc367e8acf159dbf58a75f081867/x-pack/solutions/security/plugins/elastic_assistant/server/routes/knowledge_base/get_knowledge_base_indices.ts#L69)).\nA
fix to this API was initially investigated, but there was no\nreasonable
API available for fetching all occurrences of `semantic_text`\nfields,
so with `match` queries adding support for `semantic_text` in\n`8.18`,
it was decided to go ahead and enable support for all
`text`\nfields.\n\n\n### Fix Details\n\nThe `Index` input field now uses
the `dataViews.getIndices()` API for\nsuggestions (instead of the
`useKnowledgeBaseIndices` hook/route), which\nis backed by the [resolve
indices
ES\nAPI](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index).\nSystem
indices are filtered out with the `*,-.*` filter. The initial\ncall will
return all indices just as the Discover 'Create a data view'\ninterface,
which is further filtered upon as the user continues to type.\nNote:
Discover makes subsequent calls upon further user input, though\nI'm not
entirely sure this is necessary here as all indices are\ninitially
returned and available for client-side filtering within the\ninput. I
will perform further stress testing with many indices/mappings\nto
confirm.\n\nThe `Field` input now uses the fields already queried for
the `Output\nfields` input suggestions (via
`dataViews.getFieldsForWildcard()`), just\nfiltered to those whose
`field.esTypes?.includes('text')`. This is\npotentially still a hot path
for client-side code with many mappings, so\nI will also confirm this
with further stress testing.\n\n\n### Docs\n\n@elastic/security-docs /
@benironside, we will need to update the\nSecurity Assistant KB
docs\n[here](https://www.elastic.co/docs/solutions/security/ai/ai-assistant-knowledge-base#knowledge-base-add-knowledge-index)\nto
indicate that any `text` field is now supported for retrieval.\n\n\n###
Testing\n\n#### Functional Testing\n\nTo confirm proper retrieval of
both `text` and `semantic_text` fields\nwe'll need to create an index,
add a document, then create the KB Index\nEntry. Then update the KB
Index Entry to reference the other field type,\nand test
again.\n\n<details><summary>Create Index</summary>\n<p>\n\n``` JSON\nPUT
project-details\n{\n \"mappings\": {\n \"properties\": {\n
\"project_issue\": {\n \"type\": \"text\"\n },\n \"project_name\": {\n
\"type\": \"text\"\n },\n \"summary\": {\n \"type\":
\"semantic_text\",\n \"inference_id\": \".elser-2-elasticsearch\",\n
\"model_settings\": {\n \"service\": \"elasticsearch\",\n \"task_type\":
\"sparse_embedding\"\n }\n }\n }\n }\n}\n```\n</p>\n</details>
\n\n<details><summary>Create Sample Doc</summary>\n<p>\n\n``` JSON\nPUT
project-details/_doc/doc1\n{\n \"project_issue\": \"The main issue at
hand is the breaking of the space plane\",\n \"project_name\": \"Issue
5\",\n \"summary\": \"This is a summary that contains the word
yellow\"\n}\n```\n</p>\n</details> \n\n<details><summary>Create KB Index
Entry (Text)</summary>\n<p>\n\n``` JSON\nPOST
kbn:api/security_ai_assistant/knowledge_base/entries\n{\n \"type\":
\"index\",\n \"name\": \"Project Details Tool\",\n \"index\":
\"project-details\",\n \"field\": \"project_issue\",\n \"outputFields\":
[],\n \"description\": \"Use this index to answer questions about any
project details.\",\n \"queryDescription\": \"Key terms to search for
from the user's prompt.\"\n}\n```\n</p>\n</details> \n\nNow you can open
the Assistant and perform a query like:\n```\nDo I have any project
details about the issue at hand?\n```\n\nWhich should result in a [trace
like\nthis](https://smith.langchain.com/public/208338a6-42f3-4a9d-bc4c-0ff38d06d34c/r)\nwhich
calls the generated tool that will then perform a _lexical
search_\nagainst the configured index. Ensure citations work as expected
for the\nreturned document.\n\nNow open the Index Entry in the KB
Settings UI and change the `field` to\nfrom `project_issue` to `summary`
for testing `semantic_text`.\n\nOpen the Assistant and perform a query
like:\n```\nDo I have any project details for Project
Yellow?\n```\n\nWhich should result in a [trace
like\nthis](https://smith.langchain.com/public/3041a48b-5dfd-4c89-9f51-0bcdffd38f63/r)\nwhich
calls the generated tool that will then perform a _semantic\nsearch_
against the configured index. Ensure citations work as expected\nfor the
returned document.\n\n\n\n\n\n\n\n#### Performance Testing\n\n⚠️ In
progress -- I will include a script for generating
many\nindices/mappings for testing, and also prepare the
`ci-cloud-deploy`\ninstance with the same setup for
confirmation.\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] 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 * Will
coordinate with @elastic/security-docs on the docs update here.\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: kibanamachine
<[email protected]>","sha":"4496b50237b5d6ff8acb105662912268717bf3f6"}},{"branch":"9.1","label":"v9.1.3","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}]
BACKPORT-->

Author: spong

src/platform/packages/shared/kbn-doc-links/src/get_doc_links.ts

@@ -482,7 +482,9 @@ export const getDocLinks = ({ kibanaBranch, buildFlavor }: GetDocLinkOptions): D
         mlAnomalyDetection: `${ELASTIC_DOCS}explore-analyze/machine-learning/anomaly-detection`,
       },
       detectionEngineOverview: `${ELASTIC_DOCS}solutions/security/detect-and-alert`,
+      // TODO: Follow-up PR for creating an aiAssistant category adding all relevant doc links
       aiAssistant: `${ELASTIC_DOCS}solutions/security/ai/ai-assistant`,
+      aiAssistantKnowledgeBaseIndexEntries: `${ELASTIC_DOCS}solutions/security/ai/ai-assistant-knowledge-base#knowledge-base-add-knowledge-index`,
       signalsMigrationApi: isServerless
         ? `${KIBANA_APIS}group/endpoint-security-detections-api`
         : `${KIBANA_SERVERLESS_APIS}group/endpoint-security-detections-api`,

src/platform/packages/shared/kbn-doc-links/src/types.ts

@@ -301,6 +301,7 @@ export interface DocLinks {
   };
   readonly securitySolution: {
     readonly aiAssistant: string;
+    readonly aiAssistantKnowledgeBaseIndexEntries: string;
     readonly cloudSecurityPosture: string;
     readonly installElasticDefend: string;
     readonly artifactControl: string;

x-pack/platform/packages/shared/kbn-elastic-assistant-common/constants.ts

@@ -54,8 +54,6 @@ export const ELASTIC_AI_ASSISTANT_KNOWLEDGE_BASE_ENTRIES_URL_FIND =
 export const ELASTIC_AI_ASSISTANT_KNOWLEDGE_BASE_ENTRIES_URL_BULK_ACTION =
   `${ELASTIC_AI_ASSISTANT_KNOWLEDGE_BASE_ENTRIES_URL}/_bulk_action` as const;
 
-export const ELASTIC_AI_ASSISTANT_KNOWLEDGE_BASE_INDICES_URL =
-  `${ELASTIC_AI_ASSISTANT_INTERNAL_URL}/knowledge_base/_indices` as const;
 export const ELASTIC_AI_ASSISTANT_EVALUATE_URL =
   `${ELASTIC_AI_ASSISTANT_INTERNAL_URL}/evaluate` as const;
 

x-pack/platform/packages/shared/kbn-elastic-assistant-common/impl/schemas/index.ts

@@ -60,7 +60,6 @@ export * from './actions_connector/post_actions_connector_execute_route.gen';
 
 // Knowledge Base Schemas
 export * from './knowledge_base/crud_kb_route.gen';
-export * from './knowledge_base/get_knowledge_base_indices_route.gen';
 export * from './knowledge_base/entries/bulk_crud_knowledge_base_entries_route.gen';
 export * from './knowledge_base/entries/common_attributes.gen';
 export * from './knowledge_base/entries/crud_knowledge_base_entries_route.gen';

x-pack/platform/packages/shared/kbn-elastic-assistant-common/impl/schemas/knowledge_base/get_knowledge_base_indices_route.gen.ts

@@ -7,7 +7,7 @@
 
 import { HttpSetup } from '@kbn/core-http-browser';
 
-import { getKnowledgeBaseIndices, getKnowledgeBaseStatus, postKnowledgeBase } from './api';
+import { getKnowledgeBaseStatus, postKnowledgeBase } from './api';
 import { API_VERSIONS } from '@kbn/spaces-plugin/common';
 
 jest.mock('@kbn/core-http-browser');
@@ -73,29 +73,4 @@ describe('API tests', () => {
       await expect(postKnowledgeBase(knowledgeBaseArgs)).rejects.toThrowError('simulated error');
     });
   });
-
-  describe('getKnowledgeBaseIndices', () => {
-    it('calls the knowledge base API when correct resource path', async () => {
-      await getKnowledgeBaseIndices({ http: mockHttp });
-
-      expect(mockHttp.fetch).toHaveBeenCalledWith(
-        '/internal/elastic_assistant/knowledge_base/_indices',
-        {
-          method: 'GET',
-          signal: undefined,
-          version: '1',
-        }
-      );
-    });
-    it('returns error when error is an error', async () => {
-      const error = 'simulated error';
-      (mockHttp.fetch as jest.Mock).mockImplementation(() => {
-        throw new Error(error);
-      });
-
-      await expect(getKnowledgeBaseIndices({ http: mockHttp })).resolves.toThrowError(
-        'simulated error'
-      );
-    });
-  });
 });

x-pack/platform/packages/shared/kbn-elastic-assistant-common/impl/schemas/knowledge_base/get_knowledge_base_indices_route.schema.yaml

@@ -9,9 +9,7 @@ import {
   API_VERSIONS,
   CreateKnowledgeBaseRequestParams,
   CreateKnowledgeBaseResponse,
-  ELASTIC_AI_ASSISTANT_KNOWLEDGE_BASE_INDICES_URL,
   ELASTIC_AI_ASSISTANT_KNOWLEDGE_BASE_URL,
-  GetKnowledgeBaseIndicesResponse,
   ReadKnowledgeBaseRequestParams,
   ReadKnowledgeBaseResponse,
 } from '@kbn/elastic-assistant-common';
@@ -76,32 +74,3 @@ export const postKnowledgeBase = async ({
 
   return response as CreateKnowledgeBaseResponse;
 };
-
-/**
- * API call for getting indices that have fields of `semantic_text` type.
- *
- * @param {Object} options - The options object.
- * @param {HttpSetup} options.http - HttpSetup
- * @param {AbortSignal} [options.signal] - AbortSignal
- *
- * @returns {Promise<GetKnowledgeBaseIndicesResponse | IHttpFetchError>}
- */
-export const getKnowledgeBaseIndices = async ({
-  http,
-  signal,
-}: {
-  http: HttpSetup;
-  signal?: AbortSignal | undefined;
-}): Promise<GetKnowledgeBaseIndicesResponse | IHttpFetchError> => {
-  try {
-    const response = await http.fetch(ELASTIC_AI_ASSISTANT_KNOWLEDGE_BASE_INDICES_URL, {
-      method: 'GET',
-      signal,
-      version: API_VERSIONS.internal.v1,
-    });
-
-    return response as GetKnowledgeBaseIndicesResponse;
-  } catch (error) {
-    return error as IHttpFetchError;
-  }
-};