Remove old UI and webserver

[bbovenzi]

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]

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

[uranusjr]

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

[jscheffl]

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

[potiuk]

I did too @jscheffl -> fixed some more

[jscheffl]

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]

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]

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]

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]

@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 @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]

Looking promising !

[jscheffl]

Wow! Looks pretty green now! Should we maybe run "full tests" and "all version" before merge?

e.g. K8s tests seem not to be fired in the pipeline... --> Ah, they are "just pending"...

[jscheffl]

Reviewed all changed files... looks good! (besides the other comments open)

[potiuk]

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

[bbovenzi]

[bugraoz93]

End of an era, amazing work!

[pierrejeambrun]

🎉 🎉

[jscheffl]

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

[potiuk]

Beta release today sped up the work :)

[shahar1]

Well done!