Project

Profile

Help

Task #6178

closed

Story #6146: [Epic] As a user, I can migrate RPM plugin content and repositories

Add ability to migrate Errata

Added by ttereshc about 4 years ago. Updated over 3 years ago.

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

100%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 71
Quarter:

Description

All the metadata is parsed in pulp 2 , so everyting can be take from the db.

The main part of this task is to figure out how to separate errata package lists so one erratum in pulp 2 will end up into N advisories in pulp 3. And then which advisory to assign to which repo.

Proposal

Extend Pulp2 model to track information about pulp2 repositories an erratum belongs to. Process errata in a similar way it happens in Pulp 2 during publish. In the viewset for this model provide a repo version this erratum was migrated to.

Also available in: Atom PDF