Project

Profile

Help

Issue #8137

Provide a way to map a single Pulp 2 content onto many Pulp 3 contents

Added by quba42 about 1 month ago. Updated 13 days ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
-
Sprint/Milestone:
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

This is needed for structured Debian migrations, but since it could be potentially used by other plugins, I think it makes sense to add it as a separate PR with a separate changelog entry and migration.


Related issues

Blocks Migration Plugin - Issue #7865: Add ability to migrate Debian release and component units for structured publicationCLOSED - CURRENTRELEASE<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

Associated revisions

Revision cfc8ec15 View on GitHub
Added by ttereshc 27 days ago

Add the pulp2_subid field to the Pulp2Content model

fixes #8137 https://pulp.plan.io/issues/8137

The intended use case is to provide one to many mapping from Pulp 2 to Pulp 3 content. This is achieved by creating multiple Pulp2Content entries that all share a single pulp2_id, and differ only via the pulp2_subid.

This is needed for structured Debian migrations: https://pulp.plan.io/issues/7865

The extra Pulp2Content subrecords are added by the relevant pre_migrate_content_detail method. The reason is that it is only known what subrecords are needed once the content is actually inspected by this method.

Revision cfc8ec15 View on GitHub
Added by ttereshc 27 days ago

Add the pulp2_subid field to the Pulp2Content model

fixes #8137 https://pulp.plan.io/issues/8137

The intended use case is to provide one to many mapping from Pulp 2 to Pulp 3 content. This is achieved by creating multiple Pulp2Content entries that all share a single pulp2_id, and differ only via the pulp2_subid.

This is needed for structured Debian migrations: https://pulp.plan.io/issues/7865

The extra Pulp2Content subrecords are added by the relevant pre_migrate_content_detail method. The reason is that it is only known what subrecords are needed once the content is actually inspected by this method.

Revision cfc8ec15 View on GitHub
Added by ttereshc 27 days ago

Add the pulp2_subid field to the Pulp2Content model

fixes #8137 https://pulp.plan.io/issues/8137

The intended use case is to provide one to many mapping from Pulp 2 to Pulp 3 content. This is achieved by creating multiple Pulp2Content entries that all share a single pulp2_id, and differ only via the pulp2_subid.

This is needed for structured Debian migrations: https://pulp.plan.io/issues/7865

The extra Pulp2Content subrecords are added by the relevant pre_migrate_content_detail method. The reason is that it is only known what subrecords are needed once the content is actually inspected by this method.

History

#1 Updated by quba42 about 1 month ago

  • Blocks Issue #7865: Add ability to migrate Debian release and component units for structured publication added

#2 Updated by ttereshc 27 days ago

  • Status changed from NEW to MODIFIED

#3 Updated by ttereshc 13 days ago

  • Sprint/Milestone set to 0.8.0

#4 Updated by pulpbot 13 days ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF