DanielLeens commented on issue #12721:
URL: https://github.com/apache/seatunnel/issues/12721#issuecomment-6108868097

   Classification: A / seatunnel-cli REST endpoint selection.
   
   The current source confirms the root cause. `config/seatunnel.yaml` enables 
Jetty HTTP on 8080; Jetty registers `/running-jobs`, `/option-rules`, 
`/submit-job`, and `/job-info` directly, while `seatunnel-cli` still defaults 
to 5801. #12722 is the correct focused implementation: it changes that default, 
retains the environment override, updates both language documents, and its 
current Build, lint, and Python test jobs succeeded.
   
   Before merge, please add one behavior-level regression that verifies 
`_check_engine()` probes `/running-jobs` using the default base, not just that 
the module constant spells 8080. The release-facing documentation should also 
make the behavior boundary explicit: a local engine reachable on 8080 now 
selects the already-confirmed REST submission path instead of the offline/local 
fallback. The existing confirmation panel is important and must remain.
   
   The PR still requires regular review, so this is not fixed in dev yet.


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