lablup / lablup/backend.ai-webui
Fix version gating of Deployments page filters and orderings added after 26.4.0
- Dominant language
- TypeScript
- Stars
- 133
- Forks
- 81
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 355
Description
Page: /admin/deployments. Source: report-deployments.md section 0 (findings A-D), verified against backend tags.
- Deployments tab: the default filter `status: { notIn: [STOPPED] `} uses `notIn`, added in 26.4.3 -> the tab fails to load on 26.4.0-26.4.2. Gate with `model-deployment-extended-filter` (26.4.3) and fall back to an `in` list of non-STOPPED statuses on older managers.
- Deployments tab: DOMAIN / PROJECT / RESOURCE_GROUP / TAG sorters were added in 26.4.3 (26.4.0 had NAME/CREATED_AT/UPDATED_AT only) but are enabled unconditionally -> gate them with the same flag as the filters.
- Model Store, Runtime Variant Preset, Deployment Preset tabs: `projectId`, `domainName`, `runtimeVariantId` filters changed shape in 26.4.4rc3 (UUID -> UUIDFilter, String -> StringFilter). Add a flag (26.4.4) and hide those filter properties on older managers.
- Prometheus Preset tab: `categoryId` filter and AND/OR/NOT were added in 26.4.4 while the tab gate is 26.4.2 -> gate the property and restrict to a single condition below 26.4.4.
- Model Store / Deployment Preset / Prometheus tabs: AND/OR/NOT combinators are not gated (`sub-filter` 26.7.0 for presets, 26.4.1 for model cards). Apply the same single-condition restriction the Runtime Variant Preset tab uses, and make the restriction count conditions across all properties, not per property.
Live verification on 26.8.0rc1 must show no regression; gating branches are verified by code review and unit tests.
JIRA Issue: FR-3913
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the /admin/deployments page and use report-deployments.md section 0, findings A-D, to trace the affected filter and ordering definitions across the listed tabs. Compare the version flags and condition restrictions with the Runtime Variant Preset tab, then run the relevant unit tests and verify 26.8.0rc1; done means older managers hide unsupported properties, use compatible filters, and restrict combinators correctly without regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100