Story #6146: [Epic] As a user, I can migrate RPM plugin content and repositories
Add ability to migrate Errata
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.
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.
- Status changed from ASSIGNED to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|f4b4e47ab0954144dad480132cee31aa68e78dc5.
Please register to edit this issue