-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
[AIRFLOW-3303] Deprecate old UI in favor of FAB #4339
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4339 +/- ##
==========================================
- Coverage 74.76% 73.46% -1.31%
==========================================
Files 429 421 -8
Lines 29652 27529 -2123
==========================================
- Hits 22170 20224 -1946
+ Misses 7482 7305 -177
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm in favour of this change, but I think there is a bit more work needed around the validation/config
For instance this block https://github.com/apache/incubator-airflow/blob/master/airflow/configuration.py#L173-L188 doesn't make sense anymore, and it possibly makes sense to warn if the old config settings are found.
The metastore plugin won't work (be visible) anymore either - it still has |
@verdan Can you rebase? Would be good to get this merged, since we're now doing duplicate work :-) |
@ashb, to add the warnings for old config and integrate metastore blueprints for RBAC, I'd suggest to create new JIRA tickets, as both of these seems like new features. thoughts ? |
@Fokko @bolkedebruin ready for review. |
One more rebase? |
@Fokko two more rebase done 😉 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small comment @verdan
@ashb Are you okay with merging this on a short term? Otherwise, we'll end up with merge conflicts again. |
@kaxil sorry, just saw this. I am ok with your proposal. But based on @ashb last comment, it seems that we still have some work to do for this pr besides rebase. Does it get resolved? Do we have a time estimate on when it could be finished? If it is for a short period of time, we could go ahead with your approach :) |
Sorry @verdan can you rebase again? I will merge ASAP |
My comment about the plugin is still un-resolved - the metastore plugin (at least) won't work with the Flask-AppBuilder based UI I think |
@ashb I agree, but that is not the issue of this PR, although we should preferably fix it before a release. Why not have a blocker JIRA for 2.0 that raises this issue? |
Thanks, @verdan and sorry for having to rebase & fix conflicts for the nth time. Appreciate it. |
Thanks @verdan |
the new UI with role manager is pretty nice, but I have took lot of time to get it there. |
I have a problem where the webserver keeps repeating "some workers are starting up, waiting...", and I think it might be because of these changes. It seems that the worker processes no longer get the proper prefix after initialization, because the file gunicorn_config.py was deleted from airflow/www. Before deletion, it contained the post_worker_init function: airflow/airflow/www/gunicorn_config.py Lines 25 to 28 in cb8b2a1
Lines 874 to 883 in cb8b2a1
After your changes, get_num_ready_workers still expects the prefix: Lines 691 to 704 in c030729
@verdan Could you please confirm/refute |
And also why we rename www_rbac to www which causes all the git history missing? |
@feng-tao I agree it is not ideal. In the meantime, you can use this https://github.com/apache/airflow/commits/08eba5241cdfe7449c8f546715401743a5cf0d64/airflow/www_rbac to view git history. |
@diederikwp yup, you are right. 👍 |
Make sure you have checked all steps below.
Jira
Description
This PR removes the old UI and renames the references of
www_rbac
towww
.Tests
Commits
Documentation
Code Quality
flake8
All the help with manual testing would be highly appreciated 🙂