Skip to main content

New API features in R2024-03

Features Description

Deployment strategy on a Remote Engine cluster

When configuring how a Route or data service task runs on a Talend Remote Engine cluster using API, you can use the optional parameter deploymentStrategy to determine how this task should be deployed.
  • Rolling: Tasks are deployed one by one to the engines of the cluster. This means that for a short time, different engines will be running different versions of the task, therefore you can avoid service interruption.
  • Parallel: Tasks are simultaneously deployed to all the engines of the cluster. Before deploying a new version of a task, you will need to undeploy the currently running version, which will result in service interruption.
The related endpoints are:

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!