DataWorks cross-workspace deployment moves objects—nodes, functions, resources, and components—from one basic-mode workspace to another within the same Alibaba Cloud account and region. Use this workflow to isolate development and production environments across basic-mode workspaces. For background, see Achieve environment isolation in basic mode.
Before proceeding, read Deployment logic to understand the mapping relationships between source and destination workspaces. This ensures tasks run correctly after deployment.
All cross-workspace deployment operations are performed in the source workspace.
Step 1: Create a deployment environment
A deployment environment maps the source workspace's engine instances, resource groups, and dependencies to their counterparts in the destination workspace. After this mapping is configured, the system applies it automatically during each deployment—no manual reconfiguration needed.
Only Workspace Administrator role members can create and configure deployment environments.
Go to Deploy Center
Log on to the DataWorks console. In the top navigation bar, select the desired region. In the left-side navigation pane, choose More > Management Center. On the page that appears, select the desired workspace from the drop-down list and click Go to Management Center.
In the upper-left corner of the page, click the
icon and choose All Products > More > Deploy Center.
Configure the deployment environment
On the Deploy Center page, click Deployment Environment Management in the left-side navigation pane.
Click Create Deployment Environment and fill in the configuration sections below.
Computing resource mappings
Configure mappings between source and destination computing resources. The system deploys nodes, resources, functions, and components to the mapped destination computing resource.
At least one computing resource in the source workspace must be mapped to a computing resource in the destination workspace.
Decide whether to map each source computing resource based on your business requirements.
| Parameter | Description |
|---|---|
| Computing resource in source workspace | All computing resources bound to the source workspace. |
| Computing resource type | The type of the source computing resource. |
| Computing resource in destination workspace | The corresponding computing resource in the destination workspace. To check available computing resources, go to Deployment Environment Management in the destination workspace's Deploy Center and click View workspace environment information. |
| Ignore mapping | When enabled, nodes, resources, functions, and components under that computing resource are excluded from the deployment package. Enable this for engine instances whose objects don't need to be deployed. |
Resource group mappings
Configure mappings between source and destination resource groups. The system uses the mapped destination resource group to run tasks after deployment.
Only mappings between resource groups of the same type are supported.
The Ignore mapping option is not available for default resource groups and shared resource groups.
For Data Integration resource groups, make sure the destination resource group's whitelist and network connectivity settings match those of the source. For details, see Overview of network connectivity solutions.
| Parameter | Description |
|---|---|
| Resource group in source workspace | Resource groups associated with the source workspace. |
| Resource group type | The type of the source resource group. |
| Resource group in destination workspace | The corresponding resource group in the destination workspace. To check details, go to Deployment Environment Management in Deploy Center and click View workspace environment information. |
| Ignore mapping | When enabled, the source resource group is used to deploy tasks. If the source workspace has more resource groups than the destination, enable this for the extra ones. |
Dependency mappings
This section lists the upstream projects for all cross-project dependencies in the source workspace. Map each source project to a destination project so the system rewires dependencies accordingly.
Dependency information is updated with a one-day delay. To see the latest state, click Refresh dependencies.
Configuring a dependency mapping modifies node dependencies. Make sure you can add dependencies in the destination workspace. For troubleshooting, see When I commit Node A, the system reports an error that the output name of the dependent ancestor node does not exist. What do I do?
For MaxCompute engine task types (ODPS SQL and ODPS Spark), the system automatically updates the task code after you configure dependency mappings.
| Parameter | Description |
|---|---|
| Source project name | The upstream projects for cross-project dependencies in the source workspace. |
| Property | The project category. |
| Destination project name | The destination project to map to. |
| Ignore mapping | When enabled, the system keeps the original dependencies in the destination workspace unchanged. |
Data source mappings
Map source data sources to destination data sources. The system uses the destination data sources during task deployment.
| Parameter | Description |
|---|---|
| Source data source name | Data sources in the source workspace. |
| Datasource type | The data source type. |
| Destination name | The destination data source to map to. |
| Ignore mapping | When enabled, the source data source is used directly during deployment. |
Parameter mappings
Sync workflow parameters and scheduling parameters from the source workspace to the destination workspace. Configure parameter values using the visual UI or expressions. For supported formats, see Supported formats for scheduling parameters.
Parameter names must be unique within each deployment task. Do not assign the same values to a parameter in different tasks.
Click Create.
Step 2: Deploy tasks to the source workspace production environment
Deploy the tasks you want to include in the cross-workspace deployment package. After deployment, the system pushes the built packages to the Nodes to deploy list in Deploy Center.
Members with the O&M, Deploy, or Workspace Administrator role can perform this step.
The following instructions use a basic-mode workspace in DataStudio (new version). For DataStudio (legacy version), locate the items to deploy in DataStudio and click the Submit button (
) in the top toolbar.
In DataStudio (new version), locate the nodes, functions, or other items to deploy, and click the Deploy button in the top toolbar.
In the deployment process, click Start deployment to production environment.
Step 3: Create a deployment package
Members with the Development role can create deployment packages. If you have the Workspace Administrator role, the system automatically generates a package after you select objects—click Deploy all to proceed directly.
Log on to the Deploy Center of the source workspace as a member with the Development role. To enter Deploy Center, click the
icon in the upper-left corner, then choose All Products > More > Deploy Center.In the left-side navigation pane, click Nodes to deploy. In the Actions column, click Add to deployment package for each item. The View package to deploy section updates to show the count.
NoteTo add multiple items at once, select them and click Batch add to deployment package at the bottom of the page.
If you click Terminate deployment in the DataStudio (new version) deployment process, the corresponding package no longer appears in this list.
Click View packages to review the objects in the package. Click Remove to exclude any unnecessary items.
NoteObject preview is currently available in DataStudio (old version) only.
On the Deployment package page, click Create deployment package and follow the instructions to finish.
Step 4: Deploy the package
The member performing this step must have the O&M, Deploy, or Workspace Administrator role in both the source and destination workspaces.
Log on to the Deploy Center of the source workspace. To enter Deploy Center, click the
icon in the upper-left corner, then choose All Products > More > Deploy Center.In the left-side navigation pane, click Deployment packages.
In the Actions column of the package, click Deploy and follow the on-screen instructions.
NoteDuring deployment, members with the O&M, Deploy, or Workspace Administrator role can edit the resource group used when the deployed task runs in the destination workspace.
Deployment timing
The time at which a deployment takes effect depends on the node's instance generation mode.
| Instance generation mode | Condition | Takes effect |
|---|---|---|
| Next Day | Deployed before 23:30 | On the instance generated the next day |
| Next Day | Deployed after 23:30 | On the instance generated on the third day |
| Immediately after deployment | Scheduling time is at least 10 minutes after deployment | At the scheduled time as planned |
| Immediately after deployment | Scheduling time is within 10 minutes of deployment, or deployed after 23:30 | On the instance generated on the third day |
Step 5: View the deployment result
After deploying the package, go to the Deployment packages page of the current workspace to view deployment packages.
If the deployment succeeded, go to the Operation Center of the destination workspace to verify the deployed tasks.