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|
||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.
|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:
|Resource||Created||Overwritten (Override) with values from the source environment or ignored (Keep target).||-|
Workspaces are created with empty roles: administrators must create them in the target environment.
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.
|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.
|Run profile||Created||Overwritten (Override) with values from the source environment or ignored (Keep target).||-|