Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Query container images based on package versions and indexes #2619

Open
mayaCostantini opened this issue Apr 4, 2022 · 5 comments
Open

Query container images based on package versions and indexes #2619

mayaCostantini opened this issue Apr 4, 2022 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.

Comments

@mayaCostantini
Copy link
Contributor

Problem statement

We could extend container image queries by adding package versions and indexes filters to allow users to look for containerized environments based on more precise criteria.

Proposal description

Modify the query for container images with filters for package versions and indexes and propagate those changes to the User API and Thoth Search UI.

Alternatives

Keep the current container images query implementation with only package names.

Additional context

Related: thoth-station/user-api#1739
@mayaCostantini mayaCostantini added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 4, 2022
@mayaCostantini
Copy link
Contributor Author

/sig stack-guidance

@sesheta sesheta added the sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance. label Apr 4, 2022
@goern
Copy link
Member

goern commented Jun 23, 2022

what is the priority of this?

@mayaCostantini
Copy link
Contributor Author

/priority important-longterm

@sesheta sesheta added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Jul 3, 2022
@sesheta
Copy link
Member

sesheta commented Oct 1, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 1, 2022
@harshad16
Copy link
Member

/remove-lifecycle stale
/lifecycle frozen

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. sig/stack-guidance Categorizes an issue or PR as relevant to SIG Stack Guidance.
Projects
Planning Board
Status: 🆕 New
Milestone
No milestone
Development

No branches or pull requests
4 participants
@goern @harshad16 @sesheta @mayaCostantini