DanielLeens commented on issue #11579: URL: https://github.com/apache/seatunnel/issues/11579#issuecomment-5111527880
This looks like a useful operator-focused feature track rather than a bug. The workflows listed here are reasonable, but I would avoid landing them as one large Web UI change because they mix several different risk levels: job submission and control, savepoint and restart flows, checkpoint observability, OptionRule-driven dynamic forms, and worker/admin settings. A safer path would be to split this into phases: 1. first PR: submit job from text/file, plus stop/cancel with confirmation and clear status feedback; 2. second PR: savepoint / restore / restart flows, once the backend contract and failure states are explicit; 3. later PRs: checkpoint history and OptionRule-driven forms; 4. worker tag updates and cluster security/status views only when the backend API boundary is stable enough. The main review boundary is that the Web UI should stay a thin client over the existing Zeta APIs, and sensitive values must never be exposed back to the page. If someone wants to pick this up, a smaller first PR will be much easier to review and merge than one umbrella implementation. -- 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]
