DataWorks跨项目克隆一键迁移至发布中心 - DataWorks

Dear DataWorks user,

The cross-project cloning feature is being integrated into Deployment Center. You can continue performing cross-workspace deployments in Deployment Center. Before cross-project cloning is discontinued, the platform will migrate your historical cross-project cloning data to Deployment Center based on the default migration logic. For the specific timeline, see Discontinuation of DataWorks cross-workspace cloning.

Default migration logic

Default migration logic for environments

DataWorks automatically generates a deployment environment from the source workspace to the target workspace based on your existing compute engine mappings from cross-project cloning. You can use the generated environment directly or modify it in Deployment Center.

Important

If a deployment environment already exists for the same source and target workspace pair, DataWorks does not create a new one or overwrite it.
If a source workspace has multiple target workspaces, multiple deployment environments may be generated.
- If historical clone packages from the source workspace to a target workspace exist, a deployment environment is generated.
- If no historical clone packages exist for the source workspace, no deployment environment is generated.

The generation logic is as follows:

Configuration item	Generation logic
Environment name	`CrossProjectCloneMigration_${SourceWorkspaceName}PublishTo${TargetWorkspaceName}`.
Deployment type	Cross-workspace Deployment.
Target workspace	The original Clone to Target Workspace value from cross-project cloning.
Object owner for deployment	Default.
Compute engine instance mapping	If a mapping was configured in Set Compute Engine Mapping for the original cross-project clone, that mapping is reused. If no mapping was configured in the original cross-project clone, the mapping is ignored.
Resource group mapping	Only the shared resource group for scheduling and the shared resource group for Data Service are mapped by default. Other resource groups are ignored.
Dependency mapping	If the project type is DataWorks, the target environment mapping of the deployment package is used. If the project type is MaxCompute, partial resolution is performed using the engine mapping. If a mapping was configured in Set Compute Engine Mapping for this project in the original cross-project clone, that mapping is reused. Otherwise, the mapping is ignored by default. Note For dependency mapping, the engine type in the project property currently supports only MaxCompute. E-MapReduce and Hologres are not yet supported.
Data source mapping	If a mapping was configured in Set Compute Engine Mapping for the original cross-project clone, that mapping is reused. If no mapping was configured in the original cross-project clone, the mapping is ignored.
Parameter mapping	Empty by default.
Remarks	A deployment environment generated by default migration from Data Studio cross-project cloning: `SourceProject:${SourceWorkspaceDisplayName}(${SourceWorkspaceName})ToTargetProject:${TargetWorkspaceDisplayName}(${TargetWorkspaceName})`.

Default migration logic for clone packages

DataWorks migrates all clone packages from the historical Clone Package List of Cross-project Cloning to Deployment Center > Deployment Packages.

The default migration mapping policy is as follows:

Mapping item	Clone package	Deployment package
Package ID	Clone package ID	A new deployment package ID is generated.
Package name	Clone package name	The clone package name is reused.
Deployment environment	Not applicable	`CrossProjectCloneMigration_${SourceWorkspaceName}PublishTo${TargetWorkspaceName}`.
Deployment type	Not applicable	Cross-workspace deployment.
Requester	Requester	The requester of the clone package is reused.
Request time	Request time	The request time of the clone package is reused.
Deployer	Deployer	The deployer of the clone package is reused.
Deployment time	Clone time	The clone time is reused.
Progress	Progress	Not applicable.
Status	Clone status	Deployment status.

Note

After clone package data is migrated to Deployment Center, you can deploy or undeploy it using Deployment Center rules.