meshery
meshery copied to clipboard
[Server] Registry Enhancements
Current Behavior
- [x] 1. Update the API endpoints to retrieve only the count of components and relationships for each model, rather than returning all data.
- [x] Fix the bug where both the component count and relationship count are showing zero,
- [ ] 2. Remove duplicated data that's currently being returned from the endpoint.
- [ ] 3. Add query parameters for the
meshmodel/models
,meshmodels/components
,meshmodels/relationships
, andmeshmodels/registrants
endpoints.- [ ] Add a query parameter like
duplication-data=true
to fetch information about duplicated entities. This will allow the UI to filter and highlight duplicate entities.
- [ ] Add a query parameter like
- [ ] 4. Remove the aggregation of models in the registrants tab once the data duplication is resolved from the endpoint.
- [x] 5. Add ID-based
GET
endpoints for all Registry requests to simplify the selection of entities. #12361- Currently, selection is based on a combination of name and version.
- Possibly related PR: https://github.com/meshery/meshkit/pull/538.
- [ ] 6. [UI] Ensure the
meshmodel
details component respects the current level of navigation in the tree structure. (depends on 1st issue of this list)- [ ] At the top level of a model, display the aggregate count of components across all versions of that model.
Screenshots/Logs
Environment
- Host OS: Mac Linux Windows
- Platform: Docker or Kubernetes
- Meshery Server Version: stable-v
- Meshery Client Version: stable-v
To Reproduce
Contributor Guides and Handbook
- π Meshery Build & Release Strategy
- π Instructions for contributing to documentation
- π¨ Wireframes and designs for Meshery UI in Figma (open invite)
- ππΎππΌ Questions: Discussion Forum and Community Slack