I migrated areas/iterations once, how can I stop migrating it on every next migration run?

[EdPerminas]

I migrated areas/iterations once, how can I stop migrating it on every next migration run?

[MrHinsh]

It does not migrate anything that already exists. It just verifies that it exists.

[EdPerminas]

Hi MrHinsh,

"It just varies that it exists." <-- I think my first question was really about this part. For example, you do migrate a big number of areas and iterations. Then on your next run - migration tool goes again through all those areas and iterations, not migrates it, but iterates through that long list. So when you are testing migrations or troubleshooting - the time tool goes through that list adds up.

[MrHinsh]

Agreed, however, the migration will fail if Area or Iteration paths do not exist.

[EdPerminas]

True, but it would be nice to have a switch like we used to have in older versions "NodeStructuresMigrationConfig" - with that once you know you migrated all paths, and those are not changing - then next attempt you can leave that switch off.

[MrHinsh]

@EdPerminas I have created a PR that removed the need to create any of the nodes up front!

#1733

They are all created at validation time.

[EdPerminas]

That's awesome!! Thanks MrHinsh!

[MrHinsh]

I set the default variables of ShouldCreateNodesUpFront to true, but if we can validate that it works great it could become the only way.

[MrHinsh]

It still checks with a single GetNodeFromPath for each of the full list of distinct nodes generated, but that should be fast.

[EdPerminas]

I just ran the migration with the latest updates, and can confirm it works as expected! Great update - thank you!!