Promotion rules - Cloud

Talend Management Console User Guide

Version
Cloud
Language
English
Product
Talend Cloud
Module
Talend Management Console
Content
Administration and Monitoring > Managing projects
Administration and Monitoring > Managing users
Deployment > Deploying > Executing Pipelines
Deployment > Deploying > Executing Tasks
Deployment > Scheduling > Scheduling Tasks
Last publication date
2024-02-29

Promoting objects from a source to a target environment follow pre-configured rules.

Personal workspaces cannot be promoted.

If you are promoting objects that contain webhooks, ensure that the source and target environment names do not contain any special characters, only alphanumeric characters and underscores.

Object Object does not exist in target environment Object exists in target environment Note
Job artifact/task Created
  • Environment: if the target environment name is the same as a context environment in Talend Studio, the artifact/task is created with context parameter values of the design pulled from Talend Studio.
  • Tags: the target task has the same tags as the source task.
  • Tasks: if the source task uses the option to automatically update to the latest version of its artifact, it is not enabled in the target task.
Updated
  • Parameters:
    • Existing parameter values remain unchanged.
    • If a new version of the artifact/task has new parameters, they are added to the Parameters.
  • Environment: if the target environment name is the same as a context environment in Talend Studio, the values for the new parameters are pulled from Talend Studio. Otherwise, they correspond to the values set in the source environment.
  • Tags: the target task is updated with the tags of the source task.
  • Artifact: for artifact promotion, tasks do not use promoted artifacts even if they are set to use the latest artifact version, because this latest artifact version only refers to versions of the published artifact. You need to test the promoted artifact before eventually publishing this artifact for your tasks to use it.
  • Tasks:
    • If the target task uses a specific version of the artifact, it keeps using this version and the option to automatically update it is not selected.
    • If the target task uses the option to automatically update the artifact version, the version is updated to the one used by the source task and the option remains enabled.
The promotion workflow is designed to prevent unintended artifact updates when your tasks are promoted.

For this reason, when a promoted task is created in the target environment for the first time, the auto-update option, Always use the latest available artifact version, is automatically deactivated.

This ensures that your task is not inadvertently updated to a new artifact version before you have a chance to review and test the promoted task and confirm the correct artifact version to be used.

Pipeline artifact/task Created
  • Tags: the target task has the same tags as the source task.
  • Tasks: if the source task uses the option to automatically update to the latest version of its artifact, it is not enabled in the target task.
Updated
  • Parameters: existing parameter values remain unchanged.
  • Tags: the target task is updated with the tags of the source task.
  • Tasks:
    • If the target task uses a specific version of the artifact, it keeps using this version and the option to automatically update it is not selected.
    • If the target task uses the option to automatically update the artifact version, the version is updated to one used by the source task and the option remains enabled.
-
Plan Created Updated -
Connection Created with the same name and type Updated with the same name and type

Parameters are unchanged.

If a connection with the same name but different type exists in the target environment:
  • The promotion analysis displays an error.
  • The promotion report displays an error and the task is not promoted.
-
Resource Created Overwritten (Override) with values from the source environment or ignored (Keep target). -
Task scheduler Created Updated -
Workspace Created

Workspaces are created with empty roles: administrators must create them in the target environment.

Updated

The objects in the workspace are updated according to the rules in this table.

-
Talend Remote Engine or Remote Engine Gen2 part of the task/workspace/environment promoted Created

New Remote Engines must be paired after promotion.

Updated -
Remote Engine cluster Created

Talend Remote Engines are not promoted/created during the cluster promotion. They must be added to the promoted cluster in the target environment.

Reused -
Run profile Created Overwritten (Override) with values from the source environment or ignored (Keep target). -