ch9tan-design commented on issue #68382: URL: https://github.com/apache/airflow/issues/68382#issuecomment-4679662382
Thanks for the guidance. My initial thought is to identify all entry points where a connection port can be provided (Connection model, Task SDK, REST API, Execution API, CLI, and JSON schema) and determine whether there is already a shared validation layer that can be reused. If possible, I would prefer to centralize the validation logic to avoid duplicating the port range check across multiple components. I'll investigate the existing validation patterns in these areas and submit a PR with the proposed approach. Please let me know if there is a preferred validation layer I should follow. -- 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]
