Task #6516
closed
Automatically produce a "complex" migration plan from "simple" migration plans
Status:
CLOSED - CURRENTRELEASE
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.
- Tracker changed from Issue to Task
- % Done set to 0
- Sprint/Milestone set to 0.2.0
- Priority changed from Normal to Low
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
- Priority changed from Low to Normal
- Sprint set to Sprint 78
- Sprint changed from Sprint 78 to Sprint 79
- Sprint/Milestone deleted (
0.2.0)
- Sprint changed from Sprint 79 to Sprint 80
- Sprint changed from Sprint 80 to Sprint 81
- Sprint changed from Sprint 81 to Sprint 82
- Status changed from NEW to ASSIGNED
- Assignee set to dalley
- Sprint changed from Sprint 82 to Sprint 83
- Sprint changed from Sprint 83 to Sprint 84
- Sprint changed from Sprint 84 to Sprint 85
- Sprint changed from Sprint 85 to Sprint 86
- Sprint changed from Sprint 86 to Sprint 87
- Sprint changed from Sprint 87 to Sprint 88
- Status changed from ASSIGNED to POST
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
- Sprint/Milestone set to 0.7.0
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Also available in: Atom
PDF
.
Automatically produce a "complex" migration plan from simple ones
closes: #6516 https://pulp.plan.io/issues/6516