Project

Profile

Help

Story #5517

[EPIC] Automation Hub Release Blockers

Added by bmbouter about 2 months ago. Updated 14 days ago.

Status:
NEW
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

25%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
No
Sprint Candidate:
No
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:

Description

This epic captures the pulp_ansible changes required for the initial Automation Hub release, which pulp_ansible is the storage backend for.


Subtasks

Story #5238: As a user, the Galaxy V3 APIs has working Python bindingsNEW

Actions
Story #5519: As an API user, I have an 'exclude' field that is the opposite of the 'fields' parameterMODIFIEDdaviddavis

Actions
Story #5520: As a user using a non-Galaxy API, I have a collection viewsetMODIFIEDdaviddavis

Actions
Story #5522: As a user, I can filter ImportCollection reposnse messages by date to receive limit the set of messages returnedMODIFIEDdaviddavis

Actions
Issue #5571: Add the ability to filter collection versions by tagMODIFIEDdaviddavisActions
Issue #5572: pulp_ansible/app/tasks/collections.py:import_collections() throws FieldErrorMODIFIEDdaviddavisActions
Issue #5577: As a user, I can update a collection to deprecate itMODIFIEDfabricio.aguiarActions
Issue #5579: Add the ability to set a certification status for a collection versionMODIFIEDfabricio.aguiarActions
Issue #5621: Add sort parameters to Collection Version ListMODIFIEDdaviddavisActions
Issue #5645: Need to return deprecated status in collection versions endpointMODIFIEDdaviddavisActions
Issue #5670: Add certiication param to collection version endpointMODIFIEDActions
Pulp - Issue #5673: Resource reservations are not cleaned up if worker is killedNEWActions

Please register to edit this issue

Also available in: Atom PDF