Story #5076
As a user, I have 'latest' as a boolean query parameter for CollectionVersion
100%
Description
In addition to the fields being searchable, a 'latest' parameter should be available that defaults to False. If True, it will only return the latest version when multiple versions of one Collection name are returned in the results.
Related issues
Associated revisions
Revision d2380d87
View on GitHub
Fix missing dep on 'packaging' dep in setup.py
Add 'packaging' dep required by changes introduced in ca36e63b033a1371ee02797cd7a854093330b5b0
History
#1
Updated by daviddavis about 2 years ago
I'm wondering how we determine latest? There are cases like 0.10.0 vs 0.2.0 and weird versions like "0.2.0-beta0.2".
#2
Updated by bmbouter about 2 years ago
We could filter them in memory using the python tools and then rebuild the queryset for the user by it's ids.
#3
Updated by bmbouter about 2 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
- Sprint set to Sprint 55
Taking as assigned to unblock Galaxy dev.
#4
Updated by bmbouter about 2 years ago
- Status changed from ASSIGNED to POST
PR available at: https://github.com/pulp/pulp_ansible/pull/128
#5
Updated by bmbouter about 2 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp_ansible|ca36e63b033a1371ee02797cd7a854093330b5b0.
#6
Updated by kersom about 2 years ago
- Related to Test #5269: Test - As a user, I have 'latest' as a boolean query parameter for CollectionVersion added
#7
Updated by bmbouter about 1 year ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Please register to edit this issue
.
Add 'latest' boolean for Collection filtering
When 'latest' is True, only include a Collection if it is the newest version of <namespace, name>.
https://pulp.plan.io/issues/5076 closes #5076