DanielLeens commented on issue #11511: URL: https://github.com/apache/seatunnel/issues/11511#issuecomment-5040697976
Thanks for writing this up so concretely. I checked the current branches, and the state is exactly the split you described. On current `dev`, the old stub is gone and `SeaTunnelConfValidateCommand` now performs real env / connector / option validation, so #10763 does cover the functional bug there. But the released 2.3.13 behavior still silently returns success for invalid configs, so this remains a real release-line problem even though `dev` is already fixed. So the right status here is "fixed in dev, still wrong in the current release." Keeping this open makes sense until we either backport the validation behavior to the 2.3.x line or explicitly document in the 2.3.x command docs / release notes that `--check` is not a trustworthy validation gate in 2.3.13. -- 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]
