det101 commented on issue #17252:
URL: 
https://github.com/apache/dolphinscheduler/issues/17252#issuecomment-3031879716

   
   
   > ### Search before asking
   > * [x]  I had searched in the 
[DSIP](https://github.com/apache/dolphinscheduler/issues/14102) and found no 
similar DSIP.
   > 
   > ### Motivation
   > #### Current Workflow Issues
   > ##### Operational Process:
   > 1. Development Process: For development workflows, the following steps 
must be executed: 1. Return to the workflow list -> 2. Deploy the workflow -> 
3. Run the workflow -> 4. Check the runtime logs.
   > 2. Modification Process: Adjusting workflow content is more complex: 1. 
Return to the workflow list -> 2. Undeploy the workflow -> 3. Enter workflow 
editing -> 4. Return to the workflow -> 5. Deploy the workflow -> 6. Run the 
workflow -> 7. Check the runtime logs.
   > 
   > ##### Technical/Design Factors:
   > 1. The workflow lacks a development state. While this simplifies logic and 
reduces bugs, it shifts complexity to the user.
   > 2. The design prioritizes production stability, requiring users to be more 
cautious when making adjustments.
   > 
   > #### Desired:
   > Operational Process Optimization: Introduce a dedicated development 
workflow, separate from the production workflow (which can only be deployed 
from the development environment and cannot be created directly).
   > 
   > 1. Development Workflow Process: Only requires: 1. Modify workflow content 
-> 2. Run the workflow -> 3. Check the runtime logs.
   > 2. Deployment Process: Publish a development workflow to the production 
workflow (overwriting if previously deployed).
   > 
   > ##### Technical/Design Optimization:
   > 1. Development and production workflows are stored in separate tables with 
completely independent data.
   > 2. Development workflows lack a deployment state, allowing debugging. 
Running workflows and task instances are isolated from production.
   > 3. During deployment, the current version of the workflow is copied to the 
production workflow record, with an association logged (for subsequent 
overwrites).
   > 
   
   
   In order to focus more on the problem to be solved, I updated the problem 
analysis and solution description. Please judge it.
   @SbloodyS @Gallardot @danielfree @dill21yu @ruanwenjun 


-- 
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]

Reply via email to