Dear DataWorks users:
To provide better cross-workspace deployment capabilities, Alibaba Cloud plans to integrate the cross-workspace cloning feature into Deploy Center. This way, you can use Deploy Center to perform related cross-workspace deployment operations. Before the cross-workspace cloning feature is discontinued, the system migrates historical data for cross-workspace cloning to Deploy Center based on the default migration logic. For information about the discontinuation time, see Notice on the discontinuation of DataWorks cross-workspace cloning.
Default migration logic
Default environment migration logic
DataWorks automatically generates a deployment environment for a source workspace and a destination workspace based on the compute engine mappings that are configured in the original cross-workspace cloning environment. The following content describes the policies for generating a default deployment environment. You can directly use the default deployment environment in Deploy Center or modify the environment based on your business requirements.
If a deployment environment has been configured for a source workspace and a destination workspace, DataWorks does not repeatedly generate a deployment environment to overwrite the existing environment.
If the same source workspace is mapped to multiple destination workspaces, multiple deployment environments may be generated.
If historical clone packages that are used to migrate tasks to a specific destination workspace exist in the source workspace, a deployment environment is generated for the destination workspace.
If no historical clone packages that are used to migrate tasks to a specific destination workspace exist in the source workspace, no deployment environment is generated for the destination workspace.
The following table describes the generation logic for a deployment environment in Deploy Center.
Parameter | Description |
Environment Name | This parameter is configured in the |
Deployment Type | Cross-workspace Deployment is selected. |
Destination Workspace | The value of the Target Workspace parameter on the Create Package page in Cross-project cloning is used. |
Deployment Object Owner | Default is used. |
Compute Engine Instance Mappings |
|
Resource Group Mappings | By default, mappings are configured only for shared resource groups for scheduling and shared resource groups for DataService Studio. Ignore Mapping is turned on for other types of resource groups. |
Dependency Mappings |
Note The compute engine type that is specified by the Property parameter in the Dependency Mappings section can only be MaxCompute. The E-MapReduce (EMR) and Hologres compute engine types are not supported. |
Data Source Mappings |
|
Parameter Mappings | By default, no parameter is configured. |
Remarks | This parameter is configured in the following format to describe the deployment environment that is automatically generated based on the default migration logic: |
Default clone package migration logic
DataWorks migrates all historical clone packages on the Release Package page in Cross-project cloning to the Deployment Packages page in Deploy Center.
The following table describes the default migration mapping policy.
Item to map | Clone package | Deployment package |
Package ID | Clone package ID | Regenerate a deployment package ID. |
Package name | Clone package name | Reuse the clone package name. |
Deployment environment | N/A. | Generate an environment name in the |
Deployment type | N/A. | Select Cross-workspace Deployment. |
Applicant | Applicant | Reuse the clone package applicant. |
Application time | Application time | Reuse the application time of the clone package. |
User who deploys a package | User who deploys a package | Reuse the user who deploys the clone package. |
Deployment time | Cloning time | Reuse the cloning time. |
Progress | Progress | N/A. |
Status | Clone status | Use the deployment status. |