The GitHub Actions job "Tests" on airflow.git has succeeded.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
53ff3e2228423a7712a65cbed04620aed3ec9741 / Jarek Potiuk <[email protected]>
Include plugins in the architecture diagrams

When it comes to access and management plugins management follows
different pattern than DAG files. While DAG files can (and should) be
modified by DAG authors, the whole idea of Plugins was to make it only
possible to modify plugins folder (and installl plugin-enabled packages)
by the Deploymenet Managers, not DAG authors.

The difference is quite important because even in a simplest
installation, airflow webserver never needs to access DAG files, while
it should be able to access plugins.

This is even more profound in the environment (leading in the future to
multi-tenant deployments) plugins are not 'per-tenant" - they must be
installed and managed by deployment manager, because those plugins can
be used by Airflow Webservers.

In the future we might want to make distinction between these two
different types of plugins, because theorethically it would be possible
to distingquish "scheduler, worker & triggerer" plugins from the
"webserver" plugins - however we do not have such disctinction today and
whoever manages plugins folder is impacting both webserver and workers.

This change also re-adds the "basic" architecture which is targetted
as single-user and single machine deployment and presents it as the
first architecture that the user encounters - which might make it more
digestible, while it also explains tha this is a simplified architecture
and is followed by more complete and complex deployment scenarios
involving distributed architecture, different user roles and security
boundaries.

Report URL: https://github.com/apache/airflow/actions/runs/7372354711

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to