potiuk commented on issue #24728: URL: https://github.com/apache/airflow/issues/24728#issuecomment-1170006615
I am also quite there with @ashb but also not totally against. I would rather focus on making Airflow UI as "pure" as possible - without enforcing any conventions. The owner feature has already vague enough meaning to put some kind of meaning to it via UI feature. Wild idea. Well. Owner can be anything. Including URL. Why don't we simply detect in the UI if a field (any sutiable field/property coming from Airflow DB) is a URL, and make it clickable then? That will make airflow less opinionated, no need to make configuration and program it and it gives the users an opportunity to make use of their own conventions. I think this is far better - it actually puts full power in the hands of users without much of functionality in Airflow and it solves any of the follow-up problems of the nature (I am anticipating user's questions if we make it into a feature): "Right, we have two teams with two different owner URLS, - should we make a dictionary config ? How should I do it?" -- 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]
