Dear: Wechat group "Apache Linkis(incubating) community Development group "chat records are as follows: 微信群"Apache Linkis(incubating) 社区开发群"的聊天记录如下:
————— 2022-11-4 ————— Mr. Flash 18:09 Everyone ask for advice, if you want to migrate a workflow to a new environment, after the export workflow, the content of bml how to do migration. Do you have any ideas? Li Meng 18:21 Is it a workflow that flows from one dss workflow to another new product, or to a new dss? Mr. Flash 18:22 It's a completely new environment. For example, my development environment does the development, and I go to the production environment. It's network isolated Li Meng 18:24 Oh oh, this has been done in the micro crowd, the original open dss1.0 version of dev tried to release directly to the production environment Li Meng 18:26 I tried this a long time ago, writing workflow transitions and releasing zip package transitions to new environments, especially for very large workflows, which were slow to navigate Mr. Flash 18:26 That's the Internet connection, right? I'm not connected right now. I can now export the zip for workflow Mr. Flash 18:26 However, the zip does not contain the specific hql file Li Meng 18:26 Get them all down. There's a nodeid Mr. Flash 18:27 I know that bml can be downloaded according to resourceid and versionid Mr. Flash 18:28 But download me to the new environment what to do... Mr. Flash 18:28 Or the zip actually contains these resource files peacewong@WDS 18:28 @HmhWz_webank help check it out Li Meng 18:28 My idea is to create a plug-in, like appconn, that supports zip uploads in the new environment hy 18:41 The exported zip package should contain all resources, script files, and re-upload all resource files to the new bml service when importing the new environment. We can see the code in the orchestrator/importOrchestratorFile the import interface implementation. Future open source releases plan to provide import/export workflow buttons on the front page. Mr. Flash 18:43 Thanks for testing it out, we didn't know it was actually a script ————— 2022-11-6 ————— Mr. Flash at 11:37 Mr. Flash at 11:37 [Showing teeth] 闪电先生 18:09 各位大佬 请教一下，如果要迁移一个工作流到一个全新的环境，导出工作流以后，bml里面的内容怎么做迁移。 各位大佬有思路吗？ 李孟 18:21 是一个从一个dss workflow 导到另一个新产品的工作流，还是导到一个新的dss? 闪电先生 18:22 是一个全新的环境，比如我开发环境做好了开发，去生产环境投产。 是网络隔离的 李孟 18:24 哦哦，这个微众行内做过，原来开放dss1.0有一版dev尝试过，直接发布到生产环境 李孟 18:26 我很久以前尝试过，写workflow转换 ，把zip包转换发布新的环境，就是尤其那种非常大的workflow，导的时候比较慢 闪电先生 18:26 那是网络联通是吧 我现在网络是不通的。我现在工作流可以导出zip 闪电先生 18:26 但是zip里面不包含具体的hql文件 李孟 18:26 都搂下来，有nodeid 闪电先生 18:27 我知道是根据resourceid和versionid去bml去可以下载 闪电先生 18:28 但是下载了 我到新的环境 要怎么做…… 闪电先生 18:28 还是zip里面其实是包含这些资源文件的 peacewong@WDS 18:28 @HmhWz_webank 帮忙看看 李孟 18:28 我的想法是的，搞个插件，类似appconn那种，在新环境，可以支持zip上传 hy 18:41 导出后的zip包应该要包含所有的资源、脚本文件，导入新环境时会重新上传所有资源文件到新的bml服务。可以看下代码中orchestrator/importOrchestratorFile这个导入的接口实现。后续的开源版本会计划把导入导出工作流的按钮提供到前端页面上。 闪电先生 18:43 感谢 我们测试一下，之前一直不知道其实包含了脚本 ————— 2022-11-6 ————— 闪电先生 11:37 闪电先生 11:37 [呲牙] -- Best Regards ------ 康悦 ritakang GitHub：Ritakang0451 E-mail：rita0...@163.com
