venkatamandavilli-code commented on issue #68382: URL: https://github.com/apache/airflow/issues/68382#issuecomment-4732328662
Thanks for reporting this. I agree that connection port validation should be enforced closer to the point where the connection is created or updated rather than being discovered later during task execution. From a user perspective, a connection with an invalid port appears to be successfully configured, but the resulting failures only occur when a hook or provider attempts to use it. This can make troubleshooting more difficult because the root cause is separated from the place where the incorrect value was originally entered. Since valid network ports have a well-defined range (0–65535), enforcing validation consistently across the model, API, CLI, and UI would help prevent invalid configurations from being persisted and reduce runtime errors. This also seems like a good candidate for a centralized validation approach so that all connection creation paths behave consistently and future entry points automatically inherit the same validation rules. -- 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]
