Migration Plugin

Motivation¶

With improvements introduced earlier, the migration re-runs are much faster now, at he same time when no changes are made and everything is migrated, it can take a significant amount of time to re-run a migration which is supposed to be no-op. It is mostly noticeable on the large systems with many repositories in Pulp 2.

Suggested solution¶

• compare the previous and current plans
• allow pre-migration to run to check for any changes in pulp2 (not sure if there any shortcuts available there)
• if the plan is the same and everything has been migrated, finish the task and do not proceed with content migration or repo version creation.