Pipelines can be exported to and imported from arrays with a simple method call to the TfPipeline object. That's cool, but it doesn't help end users as this functionality is not currently exposed. So, it would be desirable to have import/export forms like for example Views and Rules provide them.

CommentFileSizeAuthor
#1 transformations_ui_import-export001.diff6.1 KBsepgil

Comments

sepgil’s picture

sepgil commented
Assigned: Unassigned » sepgil
Status: Active » Needs review
StatusFileSize
new transformations_ui_import-export001.diff6.1 KB

Made a patch for the requested feature.
It works like the Import/Export from rules, but there is also the option to export single pipelines(thought that would be practically).

amitaibu’s picture

amitaibu
Primary language Hebrew
Location Israel
commented

There are lots of tabs in the patch. we'll test it when I have a chance

jpetso’s picture

jpetso commented
Status: Needs review » Needs work

Before import/export forms can go in, the patch needs to solve the problem of exporting sub-pipelines (ones that are contained in Pipeline or For-Each Loop operations, or other operations that might store pipelines as arguments). Currently the export functionality stores those pipelines as embedded pipelines, which cannot be edited with the current UI after importing. Thus, a proper export mechanism would probably export multiple pipelines at once - the actually exported pipeline and all of its sub-pipelines as well.

mitchell’s picture

mitchell commented

#3: Would Rules 2's looping support and the transformer action help with this?

jpetso’s picture

jpetso commented

Rules 2 is generally the way to go. Transformations is not being actively developed at the moment, so if you can find a solution elsewhere (Rules rules!), all the better.