[ML] AI Connector: Adds ability to filter providers by solution type#228116
Conversation
|
Pinging @elastic/ml-ui (:ml) |
…com:alvarezmelissa87/kibana into ml-ai-connector-filter-providers-by-project
|
@elasticmachine merge upstream |
Samiul-TheSoccerFan
left a comment
There was a problem hiding this comment.
kbn-inference-endpoint-ui-common changes look good.
|
@elasticmachine merge upstream |
x-pack/platform/plugins/shared/stack_connectors/public/connector_types/inference/connector.tsx
Show resolved
Hide resolved
x-pack/platform/plugins/shared/stack_connectors/public/connector_types/inference/connector.tsx
Show resolved
Hide resolved
...orm/packages/shared/kbn-inference-endpoint-ui-common/src/components/providers/selectable.tsx
Show resolved
Hide resolved
...orm/packages/shared/kbn-inference-endpoint-ui-common/src/components/providers/selectable.tsx
Outdated
Show resolved
Hide resolved
...ges/shared/kbn-inference-endpoint-ui-common/src/components/inference_service_form_fields.tsx
Outdated
Show resolved
Hide resolved
...ges/shared/kbn-inference-endpoint-ui-common/src/components/inference_service_form_fields.tsx
Outdated
Show resolved
Hide resolved
|
@elasticmachine merge upstream |
|
merge conflict between base and head |
|
/ci |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
💚 Build Succeeded
Metrics [docs]Module Count
Async chunks
Page load bundle
History
|
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
2 similar comments
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
|
Friendly reminder: Looks like this PR hasn’t been backported yet. |
…lastic#228116) ## Summary Related issue: elastic#218499 This PR adds filters for each of the project types so the list of providers can be filtered by solution/project type. The filter will be enabled by default for the current solution/project type. The filter will only be shown when user is in applicable space solution or in applicable serverless project. If the user is in classic mode, no filter will be shown. For Observability solution in space: <img width="944" height="829" alt="image" src="https://github.com/user-attachments/assets/d5a29cf0-267a-4cf6-b290-835bff2dd908" /> ## NOTE: The `EuiSelectable` accepts `searchProps` with an `append` property that appends nodes to the end of the search bar but it always had that odd gray space in between as shown below. That's why I decided not to use that prop. Adding the filters after the search bar directly as children of the component looked a lot better (screenshot above). <img width="916" height="315" alt="image" src="https://github.com/user-attachments/assets/0642cb0b-9a06-40c2-97a1-d4d9007b1b9c" /> ### 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. --------- Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
Summary
Related issue: #218499
This PR adds filters for each of the project types so the list of providers can be filtered by solution/project type.
The filter will be enabled by default for the current solution/project type.
The filter will only be shown when user is in applicable space solution or in applicable serverless project. If the user is in classic mode, no filter will be shown.
For Observability solution in space:
NOTE:
The
EuiSelectableacceptssearchPropswith anappendproperty that appends nodes to the end of the search bar but it always had that odd gray space in between as shown below. That's why I decided not to use that prop. Adding the filters after the search bar directly as children of the component looked a lot better (screenshot above).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_note:*label is applied per the guidelinesbackport:*labels.