Story #3630
As a user I can filter python content by repository version
Start date:
Due date:
% Done:
0%
Platform Release:
Blocks Release:
Target Release - Python:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Easy Fix
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
History
#1
Updated by amacdona@redhat.com over 1 year ago
- Tracker changed from Issue to Story
- Project changed from Pulp to Python Support
- % Done set to 0
- Tags Pulp 3 added
#2
Updated by bizhang over 1 year ago
- Tags Easy Fix added
#3
Updated by bizhang over 1 year ago
- Sprint/Milestone set to 3.0 GA
#4
Updated by amacdona@redhat.com over 1 year ago
- Status changed from NEW to CLOSED - NOTABUG
Closing for now. I've head it is challenging to filter based on repository version, but this use case appears to be covered.
/repositories/<repo id>/versions/<number/content/ Should cover most use cases. It is possible that users will need more specific serialization; for that, I think doing this on top of the versions endpoint would make more sense. Something like:
/repositories/<repo id>/versions/<number/content/type/python/
Please register to edit this issue
.