Migration Plan
Prepare the Rewire
Prepare the Rewire
Open Prepare the rewire from the Migration Plan journey when the plan rewires pipelines. The step sits in Move repositories, or in Run waves when a wave moves repositories and pipelines together.
It reads the dry run in the sandbox: how many rewire decisions that dry run made, which questions are still open, the sandbox's update pull requests, how ready the repositories are, and an estimate for each wave.
Opening the step
You need the Migration Assistant manage permission. The Migration Plan is available on CodeCargo plans that include it. If you do not see it, contact your CodeCargo administrator.
Questions Still Open
The step is here so each wave can carry the dry run's decisions to its destination org. A decision is a fix, a dismissal, or a change you made by hand that still holds, including one an update pull request already delivered in the sandbox.
Questions waiting on a person are listed by Azure DevOps instance, for the plan's repositories under that instance. Open Prepare for rewire on that instance and answer them there. See Prepare Rewire.
You also see how many of the sandbox's update pull requests have merged, and how many are still open. Merge those on Prepare for rewire, not on this step.
How Ready the Repositories Are
Each repository is in one group at most.
- Ready to carry — it has something to rewire, or a decision already made, and nothing is waiting on you.
- Waiting on you — a question is open, or a decision no longer holds and goes back to Review with AI.
- Not ready — pipelines follow it, and its dry-run copy is queued, copying, or failed, so the sandbox cannot scan it yet. Finish that copy on Dry Run.
- Not copied — pipelines follow it, and the dry run never copied it.
A copy the sandbox has not scanned yet has no questions to ask. That is not the same as every question answered.
Each Wave's Estimate
Waves are listed in the order they move. For each one, the estimate splits the dry run's decisions:
- Apply clean — the repository has not changed since its dry run.
- Carry over — the repository has changed since its dry run. The decision is checked against that change and carried into the wave.
- Back to Review with AI — the decision no longer holds in the sandbox. These are counted on their own, not in the other groups.
- Wait for a later wave — a reference to a repository that moves in a later wave, or in no wave. It stays on Azure DevOps until that repository moves, and that repository is rewired again when it does. These are taken out of what applies clean.
- New in production — findings only the destination org's scan can see. None until that scan runs.
- Pipelines to rebind — imported pipelines that follow the wave's repositories with something to rewire.
Rewire without AI is how many decisions are expected to carry into the wave without a review: the ones that apply clean, carry over, or wait for a later wave. Schedule Waves shows that same count on each wave.
A wave's estimate is complete once the sandbox has scanned every repository of that wave it copied, and none of the wave's repositories is still waiting on a copy.
When the Step Is Done
Done when is every rewire question answered. The item shows how many are still open, and it says so when the sandbox has not scanned every copy yet.
The step needs you while a question is open, even if the sandbox has not scanned every copy yet. The badge is how many questions are open.
It is done once the sandbox has scanned every repository the dry run copied and no question is open. Until that scan has finished, and no question is open yet, the step stays upcoming.