[FIX] Add search by name filter to Model Endpoints 'Filter by' popup by arturrybalskyy-dev · Pull Request #3775 · mlrun/ui · GitHub
Skip to content

[FIX] Add search by name filter to Model Endpoints 'Filter by' popup - #3775

Draft
arturrybalskyy-dev wants to merge 1 commit into
mlrun:developmentfrom
arturrybalskyy-dev:fix/model-endpoints-search-by-name
Draft

arturrybalskyy-dev wants to merge 1 commit into
mlrun:developmentfrom
arturrybalskyy-dev:fix/model-endpoints-search-by-name

Conversation

@arturrybalskyy-dev

Copy link
Copy Markdown
Contributor

📝 Description

Adds a Name filter to the "Filter by" popup on the Model Endpoints tab, both on the main Model Endpoints page and in the Real-time pipeline details pane. Previously the Model Endpoints tab had no search by name.

While investigating the API, I also found that the UI was sending latest_only, but the backend accepts only the latest-only alias (Query(False, alias="latest-only") since mlrun v1.8.0). As a result the parameter was silently ignored. This is fixed in all 5 places that call the model endpoints list


🛠️ Changes Made

  • Added Name input to ModelEndpointsFilters (shown in the "Filter by" popup).
  • Added NAME_FILTER to the filters config of the main Model Endpoints page and of the pipeline details pane.
  • getModelEndpoints API:
    • sends name as a list param, as the API expects (array<string>); empty or whitespace-only values are not sent
    • no longer mutates the params object passed by the caller
    • defaults filters to {}
  • Renamed latest_only → latest-only query param in ModelEndpoints, DetailsModelEndpoints, ApplicationMetrics, ApplicationMonitoringEndpoints and useNuclioEnrichedFunctions.
  • Mock server:
    • name, function-name, function-tag and latest-only filters now work independently and use the same param names as the backend
    • previously function-name was ignored, so the pipeline details pane showed all project endpoints
  • Mock data: added 3 model endpoints for test-pipeline, so the details pane filters can be checked on the mock.

✅ Checklist

  • I have given the PR a well-structured title describing the domain and the specific change that was made
  • I tested the changes in the browser (locally or via preview build)
  • I confirmed that existing tests pass
  • I added or updated unit / integration tests (if needed)
  • I checked that this change doesn’t introduce new console warnings or lint / formatting errors
  • I updated the relevant Jira ticket with the appropriate details and status

🔗 References

  • Related ticket / issue: Link

🚨 Potentially Breaking Changes

  • Yes
  • No

Includes DRC change

  • Yes
  • No

@arturrybalskyy-dev
arturrybalskyy-dev marked this pull request as draft October 12, 2026 07:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant