Skip to content

Support filtering of dynamic/computational services in catalog rpc client #7532

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
1 task done
bisgaard-itis opened this issue Apr 15, 2025 · 3 comments · Fixed by #7537
Closed
1 task done

Support filtering of dynamic/computational services in catalog rpc client #7532

bisgaard-itis opened this issue Apr 15, 2025 · 3 comments · Fixed by #7537
Assignees
Labels
t:enhancement Improvement or request on an existing feature
Milestone

Comments

@bisgaard-itis
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

User Story

This is required to fulfill the requirements of the api-server

Definition of Done

No response

@bisgaard-itis bisgaard-itis added the t:enhancement Improvement or request on an existing feature label Apr 15, 2025
@pcrespov
Copy link
Member

@bisgaard-itis waht do you want to filter, besides the service type?

@bisgaard-itis
Copy link
Contributor Author

bisgaard-itis commented Apr 16, 2025

@bisgaard-itis waht do you want to filter, besides the service type?

@pcrespov the api server doesn't need any other filtering in the listing. But an endpoint for getting the service ports is also needed:

@bisgaard-itis
Copy link
Contributor Author

@pcrespov note also that it would be useful to have sorting when listing the release history of a service:


That is useful e.g. for getting the latest version. Currently I get the entire history and do the sorting on my side to get the latest version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:enhancement Improvement or request on an existing feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants