Welcome to the Datanyx Community!

Get Help, Learn Best Practices, Network With Other Datanyx Users
Is it possible for ...
 
Notifications
Clear all

Is it possible for users to import migration plans from alternate accounts?

3 Posts
2 Users
0 Likes
199 Views
Abhishek
(@abhishek)
Eminent Member
Joined: 11 months ago
Posts: 11
Topic starter  

Furthermore, does this feature also grant users the capability to track the status of their import processes?


   
Quote
Topic Tags
ankit.pradhan
(@ankit-pradhan)
Eminent Member
Joined: 2 years ago
Posts: 20
 

Step 1: On the Main Navigation Bar Click the Migration icon. (Refer to the image below).

1693309476-mignav.png

Step 2: In Migration, we have two options: 

Migration Plan: Migration plans are accessible to all admin users that belong to the same environment. It can be downloaded as a Zip file if need be. A new plan can be created in addition to the comprehensive list of plans that have been previously created by the users within the organization. 

Migration: Users can import any migration plan from other accounts/ environment or local migration folder by clicking on the import icon at the bottom right of screen. The user is also able to check the status of their import. 

Step 3: Click on the import migration icon. The Migration pop-up appears. (Refer to the image below). 

1693309606-migrationpopup.png

Step 4:  The user can select the following:

Project: The desired project under which the import of the migration plan is to take place.

Configuration Template: The user can select from the already existing configuration templates or can add a new template. The user can also edit the existing template.

A configuration template pop-up appears wherein the user can enter the title of the template, select the migration source environment, file type, enter the Source Id (Source id from the environment from where the file is to be imported from) and Local Id (Source id of the target environment to which the migration is to be performed).

If the type is Datasource Id, then the source Id (Datasource Id) will be the environment from where the migration has been done, and the Local Id (Destination Id) will be the environment to which the migration is to be performed. (Refer to the image below).

1693309673-config-temp-datasource.png
If the type is Connector Id, then the source Id will be the environment from where the migration has been done, and the Local Id (Destination Id) will be the environment to which the migration is to be performed. (Refer to the image below) 
1693309701-config-temp-connector.png
The user can configure multiple artifacts. The user can toggle between the Input box where they can enter manually. They can also select from the dropdown by clicking on the toggle button. (Refer to the image below). 
1693309750-configuration-temp.png

   
ReplyQuote
ankit.pradhan
(@ankit-pradhan)
Eminent Member
Joined: 2 years ago
Posts: 20
 

Once the desired configurations have been done, click on the apply button. 

Migration Plan: The user can choose the environment and the required migration plan. Alternatively, the user can click on the choose file button to import the previously downloaded migration plan. 

The user can enter the desired notes for the plan (optional). 

Step 5: Click on the Start Migration button to begin the process of migration. The migrated artifact will be available in the list of migrations upon successful migration. (Refer to the image below). 

1693309858-migration-import-list.png
Note: The users under the same organization and same environment can view the logs of migrations plans executed by other users as well.  

   
ReplyQuote
Share: