For customers who have job dependencies, where the workflow references a job by name, after running the migration script, the new job name will be job name + ::: + job id.
Customers can update their job names after the fact by removing this id, but it would be good to have an option for customers who are confident they do not have duplicate job names to allow the migrated name to be equal to the old job name.
For customers who have job dependencies, where the workflow references a job by name, after running the migration script, the new job name will be job name + ::: + job id.
https://github.com/databrickslabs/migrate/blob/b086c48cd89138356a63d4a30ee0c8dab277b36f/dbclient/JobsClient.py#L62-L80
Customers can update their job names after the fact by removing this id, but it would be good to have an option for customers who are confident they do not have duplicate job names to allow the migrated name to be equal to the old job name.