Skip to content

Remove old UI and webserver - #46942

Merged
jedcunningham merged 55 commits into
mainfrom
remove-legacy-ui
Feb 27, 2025
Merged

jedcunningham merged 55 commits into
mainfrom
remove-legacy-ui

Conversation

@bbovenzi

Copy link
Copy Markdown
Contributor

excited-fuego

Try to strip out as much of the old webserver and UI as possible for AIP-79.


^ 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.rst or {issue_number}.significant.rst, in newsfragments.

@jedcunningham

Copy link
Copy Markdown
Member

So we don't loose it from the original PR: #protm!

@Lee-W Lee-W mentioned this pull request Feb 21, 2025
1 of 2 tasks
@Lee-W
Lee-W self-requested a review February 21, 2025 03:15
@uranusjr

uranusjr commented Feb 21, 2025 •

Copy link
Copy Markdown
Member

Now we removed www, FAB is not automatically set up for tests. This is causing problems in FAB provider tests.

@jscheffl

Copy link
Copy Markdown
Contributor

I'm starrting to take a look into failing breeze tests...

@potiuk

potiuk commented Feb 21, 2025

Copy link
Copy Markdown
Member

I did too @jscheffl -> fixed some more

@jscheffl

Copy link
Copy Markdown
Contributor

I did too @jscheffl -> fixed some more

I was unsure and wated to contact you.... but you fixed what I suspected and wondered why this was the impact.

@potiuk

potiuk commented Feb 21, 2025

Copy link
Copy Markdown
Member

I was unsure and wated to contact you.... but you fixed what I suspected and wondered why this was the impact.

fab provider is added as amazon's optional dependency -> that triggers the tests transitively

@jscheffl

Copy link
Copy Markdown
Contributor

I was attempting to make some fixes to the pytests failing, but I am missing an idea how the previous mocked app based on appbuilder+Flask can be replicated over. I fear either we need to re-write a lot of tests or we need to add the dependency to FAB provider... which is also not helpful.
A common solution would be great but I am lagging an idea.

@potiuk

potiuk commented Feb 23, 2025 •

Copy link
Copy Markdown
Member

I was attempting to make some fixes to the pytests failing, but I am missing an idea how the previous mocked app based on appbuilder+Flask can be replicated over. I fear either we need to re-write a lot of tests or we need to add the dependency to FAB provider... which is also not helpful.
A common solution would be great but I am lagging an idea.

I think it's a matter of adding the right fixture to tests_common so that it can be used with those tests - following the new "fast_api" way of initializing the app, but I also lack a bit of understanding how it is done now without doing a lot of digging

@jedcunningham

Copy link
Copy Markdown
Member

@pierrejeambrun @bbovenzi take a look at 6a01eaa - I didn't want to tackle a general "build arbitrary url" helper, so I just did dagrun. Is there something existing for this use case though?

@pierrejeambrun

pierrejeambrun commented Feb 24, 2025 •

Copy link
Copy Markdown
Member

@pierrejeambrun @bbovenzi take a look at 6a01eaa - I didn't want to tackle a general "build arbitrary url" helper, so I just did dagrun. Is there something existing for this use case though?

Looks nice. I am not aware of anything that can achieve this in the new web stack.

@potiuk

potiuk commented Feb 24, 2025

Copy link
Copy Markdown
Member

Looking promising !

Comment thread clients/python/test_python_client.py Resolved
@potiuk

potiuk commented Feb 26, 2025

Copy link
Copy Markdown
Member

All good - it should be ✅ hopefully - all remaining things in comments.

@jedcunningham
jedcunningham merged commit 5141554 into main Feb 27, 2025
@bbovenzi

Copy link
Copy Markdown
Contributor Author

gif

@bbovenzi
bbovenzi deleted the remove-legacy-ui branch February 27, 2025 02:00
@bugraoz93

Copy link
Copy Markdown
Contributor

End of an era, amazing work!

@pierrejeambrun

Copy link
Copy Markdown
Member

🎉 🎉

@jscheffl

Copy link
Copy Markdown
Contributor

