Migrating DataWorks cross-workspace cloning to Deploy Center - DataWorks

Dear DataWorks users,

The Cross-workspace cloning feature is moving to Deploy Center to enhance cross-workspace deployments. You can now manage these deployments in Deploy Center. Before Cross-workspace cloning is retired, DataWorks automatically migrates your historical data from Cross-workspace cloning to Deploy Center based on the default migration logic. For the detailed timeline, see the DataWorks Cross-workspace Cloning Deprecation Announcement.

Default migration logic

Default deployment environment migration logic

DataWorks automatically creates a deployment environment between a source and destination workspace, using your existing compute engine mappings in Cross-workspace cloning. The default generation strategy for these deployment environments is as follows. You can use the generated environment directly in Deploy Center or modify it as needed.

Important

DataWorks will not create or overwrite a deployment environment if one already exists for the same source and destination workspaces.
If a source workspace maps to multiple destination workspaces, multiple deployment environments may be generated.
- A deployment environment is generated if the source workspace has historical clone packages that were deployed to a destination workspace.
- If a source workspace has no historical clone packages, no deployment environment is generated.

The generation logic for a deployment environment is detailed below:

Parameter	Description
Environment Name	`Cross-workspace cloning migration_${SourceWorkspaceName}_to_${DestinationWorkspaceName}`.
Deployment Type	Cross-workspace Deployment.
Destination Workspace	The value from the original destination workspace parameter in Cross-workspace cloning.
Deployment Object Owner	Default.
Compute Engine Instance Mappings	Reuses any mappings from the original compute engine mappings settings in Cross-workspace cloning. If no mappings were configured, this setting is ignored.
Resource Group Mappings	Only `shared resource groups for scheduling` and public resource groups for DataService are mapped by default. Mappings for other resource groups are ignored.
Dependency Mappings	If the project type is `DataWorks`, the system uses the mappings defined in the target deployment environment. If the project type is `MaxCompute`, mappings are partially resolved by using the engine mapping configuration. If mappings for this project were configured in the original compute engine mappings settings, the deployment environment reuses them. All other mappings are ignored by default. Note For dependency mappings, the only supported engine type for projects is currently `MaxCompute`. Engines such as `E-MapReduce (EMR)` and `Hologres` are not yet supported.
Data Source Mappings	If mappings were configured in the original compute engine mappings settings, those mappings are reused. If no mappings were configured, this setting is ignored.
Parameter Mappings	Empty by default.
Remarks	This deployment environment was automatically migrated from Cross-workspace cloning. `Source: ${source_workspace_display_name} (${source_workspace_name}) to Destination: ${destination_workspace_display_name} (${destination_workspace_name})`.

Default clone package migration logic

DataWorks migrates all historical clone packages from the Cross-workspace cloning clone package list to the Deploy Center > Deployment Packages.

The default migration mapping strategy is as follows:

Parameter	Clone Package	Deployment Package
Package ID	Clone package ID	A new deployment package ID is generated.
Package name	Clone package name	Reuses the clone package name.
Deployment environment	Not applicable	`Cross-workspace cloning migration_${SourceWorkspaceName}_to_${DestinationWorkspaceName}`.
Deployment Type	Not applicable	Cross-workspace Deployment.
Applicant	Applicant	Reuses the applicant from the clone package.
Application time	Application time	Reuses the application time from the clone package.
Published By	Published By	Reuses the publisher from the clone package.
Deployment time	Cloning time	Reuses the cloning time.
Progress	Progress	Not applicable.
Status	Clone status	Deployment status.

Note

After migration to Deploy Center, you can manage the migrated packages, such as deploying or canceling deployments, according to the rules of Deploy Center.