[ML][AI Connector] Adds a default placeholder icon for future AI connectors by KodeRad · Pull Request #235166 · elastic/kibana

KodeRad · 2025-09-16T08:09:38Z

Summary

Implements #233668

In case backend adds new AI connector it will be displayed with a default placeholder icon instead without any.

Additionaly, it now highlights new providers when searched for them in the list. Just like the others.

To test it I deleted alibabacloud-ai-search connector from SERVICE_PROVIDERS imitating the situation where the new provider was added.

Screenshots before

Screenshots after

Highlight searched names (mind that recording has old greyed-out icon)

highlight.mp4

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
Documentation was added for features that require explanation or tutorials
Unit or functional tests were updated or added to match the most common scenarios
If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
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.
Flaky Test Runner was used on any tests changed
The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

See some risk examples
...

elasticmachine · 2025-09-16T11:07:14Z

Pinging @elastic/ml-ui (:ml)

peteharverson

Tested and LGTM. Just left one comment.

peteharverson · 2025-09-17T11:17:22Z

...nce-endpoint-ui-common/src/components/providers/render_service_provider/service_provider.tsx

 import deepSeekIcon from '../assets/images/deepseek.svg';
 import ai21Icon from '../assets/images/ai21_labs_default.svg';
 import llamaIcon from '../assets/images/llama_stack_default.svg';
+import default_icon from '../assets/images/default_connector_icon.svg';


Nit - why not camel case defaultIcon for consistency with the others?

There is a linting rule about file names needing to be snake_case, but I agree that we should be consistent with the other names so it'd be ok to ignore the rule for this file.

That's right. For the consistency it's better to change it as the rest. Fixed here: 7329849

alvarezmelissa87

LGTM ⚡

elasticmachine · 2025-09-19T14:32:14Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: 9d2c783

Failed CI Steps

FTR Configs #77

Test Failures

[job] [logs] FTR Configs #77 / serverless security UI navigation navigate using search

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
`indexManagement`	673	674	+1
`searchInferenceEndpoints`	151	152	+1
`searchPlayground`	426	427	+1
`securitySolution`	8007	8008	+1
`stackConnectors`	364	365	+1
total			+5

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
`indexManagement`	689.5KB	691.1KB	+1.6KB
`searchInferenceEndpoints`	106.5KB	108.1KB	+1.6KB
`searchPlayground`	228.4KB	228.4KB	+2.0B
`stackConnectors`	705.7KB	707.3KB	+1.6KB
total			+4.7KB

History

💚 Build #340713 succeeded 7329849
💚 Build #339765 succeeded e784ff8
💔 Build #339646 failed cb92dde

cc @KodeRad

