Breeze start-airflow command wasn't able to initialize the db in 1.10.x#11207
Breeze start-airflow command wasn't able to initialize the db in 1.10.x#11207potiuk merged 4 commits intoapache:masterfrom
Conversation
| airflow initdb | ||
| else | ||
| airflow db init | ||
| airflow users create -u admin -p admin -f Thor -l Adminstra -r Admin -e dummy@dummy.email |
There was a problem hiding this comment.
| airflow users create -u admin -p admin -f Thor -l Adminstra -r Admin -e dummy@dummy.email | |
| airflow users create -u admin -p admin -f Thor -l Adminstra -r Admin -e dummy@dummy.email || true |
This will help in case of no RBAC.
There was a problem hiding this comment.
Actually that line is only for version 2 onward, but it gave me an idea to include create_user also for the RBAC setup. See my next commit.
There was a problem hiding this comment.
@potiuk there won't be any RBAC option in 2.0 anymore, right?
There was a problem hiding this comment.
Ther won't be indeed. But we are still able to install 1.10 in the ./breeze from 2.0 (for convenience) via --install-airflow-version . So we should add this option just for that case. I am going to do it shortly.
| airflow initdb | ||
| else | ||
| airflow db init | ||
| airflow users create -u admin -p admin -f Thor -l Adminstra -r Admin -e dummy@dummy.email |
There was a problem hiding this comment.
Ther won't be indeed. But we are still able to install 1.10 in the ./breeze from 2.0 (for convenience) via --install-airflow-version . So we should add this option just for that case. I am going to do it shortly.
….x (apache#11207) (cherry picked from commit 03e0ff2)
….x (apache#11207) (cherry picked from commit 03e0ff2)
The database initialization needs a different cli command (the old
initdb).Also it is not necessary to create a dummy user in version 1.10.x to allow people to login in the Web UI.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.