-
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-3761] Decommission User & Chart models & Update doc accordingly #4577
[AIRFLOW-3761] Decommission User & Chart models & Update doc accordingly #4577
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4577 +/- ##
==========================================
+ Coverage 74.16% 74.17% +<.01%
==========================================
Files 421 421
Lines 27773 27733 -40
==========================================
- Hits 20598 20570 -28
+ Misses 7175 7163 -12
Continue to review full report at Codecov.
|
This is not the right way to do it in alembic. You should create a New migration script that drops the tables and fields and re-adds them on a downgrade. The way it is structured now does not properly work with upgrades and downgrades. |
Thanks @bolkedebruin . New to Alembic. Let me check & commit again later. Other than Alembic part, any other comment? Thanks! |
f3d5e36
to
a216889
Compare
a216889
to
5ac3b52
Compare
Addressed the comment on Alembic. PTAL @bolkedebruin @ashb |
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.
LGTM. @bolkedebruin any other comments?
There is a conflict for
|
A gentle ping, @ashb @bolkedebruin . In addition, the conflict I mentioned above was resolved by b6f207f |
In master branch, we have already decommissioned the Flask-Admin UI. In model definitions, User and Chart are only applicable for the "old" UI based on Flask-Admin. Hence we should decommission these two models as well. Related doc are updated in this commit as well.
5ac3b52
to
5227446
Compare
Rebased as suggested @feng-tao . Thanks. |
…gly (apache#4577) In master branch, we have already decommissioned the Flask-Admin UI. In model definitions, User and Chart are only applicable for the "old" UI based on Flask-Admin. Hence we should decommission these two models as well. Related doc are updated in this commit as well.
…gly (apache#4577) In master branch, we have already decommissioned the Flask-Admin UI. In model definitions, User and Chart are only applicable for the "old" UI based on Flask-Admin. Hence we should decommission these two models as well. Related doc are updated in this commit as well.
Hi @zhongjiajie, there are still two sets of web UI supported in 1.10.*, so this patch should only be in master branch for now. Correct me if I’m wrong. |
@XD-DENG You’r right, I find it still use
|
@zhongjiajie but you're right that the documentation is somehow out-dated, especially the I'm preparing a PR to address this issue and further housekeep out-dated code & doc. Will raise the PR soon this week. Will tag you then. And big congrats again for your nomination as committer! Welcome aboard! |
Yeah, I think we should still change the doc, cause user should change the |
Thanks Xiao Dong |
Good to see you again @XD-DENG . Looking forward for the PR |
Indeed good to see you back @XD-DENG ! |
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch.
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch.
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
- All authentication backends in `airflow/contrib/auth` are base on the `user` model which has already been removed earlier (apache/airflow#4577 (comment)) - Security related documentation is out-dated, especially the LDAP and OAuth integration sections. It still directs user to the configuration of "old" web UI which has already been removed in master branch. GitOrigin-RevId: 3a7b741ab9ed0937571c77a10b5d244f14eaf7db
Jira
Description
Background
In master branch, we have already decommissioned the Flask-Admin UI.
What have been done
In model definitions, User and Chart are only applicable for the "old" UI based on Flask-Admin. Hence we should decommission these two models as well.
Alembic updated accordingly
Related doc are updated in this commit as well (like
profiling
section is no longer applicable).