davidzollo opened a new issue, #11579: URL: https://github.com/apache/seatunnel/issues/11579
## Background SeaTunnel Engine already exposes many operational capabilities through REST API and CLI. The built-in Web UI currently focuses on visual inspection of cluster overview, jobs, job details, logs, realtime metrics, workers, and master status. It would be useful to add common operation controls to the Web UI so operators can complete frequent Zeta workflows without leaving the console. ## Proposed capabilities - Submit a job from configuration text. - Submit a job by uploading a configuration file. - Stop a running job gracefully. - Cancel a running job when force termination is required. - Stop a job with savepoint. - Restart or resubmit a job from checkpoint or savepoint state. - View checkpoint overview and checkpoint history from the job detail page. - Browse connector OptionRule metadata for UI-driven dynamic forms. - Update worker node tags from the UI when supported by the backend API. - Show HTTP, HTTPS, and authentication status in a safe read-only operations view. ## Notes - The UI should reuse the existing Zeta REST API where possible. - Destructive or state-changing actions should include confirmation and clear status feedback. - Sensitive values such as credentials, tokens, and passwords must not be displayed in the UI. - The first implementation can split these items into smaller PRs if that is easier to review. ## Related docs - REST API V2: https://seatunnel.apache.org/docs/engines/zeta/rest-api-v2 - Job Lifecycle API: https://seatunnel.apache.org/docs/engines/zeta/rest-api-job-lifecycle - Web UI: https://seatunnel.apache.org/docs/engines/zeta/web-ui -- 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]
