Migrating a connector from previous versions using the Data Integration REST API

Migrating a connector from previous versions using the Data Integration REST API

View the updated assets

View the updated assets

If the assets that reference the old connection are in a single or multiple folders in Cloud Data Integration, the migrate API creates a corresponding new folder or folders for the updated assets when the migration is complete.
The migration call returns the migrate job ID, migrate job name, and the source and target paths in Cloud Data Integration. The source path contains the assets referenced with the old connection, while the target path contains the assets updated with the current connection version. The target folder name uses the same name as the source, but has the migration job ID appended to the name.
For example, if the source folder with the referenced assets is
AA_OldArtifacts
, the updated assets are copied to a target folder
AA_OldArtifacts_Migration_1ABCo
, with the migration job ID is sufficed to the target folder.
If the assets that reference the source connection are in multiple folders, the migrate API creates corresponding new folders to include the updated assets.
For example, if the folder names that contain the assets is
AA_OldArtifacts1
and
AA_OldArtifacts2
, these assets are copied to corresponding new folders
AA_OldArtifacts_Migration_1ABCo
and
AA_OldArtifacts_Migration_2ABCo
.
If the assets in the source path are at the project level and not within a folder in a project, the target path folder name takes the source project name.
When you click the migrated asset in the folders, the names of these assets, for example, the mapping name, remains the same as in the old connection, but the old connection in the assets is replaced by the current version.

0 COMMENTS

We’d like to hear from you!