Task #6516
closedAutomatically produce a "complex" migration plan from "simple" migration plans
100%
Description
The migration plugin code should only handle complex migration plans under the hood, as they are simpler to schedule work for. When a user creates a "simple" migration plan for a plugin, it should be transparently pre-processed such that the same codepaths are used as for the complex migration plans.
Updated by ttereshc over 4 years ago
- Tracker changed from Issue to Task
- % Done set to 0
Updated by ipanova@redhat.com over 4 years ago
This will be a non user facing change. Simple migration plan will be translated into complex migration plan and used during the migration but to the user will still be returned simple plan
Updated by ttereshc over 4 years ago
- Priority changed from Low to Normal
- Sprint set to Sprint 78
Updated by dalley about 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
Updated by dalley almost 4 years ago
- Status changed from ASSIGNED to POST
Added by dalley almost 4 years ago
Added by dalley almost 4 years ago
Revision e243fcc2 | View on GitHub
Automatically produce a "complex" migration plan from simple ones
Added by dalley almost 4 years ago
Revision e243fcc2 | View on GitHub
Automatically produce a "complex" migration plan from simple ones
Updated by dalley almost 4 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp:pulp-2to3-migration|e243fcc21b16fcc4589027f8339bbef472bedb85.
Updated by pulpbot almost 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Automatically produce a "complex" migration plan from simple ones
closes: #6516 https://pulp.plan.io/issues/6516