Introduction

Until now, the use of multiple DataFlow instances has been allowed (soporte multitenant en Dataflow).

With this improvement, our intention is to make it easier for users to create pipelines and manage them between these instances.

We have added the possibility of duplicating pipelines from a multiple selection of pipelines in the Dataflow list to different instances.

Functionality to duplicate pipelines

Now we can duplicate one or several pipelines and all their contents in one or several instances in a simplified and intuitive way.

How to use it?

From Menu>Processing>DataFlows Management we select the pipelines that we want to clone.

Open

Once selected, click on the Duplicate Selected button.

Open

We will be redirected to a new screen where we can select the instances. This instances will be the destination where the previous selected pipelines will be duplicated. Once selected, click on the Duplicate button.

This will return us to the list of pipelines and will generate new pipelines with the following naming convention: pipelineSelected_instanceSelected. If the selected instance is the owner of any of the selected pipelines, that pipeline remains in its instance without being duplicated.

There is also the possibility of accessing this function via REST API, to do this click on the top three points > APIs > Control Panel. Also, click on the API Key to copy it.

This gives us access to a Swagger UI where we can navigate to the DataFlow endpoints.

We then click on the Authorize button and paste the API Key we copied earlier.

Once authorized, look for the endpoint POST /api/dataflows/pipelines/duplicate and click on the Try it Out button.

Enter the identifiers of the pipelines to duplicate and the instances where we want to duplicate them to. After doing so, click on Execute.

If we scroll down, we can see the response.

Finally, in case we make a mistake when entering the identifiers, the system will warn us of the error and will only duplicate the correct identifiers, meaning errors will not block the rest of the process.

What changes does this new feature bring?

Up until now, a user could have more than one instance assigned to him, although the nature of this made this case impractical. After the implementation of this functionality, a user must be the owner of only one instance, otherwise there could be conflicts when duplicating pipelines on these instances.