Actions
Story #5231
closed
Story #3821: As a user, I can migrate from Pulp 2 to Pulp 3
As a user, I can query Pulp 2->Pulp 3 mapping for migrated content
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 57
Quarter:
Description
Create a new endpoint to query the Pulp2-Pulp3 mapping for content.
Required info (agreed with Katello):
pulp2_content_id (e.g. '6168ebd6-0ffb-48b9-8ebb-e5f1775d1e0c')
pulp2_content_type (e.g. 'iso')
pulp3_content_href (e.g. '/pulp/api/v3/content/file/files/6d382246-4838-4350-a9ea-33e5de25ca11/d3cf852f-d7ff-40e0-b95b-5e35f74aacf8')
pulp3_content_type (e.g. 'file')
pulp3_created (time of creation in Pulp 3) (e.g."2019-07-22T10:06:48.881666Z")
This information can be found on Pulp2Content model.
Add ability to filter by content types and creation time.
Ask Katello if any other filters are needed,
Actions
.
Problem: Pulp2Content can't be queried using REST API
Solution: add REST API for Pulp2Content
This patch adds a ViewSet, a Filter, and a Serializer for Pulp2Content model. This enables REST API users to retrieve a list of Pulp2Content as well as individual units. Lots of filters for filtering are also available.
fixes: #5231 https://pulp.plan.io/issues/5231