DanielLeens commented on issue #11579: URL: https://github.com/apache/seatunnel/issues/11579#issuecomment-5148480866
Thanks for opening #11613 and linking it back here. The PR gives this issue a concrete implementation path, but because it covers more than the first phase originally suggested here, the review should be especially strict about the operational boundaries: job submission, stop/cancel, savepoint, restore, checkpoint history, OptionRule metadata, worker tags, and HTTP service status are not all the same risk level. For the issue status, I would keep this open until #11613 is reviewed and its Build check is green. On the PR side, the key thing is to keep destructive operations guarded by confirmation, keep the Web UI as a thin client over existing Zeta REST contracts, and make failure/permission states visible instead of silently swallowing backend errors. -- 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]
