Bisk1 commented on issue #10913: URL: https://github.com/apache/airflow/issues/10913#issuecomment-1816608710
I would like to revive this thread because recently I've spend a lot of time when I was trying to set up an HTTPS connection. Currently if I want to do it then the URI has to be either `http://example.com/https` OR `http://https%3A%2F%2Fexample.com` but the most intuitive one: `https://example.com` doesn't work. I also noticed that there was more work done on supporting the second pattern: https://github.com/apache/airflow/pull/31465 which makes it seem like it is now the recommended solution rather than a bug. I feel like there is a design decision needed here. Either Airflow committers agree that the current URI syntax: https://airflow.apache.org/docs/apache-airflow/stable/howto/connection.html#uri-format is the final one and in that case this issue should be closed. Alternatively (which is in my opinion better) we could try to aim at changing the URI syntax so that only the 3rd pattern is valid and others are deprecated. E.g. schema (actually 'scheme') and protocol could be considered as one and the same thing in the connection model (in future, now it would be a breaking change). And connection type can be derived from the scheme in code (e.g. if the scheme is HTTPS then conn_type is HTTP, in almost all other cases conn_type = scheme). Then the path part is not needed and hostname should not contain protocol because it will be available in scheme. I'm willing to propose some solution and deprecation path (so that the old patterns are only supported until Airflow 3) if the community sees value in this idea. -- 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]
