Versions Compared

Old Version 3

changes.mady.by.user Unknown User (kaxilnaik)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (bbovenzi)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Many plugins, especially UI-facing ones, use FAB to generate views or create custom models. Those will have to be rewritten to interface with a modern React UI and a new webserver REST API. AIP-68 New Plugin Interface goes into more detail on how this can be implemented and provide new ways for plugins to connect into the Airflow UI.

Plugins

This AIP should be implemented jointly with AIP-68 Extended Plugin Interface for React Views. Removing FAB will mean we will lose the appbuilder_views, and appbuilder_menu_items attributes on a Plugin. AIP-68 will need to be extended here to replace the lost FAB functionality with new javascript powered views. Legacy UI plugins will not work out-of-the-box.

How are users affected?

  • Users will lose the ability to use the FAB Auth Manager and any legacy UI plugins out-of-the-box
  • Users will get a fast and responsive UI
  • Contributors will have an easy time making changes to Airflow with more standardized linting and testing
  • A lot of views are subject to be redesigned as we rebuild them
  • The UI completely relying on rest APIs vs FAB will result in the public REST API becoming more expansive and powerful for 3rd party users