-
Notifications
You must be signed in to change notification settings - Fork 16.4k
[helm] Isolate defaultUser handling in createUserJob #59767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[helm] Isolate defaultUser handling in createUserJob #59767
Conversation
|
I cleaned the fork branch, so it affected to close pr:59715, so I created an alternative pr. |
* [helm] Move defaultUser to createUserJob * [test] Fix ruff format * [test] Fix static check value of chart * remove redundant file --------- Co-authored-by: nhuan.bc <nhuan.bc@teko.vn>
|
Hi there - the default values of the latest Helm chart version (1.18) still reference defaultUser under webserver: Is that planned to change in the next version of the Apache Airflow Helm chart? I'm trying to deploy v1.18 with modified admin user credentials. Thanks so much, sorry if answer is obvious. |
Yes, see this PR. You can wait until (pending/overduw) 1.19 release of the helm chart or pull it from main which includes this here. |
* [helm] Move defaultUser to createUserJob * [test] Fix ruff format * [test] Fix static check value of chart * remove redundant file --------- Co-authored-by: nhuan.bc <nhuan.bc@teko.vn>
* [helm] Move defaultUser to createUserJob * [test] Fix ruff format * [test] Fix static check value of chart * remove redundant file --------- Co-authored-by: nhuan.bc <nhuan.bc@teko.vn>
What:
airflow userscommand (FAB CLI Commands). Therefore, I believe thatdefaultUsershould not be part of thewebserver or apiServer.createUserJobdepends on thewebserver, but thewebserverhas been replaced by theapiServer. As a result, we should movedefaultUserto theapiServer configuration.Solution:
defaultUserintocreateUserJobto isolate the functionality of createUserJob.webserver.defaultUserfrom the Helm chart and related tests.^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.