prakharcode commented on issue #51304: URL: https://github.com/apache/airflow/issues/51304#issuecomment-3323850261
I am also currently facing this bug, while trying to deploy aiflow 3.0.2 and using simple.auth.manager in the CI environment. While I understand that simple auth is not made to be something to be deployed in production but it is a good (fast) way to go with in CI and alike. @mrbungie summarized quite well here: > If that's not the hoped behaviour, I would guess AIRFLOW__CORE__AUTH_MANAGER, if set, should be propagated down into the create-user container (after all, if its going to run create-user in Airflow 3, it should have that set to FAB or it is always going to fail). Maybe the create-user container should check if FAB is on (via env var + airflow.cfg), and if not, it should just continue gracefully and maybe logging that so users are advised to set createUser = false if they are just using Simple Auth. giving an option in the helm chart to do `enable: false` would be nice, then the onus of disable and enabling the service is on the user. If this makes sense, I can contribute to include this in the chart. I see the issue is already assigned to @Brunda10 but if they are not working I can take it up or they can continue with this direction if maintainers agree. -- 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]
