jscheffl commented on PR #41777:
URL: https://github.com/apache/airflow/pull/41777#issuecomment-2316302602

   > > Did a review - if we would not want to replace FAB in Airflow 3 I would 
have made an approve, but as we actually want to get rid of it... Might be we 
need to introduce another method of integration that is future proof.
   > > Will the AWS Auth Manager render the views inside Airflow UI or just add 
menu entries which point to an external site?
   > 
   > 100% agree with you but the intent of this PR is not to drop FAB from 
Airflow. That requires a lot of work and will be done in separate PRs. The way 
I register views in the auth manager is the way it is done today so I dont add 
anything new. Definitely this will need to be reworked/redone later to complete 
AIP-79. And yes likely we will need a mechanism similar to AIP-68 will expose 
for plugins so that the auth manager can add new views to an Airflow environment
   
   I just want to clarify not to add a new interface and therefore add a new 
legacy - even if it is used the same way but unclean today.


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to