…ctors (elastic#235166) ## Summary Implements [elastic#233668](elastic#233668) In case backend adds new AI connector it will be displayed with a default placeholder icon instead without any. Additionaly, it now highlights new providers when searched for them in the list. Just like the others. To test it I deleted `alibabacloud-ai-search` connector from `SERVICE_PROVIDERS` imitating the situation where the new provider was added. ### Screenshots before <img width="984" height="1298" alt="Screenshot 2025-09-15 at 15 37 03" src="https://github.com/user-attachments/assets/7b85b316-5bf8-45a1-8e63-ec925f8d492f" /> <img width="736" height="1122" alt="Screenshot 2025-09-15 at 15 37 23" src="https://github.com/user-attachments/assets/d25c30cb-3f49-45e2-983a-f4a7cd383ade" /> ### Screenshots after <img width="989" height="575" alt="Screenshot 2025-09-16 at 16 38 08" src="https://github.com/user-attachments/assets/2d211a65-27d4-45f1-bf9e-878308e196de" /> <img width="984" height="843" alt="Screenshot 2025-09-16 at 16 38 35" src="https://github.com/user-attachments/assets/22918985-b2a7-4f44-9d66-0b5d453c70f6" /> ### Highlight searched names (mind that recording has old greyed-out icon) https://github.com/user-attachments/assets/4c14fef8-c1a3-4dbd-9780-f99073a8bfb2 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] 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. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

…ctors (#235166) ## Summary Implements [#233668](#233668) In case backend adds new AI connector it will be displayed with a default placeholder icon instead without any. Additionaly, it now highlights new providers when searched for them in the list. Just like the others. To test it I deleted `alibabacloud-ai-search` connector from `SERVICE_PROVIDERS` imitating the situation where the new provider was added. ### Screenshots before <img width="984" height="1298" alt="Screenshot 2025-09-15 at 15 37 03" src="https://github.com/user-attachments/assets/7b85b316-5bf8-45a1-8e63-ec925f8d492f" /> <img width="736" height="1122" alt="Screenshot 2025-09-15 at 15 37 23" src="https://github.com/user-attachments/assets/d25c30cb-3f49-45e2-983a-f4a7cd383ade" /> ### Screenshots after <img width="989" height="575" alt="Screenshot 2025-09-16 at 16 38 08" src="https://github.com/user-attachments/assets/2d211a65-27d4-45f1-bf9e-878308e196de" /> <img width="984" height="843" alt="Screenshot 2025-09-16 at 16 38 35" src="https://github.com/user-attachments/assets/22918985-b2a7-4f44-9d66-0b5d453c70f6" /> ### Highlight searched names (mind that recording has old greyed-out icon) https://github.com/user-attachments/assets/4c14fef8-c1a3-4dbd-9780-f99073a8bfb2 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] 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. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

…ctors (elastic#235166) ## Summary Implements [elastic#233668](elastic#233668) In case backend adds new AI connector it will be displayed with a default placeholder icon instead without any. Additionaly, it now highlights new providers when searched for them in the list. Just like the others. To test it I deleted `alibabacloud-ai-search` connector from `SERVICE_PROVIDERS` imitating the situation where the new provider was added. ### Screenshots before <img width="984" height="1298" alt="Screenshot 2025-09-15 at 15 37 03" src="https://github.com/user-attachments/assets/7b85b316-5bf8-45a1-8e63-ec925f8d492f" /> <img width="736" height="1122" alt="Screenshot 2025-09-15 at 15 37 23" src="https://github.com/user-attachments/assets/d25c30cb-3f49-45e2-983a-f4a7cd383ade" /> ### Screenshots after <img width="989" height="575" alt="Screenshot 2025-09-16 at 16 38 08" src="https://github.com/user-attachments/assets/2d211a65-27d4-45f1-bf9e-878308e196de" /> <img width="984" height="843" alt="Screenshot 2025-09-16 at 16 38 35" src="https://github.com/user-attachments/assets/22918985-b2a7-4f44-9d66-0b5d453c70f6" /> ### Highlight searched names (mind that recording has old greyed-out icon) https://github.com/user-attachments/assets/4c14fef8-c1a3-4dbd-9780-f99073a8bfb2 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [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 - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] 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. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ...

KodeRad added 2 commits September 15, 2025 15:29

add default placeholder icon for future ai connectors

b45e552

highlight new connectors in the list and add tests

cb92dde

KodeRad self-assigned this Sep 16, 2025

KodeRad added :ml release_note:skip Skip the PR/issue when compiling release notes backport:skip This PR does not require backporting Team:ML Team label for ML (also use :ml) t// Feature:Inference UI ML Inference endpoints UI and AI connector labels Sep 16, 2025

KodeRad marked this pull request as ready for review September 16, 2025 11:07

KodeRad requested a review from a team as a code owner September 16, 2025 11:07

Merge branch 'main' into ml-ai-connector-add-default-icon

e784ff8

KodeRad requested review from alvarezmelissa87, jgowdyelastic and peteharverson September 16, 2025 11:15

change default icon

7b73c7a

peteharverson changed the title ~~[ML][AI Connector] Add a default placeholder icon for future ai connectors~~ Sep 17, 2025

peteharverson added release_note:enhancement and removed release_note:skip Skip the PR/issue when compiling release notes labels Sep 17, 2025

peteharverson mentioned this pull request Sep 17, 2025

[ML][Meta] Increase Test Coverage 9.2.0 #228743

Closed

12 tasks

peteharverson approved these changes Sep 17, 2025

View reviewed changes

change name for consistency

7329849

alvarezmelissa87 approved these changes Sep 18, 2025

View reviewed changes

Merge branch 'main' into ml-ai-connector-add-default-icon

001006c

KodeRad enabled auto-merge (squash) September 19, 2025 10:48

Merge branch 'main' into ml-ai-connector-add-default-icon

9d2c783

KodeRad merged commit e5cfd1e into elastic:main Sep 19, 2025
12 checks passed

kibanamachine added the v9.2.0 label Sep 19, 2025

peteharverson mentioned this pull request Sep 22, 2025

[ML][AI Connector] Add default icon for future AI Connectors #233668

Closed

1 task

peteharverson changed the title ~~[ML][AI Connector] Add a default placeholder icon for future AI connectors~~ Sep 24, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[ML][AI Connector] Adds a default placeholder icon for future AI connectors#235166

[ML][AI Connector] Adds a default placeholder icon for future AI connectors#235166
KodeRad merged 7 commits intoelastic:mainfrom
KodeRad:ml-ai-connector-add-default-icon

KodeRad commented Sep 16, 2025 •

edited

Loading

elasticmachine commented Sep 16, 2025

peteharverson left a comment

peteharverson Sep 17, 2025

jgowdyelastic Sep 17, 2025 •

edited

Loading

KodeRad Sep 18, 2025

alvarezmelissa87 left a comment

Uh oh!

elasticmachine commented Sep 19, 2025

Labels

6 participants

Conversation

KodeRad commented Sep 16, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Screenshots before

Screenshots after

Highlight searched names (mind that recording has old greyed-out icon)

Checklist

Identify risks

elasticmachine commented Sep 16, 2025

peteharverson left a comment

Choose a reason for hiding this comment

peteharverson Sep 17, 2025

Choose a reason for hiding this comment

jgowdyelastic Sep 17, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

KodeRad Sep 18, 2025

Choose a reason for hiding this comment

alvarezmelissa87 left a comment

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Sep 19, 2025

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

Metrics [docs]

Module Count

Async chunks

History

Labels

6 participants

KodeRad commented Sep 16, 2025 •

edited

Loading

jgowdyelastic Sep 17, 2025 •

edited

Loading