Skip to main content Skip to complementary content

Adding an existing Remote Engine to a Remote Engine Cluster

Enrich the shell script created in the previous example to add the Remote Engine to an existing Remote Engine Cluster.

Before you begin

You have a Remote Engine installed and already paired.

You already have a Remote Engine Cluster.

About this task

The following example extends the shell script shown in the previous example but can also be used standalone, provided that you have a personal access token or a service account token to authenticate your API request.

Procedure

Add the Remote Engine to the Remote Engine Cluster of your choice with a PUT as follows.
curl -X PUT 
--header 'Content-Type: application/json' 
--header 'Accept: application/json' 
--header 'Authorization: Bearer 'personal_access_token or service_account_token'' 
'https://api.us.cloud.talend.com/tmc/v1.3/runtimes/remote-engine-clusters/5dc02e89f87cb233a2f83990/engines/5d2f1d9018e83f4406199233'
Information noteNote: You can retrieve Remote Engine and Remote Engine Cluster IDs with a GET on the /tmc/v1.3/runtimes/remote-engines or /tmc/v1.3/runtimes/remote-engine-clusters endpoints. You can also find their ID from the URL in Talend Cloud when displaying a Remote Engine or Remote Engine Cluster details.

Results

The Remote Engine is added to the Remote Engine Cluster.

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!