Wow. I did not expect it gets merged this week :-D Good job!

@jscheffl jscheffl mentioned this pull request Feb 27, 2025
@potiuk

potiuk commented Feb 27, 2025

Copy link
Copy Markdown
Member

Beta release today sped up the work :)

ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Feb 28, 2025
ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Feb 28, 2025
Co-authored-by: Ash Berlin-Taylor <ash@apache.org>
Co-authored-by: Jed Cunningham <jedcunningham@apache.org>
Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
Co-authored-by: vincbeck <vincbeck@amazon.com>
Co-authored-by: Jens Scheffler <jscheffl@apache.org>
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
Co-authored-by: vatsrahul1001 <43964496+vatsrahul1001@users.noreply.github.com>
Co-authored-by: GPK <gopidesupavan@gmail.com>
Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
potiuk added a commit to potiuk/airflow that referenced this pull request Feb 28, 2025
After apache#46942 - we should wait for UI not WWW asset compilation in
the start-airlfow command.
potiuk added a commit that referenced this pull request Feb 28, 2025
…47202)

After #46942 - we should wait for UI not WWW asset compilation in
the start-airlfow command.
@shahar1

shahar1 commented Mar 1, 2025

Copy link
Copy Markdown
Contributor

Well done!

aaron-y-chen pushed a commit to aaron-y-chen/airflow that referenced this pull request Apr 4, 2025
aaron-y-chen pushed a commit to aaron-y-chen/airflow that referenced this pull request Apr 4, 2025
Co-authored-by: Ash Berlin-Taylor <ash@apache.org>
Co-authored-by: Jed Cunningham <jedcunningham@apache.org>
Co-authored-by: Tzu-ping Chung <uranusjr@gmail.com>
Co-authored-by: vincbeck <vincbeck@amazon.com>
Co-authored-by: Jens Scheffler <jscheffl@apache.org>
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
Co-authored-by: vatsrahul1001 <43964496+vatsrahul1001@users.noreply.github.com>
Co-authored-by: GPK <gopidesupavan@gmail.com>
Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
aaron-y-chen pushed a commit to aaron-y-chen/airflow that referenced this pull request Apr 4, 2025
…pache#47202)

After apache#46942 - we should wait for UI not WWW asset compilation in
the start-airlfow command.
potiuk pushed a commit that referenced this pull request Sep 12, 2026
…up (#73025)

The readiness banner is the signal developers wait on before opening the
browser, so it has to account for the component that serves it. The API
server is the slowest of the four to come up, and until it binds its port
the banner points users at a connection they cannot make.

The port check existed from the command's introduction and was lost as
collateral damage when the old webserver was removed: #46942 deleted the
attribute holding the port but left the call reading it, and the follow-up
hot-fix #47145 resolved the resulting AttributeError by deleting the call
rather than repointing it at the renamed config key. The probe and its
tests have been unreachable since.

Resolving the port once during startup, as the pre-#47145 code did, also
keeps a raising config lookup out of the poll loop, whose only handler is
KeyboardInterrupt and whose component shutdown sits after the try block.

Co-authored-by: Eason09053360 <185830721+Eason09053360@users.noreply.github.com>
xvega pushed a commit to xvega/airflow that referenced this pull request Sep 13, 2026
…up (apache#73025)

The readiness banner is the signal developers wait on before opening the
browser, so it has to account for the component that serves it. The API
server is the slowest of the four to come up, and until it binds its port
the banner points users at a connection they cannot make.

The port check existed from the command's introduction and was lost as
collateral damage when the old webserver was removed: apache#46942 deleted the
attribute holding the port but left the call reading it, and the follow-up
hot-fix apache#47145 resolved the resulting AttributeError by deleting the call
rather than repointing it at the renamed config key. The probe and its
tests have been unreachable since.

Resolving the port once during startup, as the pre-apache#47145 code did, also
keeps a raising config lookup out of the poll loop, whose only handler is
KeyboardInterrupt and whose component shutdown sits after the try block.

Co-authored-by: Eason09053360 <185830721+Eason09053360@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:CLI area:dev-tools area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.