Transport existing tasks between Servers

[GonzaloPerezPrim]

Hi

We would like to create tasks on a separate development server with a security configuration and then export and import these tasks to a productive environment.  That also allow us to have the endpoints separately

We have tried to export the task configuration from the development server and then imported on the new server, but it is not working correctly, we have that is a task connected a Development Source Endpoint and we want to move it and then map it with the Production Endpoint but we do not see if it is feasible.

Is there any other way to perform this type of production deployment? In other systems, we have read the setup guide and in theory is possible to modify the import/export json task, but this is a prone error task and it could also delete the settings.

Any recommendation

Kind regards

Gonzalo

[AlexeySosnovskih]

In order to implement it, you need endpoints to have same names on Prod and Dev servers.

Then when you export from Dev, you have an option to exclude endpoint configuration from JSON, so that only endpoint name will be in the JSON.

Then import it to production, this way you should be able to map task to Production endpoints.

[GonzaloPerezPrim]

Hi Alexey:

Do you if this option is available through the command line? I have not being able to found it through the replicate console. I wonder where it is possible to customize to exclude JSON endpoint configuration.

Kind regards

Gonzalo 

[AlexeySosnovskih · Accepted solution]

If you are looking for UI option - this option is available in QEM.

Or you can use QEM api - if you are looking for script approach.