andersbogsnes commented on PR #27796: URL: https://github.com/apache/airflow/pull/27796#issuecomment-1326320063
I don't have a strong opinion either way, it's more of a conceptual issue of what a URI means and what end users can expect to use that for. My team ran into it because they had an expectation that they can directly use an Airflow uri as a connection string, which is a general requirement if we want to support using f.ex a Postgres connection to inject the DB url into a KubernetesPodOperator via Jinja Templating. I would argue that getting a uri should be consistent across public APIs or explicitly documented as being for one purpose or the other. Which is correct in this case, I'll leave up to you - it's not blocking anything since there's a simple workaround as pointed out previously. The core is the end-user "surprise" at the difference between the APIs -- 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]
