DataWorks:Create a deployment package to deploy objects in the deployment package across workspaces

Limits

Your account must meet the following conditions:

• Your account is assigned the Workspace Administrator, O&M, or Deploy role of the source workspace.

• Your account is assigned the Workspace Administrator, O&M, or Deploy role of the destination workspace.

For information about how to assign roles to a user, see the "Add a RAM user to a workspace as a member and assign roles to the member" section of the Manage permissions on workspace-level services topic.

Procedure

1. Go to the Deployment Package Creation page.

   In the left-side navigation pane of the Deploy Center page, click Deployment Package Creation.

   Note

   • The Deployment Package Creation page displays the committed nodes in the current workspace. All committed nodes can be packaged and deployed on this page.

   • A node can be repackaged only if the status of the deployment package to which the node belongs is Deployed or Failed.

2. Create a deployment package.

   On the Deployment Package Creation page, add the objects that you want to deploy, such as nodes, functions, and resources, to a deployment package.

   1. Select a deployment environment.

      In the area that is marked with 1, select the cross-workspace deployment environment for the deployment package that you want to create.

   2. Search for objects based on specific conditions.

      In the area that is marked with 2, search for objects based on specific conditions, such as Solution, Workflow, and Node Type.

   3. Add the objects to a deployment package.

      In the area that is marked with 3, select the objects that you want to deploy and click Batch Add to Deployment Package. After you add the objects to the list of undeployed objects, the number of objects to be deployed is displayed in the upper-right corner of the Nodes to Deploy button.

      Note

      If you want to deploy only a small number of objects, you can find each object that you want to deploy and click Deploy in the Actions column. In the Deployment Confirmation dialog box, you can perform subsequent operations as prompted.

   4. Confirm the deployment information and deploy the objects.

      1. View the objects to be deployed.

         • View the objects to be deployed: Click Nodes to Deploy. In the Nodes to Deploy pane, view the basic information about the objects to be deployed, such as ID, Node Type, Change Type, and Node Status.

         • View object details or remove an object: Find the object that you want to view or remove and click View Details or Remove in the Actions column.

      2. Confirm the deployment information.

         Click Deploy All. In the Deployment Confirmation dialog box, enter a name in the Deployment Package Name field and check the deployment environment and the objects to be deployed.

         Note

         When you deploy objects across workspaces, you can change the resource groups that are used to run the objects in the destination workspace only if your account is assigned the Development or Workspace Administrator role.

         

      3. After you confirm the deployment information, click Deploy. The system creates a deployment package and deploy the objects in the deployment package.

         Note

         • For a node whose instance generation mode is Next Day, the deployment takes effect based on the following rules:

           • If you deploy the node before 23:30 on the current day, the deployment takes effect on an instance that is generated for the node on the next day.

           • If you deploy the node after 23:30 on the current day, the deployment takes effect on an instance that is generated for the node on the third day.

         • For a node whose instance generation mode is Immediately After Deployment, the deployment takes effect based on the following rules:

           • If the scheduling time of the node is at least 10 minutes after the node is deployed, the updated instance is generated as scheduled.

           • If the scheduling time of the node is within 10 minutes after the node is deployed, or you deploy the node after 23:30 on the current day, the updated instance is generated on the third day.