privking opened a new issue, #15888: URL: https://github.com/apache/dolphinscheduler/issues/15888
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description The current export and import functionality is very similar to the existing copy functionality. I think more application scenarios should be copying from one environment to another environment (such as publishing a development environment to a production environment), or being able to restore it after being accidentally deleted. But the problem is: 1. If it is accidentally deleted and re-imported, the re-imported workflow name will be added with the `_import_` suffix, and the dependencies of the sub_process will also be invalid(the reference is still the original deleted id). 2. If you are migrating from one environment to another, in addition to the name problem, if the task instance involves references to similar data sources, the references will also become invalid. suggestion: 1. Do not modify the workflow name when importing, and overwrite the original one if there is a conflict? 2. Is the import done in two steps? 1. Check the data source references used in the instance, and pop up a window to confirm which reference these references correspond to in the new environment. 2. Submit the imported content and replacement information ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
