potiuk commented on issue #54098: URL: https://github.com/apache/airflow/issues/54098#issuecomment-3160836721
I think use "they" in a bit "accusative" tone, I prefer if people use "we" as I think maintinaers, code contributors and users are the same community and anyone of those contributes to make Airflow better,. I think it would be great if someone who has good knowledge about those (@suhail-zemoso @somas193 ) could dive deeper and see if they can figure out what exactly is wrong. The "no sufficient documentation" comes likely from the fact that the Fab provider has it's own, documentation for Oauth and what you really have to do (and always had to) is to look at FAB docs - see how to configure it in and adapt it to way how to pass it to Airflow. And a number of changes come from the fact that there are different Fab versions and changes in managing acess there. And many questions of "what to do" or "how to do things better" should be asked with Flask Applicatio Builder. And of course - there might be some bugs, but without help of the community who could dive deeper, this might be difficultt to solve things (also if the community people who solved their problems and learned how to combine the two - are more than welcome to update the documentation - maintainers are generally quite bad in writing documentation and the best way how users can contribute back (let me remind everyone - for the software they got for free without any guarantees - and one they paid exactly 0 for, where many maintainers implement things in their free time after hours and away from their families). Luckily maintainer recognized the dificulty with Fab integration and we are workng on a native KeyCloak Auth Manager that shoudl hopefully be available at the time of 3.1 release. Again documentation migh not be perfect there, but I count on eveyrone here to try out the RC, learn together with us how to use the integration effectively and - yes - possibly even contriubute back nice documentation written by the users who solved the initial problems and described in the way that other users can make use ot it (again maintainers are not good in writing good docs, but users who write docs for themselves to solve their problems are great). -- 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]
