Publish objects from an imported deployment package - Dataphin - Alibaba Cloud - Dataphin

Prerequisites

You have imported the deployment package from the source environment into the destination environment. For more information, see Import a deployment package.

Considerations

To protect production data and prevent incidents from broken object references, the system enters a maintenance state during deployment, which prevents issues caused by concurrent operations. A system administrator or super administrator must manually exit this state before other users can access the system.
If an object in the deployment package has the same version as its counterpart in the current environment, deployment is not required. However, the object is still included in the total object count on the overview page.

Note

Dataphin V3.11 supports exporting historical objects created before Dataphin V3.9 and deploying them to other tenants.

Permissions

Only users with the cross-tenant deployment user role can access and manage objects awaiting deployment.

Deployment package overview access

Log on to Dataphin as a cross-tenant deployment user.
On the Dataphin homepage, in the top navigation bar, choose Management Center > Cross-tenant Deployment.
In the left-side navigation pane, choose Cross-tenant Deployment > Import Deployment Package.
In the Actions column for the target deployment package, click the Deploy icon.

Deployment package overview

The Deployment Package Overview page shows a comparison between the imported deployment package and the current environment, the number of changed objects, and a summary of object deployment statuses. The statuses include To Be Deployed, Queued, Deploying, Deployed Successfully, Deployment Failed, and Succeeded with Risks. On this page, you can manage and deploy objects of different types and with different statuses, which are grouped by functional module: Global, Data Architecture, Development, Tag Architecture, Tag, Data Standard, Data Quality, and Data Security.

Note

The Deployment Package Overview page displays only objects that require deployment. Objects in the deployment package that have the same version as those in the current environment are ignored.

Section

Description

①Action area

You can perform the following actions: Modify Deployment Settings, Re-parse, One-click Deployment, and Refresh.

Modify Deployment Settings: Deployment settings are required to deploy objects in a deployment package. If the settings change, you can click Modify Deployment Settings to quickly update them on the deployment package import settings page.
Re-parse: The system compares the objects in the deployment package with those in the current environment. If an object's version matches, it does not require deployment. If the versions differ, or if the object's change type is Add or Delete, its status is set to To Be Deployed. An object's status may change after re-parsing if the version of its counterpart in the current environment has been modified.
One-click Deployment: The system deploys the objects awaiting deployment in sequence. You can Terminate Deployment during the process.

During one-click deployment, the system deploys objects without strong dependencies in the order they appear on the page. The deployment process is not interrupted if an object in an earlier stage fails to deploy. For the deployment order, see Recommended deployment order.

When you terminate a deployment, the system only stops the functional modules that are not in the Deploying state. You cannot terminate a module that is currently being deployed or roll back modules that have been completed. If you restart the deployment, the system retries deploying the failed and pending objects.
Note
- You must complete the deployment settings before using one-click deployment. Otherwise, the action is unavailable.
- When using one-click deployment, if the package includes a compute engine, the system deploys it using the configuration from the source environment. If it includes a data source, the system applies replacement rules before deployment. The deployment will fail if required object information (such as connection details, authentication information, or files) is missing.
- If the compute engine information is identical in the source and destination tenants, there is a risk of data loss. We recommend that you first deploy the compute engine and data source, and then perform the one-click deployment.
Refresh: Refreshes the list of objects awaiting deployment.

②Deployment object list

The system groups objects by functional module (Global, Data Architecture, Development, Tag Architecture, Tag, Data Standard, Data Quality, and Data Security), displaying the card status and object information for each module.

Status: An icon on each module's card indicates its overall deployment status.
- : The module is awaiting deployment.
- : The module contains objects that failed to deploy.
- : The module is being deployed.
- : All objects in the module have been deployed successfully.
Object information: Displays the Total number of objects (excluding objects that do not require deployment) and the count for each deployment status: To Be Deployed, Queued, Deploying, Deployed Successfully, Succeeded with Risks, and Deployment Failed. The Queued status indicates that the object is in the deployment queue and waiting to be deployed.
View Details: If a functional module contains changed objects, you can click the icon on its card to view details.

Change types

When you import a deployment package, the system automatically identifies and marks objects with one of the following change types based on a set of rules: Add, Update, or Delete.

Add: An object is marked as Add if it exists in the deployment package but does not exist in the destination environment. Deploying this object adds it to the destination environment.
Update: An object is marked as Update if it exists in the destination environment but has a different version in the deployment package. Deploying this object overwrites the existing version.
Delete: An object is marked as Delete if it exists in the destination environment but is not included in the deployment package. Deployment deletes the object from the destination environment.

Permissions for deploying objects

After importing a deployment package, a cross-tenant deployment user must have specific deployment permissions for each object type to deploy them. The table below describes the required permissions.

Deployment object	Subtype	Permission description
Global	Statistical Period Global Variable Public Calendar Object Property Identification Feature	The user must be a cross-tenant deployment user with super administrator or system administrator permissions.
	Data Block	The user must be a cross-tenant deployment user with super administrator or system administrator permissions, or be the Data Block Architect for the corresponding data block.
	Compute Engine	The user must be a cross-tenant deployment user and have super administrator or system administrator permissions, or be a Data Block Architect responsible for the data block to which the compute engine is bound, or be the compute engine owner.
	Project	The user must be a cross-tenant deployment user and have super administrator or system administrator permissions, or be a Data Block Architect responsible for the data block to which the compute engine is bound, or be the project owner.
	Data Source	The user must be a cross-tenant deployment user and have Data Source Administrator or Data Source Owner role permissions.
Data Architecture	Business Object Business Activity Subject Domain	The user must be a cross-tenant deployment user and have super administrator or system administrator permissions, or be a Data Block Architect responsible for the corresponding data block.
Development Objects	Integration Task Model Development Metric Development File Management Computing Task Offline Physical Table	The user must be a cross-tenant deployment user with super administrator permissions. Alternatively, a cross-tenant deployment user must also be a member of the object's project and have commit (for Dev or Basic projects) or deployment (for Prod projects) permissions.
Tag Architecture Tag	Tag Entity Tag Entity ID Workbench Object	The user must be a cross-tenant deployment user with super administrator or system administrator permissions.
Data Standard	Code Table Directory Standard Set Directory Common Standard Property Standard Template Standard Set Data Standard Standard Mapping Rule Mapping Relation (Asset Granularity) Code Table Word Root	The user must be a cross-tenant deployment user with super administrator or system administrator permissions.
Data Quality	Quality Rule Template Quality Rule (Object Granularity)	The user must be a cross-tenant deployment user with super administrator or system administrator permissions.
Data Security	Data Classification Data Sensitivity Level Identification Result (Table Granularity) Key	The user must be a cross-tenant deployment user with super administrator or system administrator permissions.

Recommended deployment order

Due to object dependencies, we recommend the following deployment order.

Global (compute engine -> data source -> Statistical Period -> Global Variable -> Public Calendar -> Object Property -> third-party Python package -> data block -> project -> Identification Feature).
Data Architecture (subject domain -> Business Activity -> Business Object).
Data Security (key -> data classification -> data sensitivity level -> Identification Feature).
Data Standard (code table Directory -> code table -> Word Root -> Standard Set Directory -> Standard Set -> Common Standard Property -> Standard Template).
Data Quality (Quality Rule Template).
Standard (Data Standard -> Standard Mapping Rule).
Development (offline physical table -> node task).
Tag Architecture (Tag Entity -> Tag Entity ID).
Tag (Workbench Object).
Data Quality (Quality Rule).
Data Standard (Mapping Relation (Asset Granularity)).
Data Security (Identification Result (Table Granularity)).