vincbeck commented on PR #47691: URL: https://github.com/apache/airflow/pull/47691#issuecomment-2736647882
> LGTM overall. Just one question will that also impact `airflow standalone` ? It looks like it by the config update but I'm not sure about that. (At first I thought this was only for development purpose in breeze) It will. We set simple auth manager as default auth manager in airflow config so `airflow standalone` (unless it overrides the auth manager but I do not think so?) and any other installation of Airflow will have simple auth manager as default. I agree this is a bit weird cause the simple auth manager is only for development purposes so that means forcing users to switch to another auth manager for production purposes. But we also agreed on that plan to make the simple auth manager by default in Airflow so that we no longer have FAB dependency in Airflow by default. Also, since we might want to deprecate/remove/discourage users of using FAB auth manager in Airflow 3.X as some point, we cannot make it the default one. We would need to wait for Airflow 4.0 to change that, we do not want that. So having for now the simple auth manager as default and telling users to use another one for production purposes is probably the most future safe. -- 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]
