GitHub user potiuk added a comment to the discussion: override simple auth manager for `airflow standalone` to use provided config
> Is there any better/more clean way of tackling it? There is no recommended approach. - it's more of a deployment and dev env decision. You can do a range of things from local venvs, to building docker-compose containrs, or running k8s. Every user has different expectations for those and it's up to you to choose a proper method of deployment that involves the way how you usually share development environment with your teams. We do not have a single recommended approach - but variety of ways you can deploy airflow described in https://airflow.apache.org/docs/apache-airflow/stable/installation/index.html I think the question is why Standalone with SImpleAuthManager is not something you can adjust to. But if you explain your use case with all the constraints and expectations on the devlist - maybe SimpleAuthManager is somethign that would indeed serve your case. So I - again - propose you start a devlist discussion where you explain how you used it, what is your workflow, and how you adapted it to your case and how you see it can be useful for others in similar way. Then it might turn into one of the "recommended ways" especially if user like you will contribute back the description, use case, documentation written from the perspective of such user. Big part of our documentation has been created by users turned into contributors who either implemented some changes to fit their use case or simply contributed documentation describing "recommendation" and approach they have taken and generalized it so that others could find it useful. We have > 3300 contributors and many of them are those kind of contibutions are very much welocme. GitHub link: https://github.com/apache/airflow/discussions/53225#discussioncomment-13755536 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
