shubhamraj-git opened a new pull request, #46628:
URL: https://github.com/apache/airflow/pull/46628
Usually, the files added to `../files/dags` and `../files/plugins` on the
local gets loaded and visible on the UI.
But using
```
breeze start-airflow --use-airflow-version 2.10.5rc1 --python 3.9 --backend
postgres --executor CeleryExecutor
````
dags get loaded using mentioned path but plugins in the mentioned path, is
not loaded in case of particular airflow version.
-------------------
We have a solution, thanks to @potiuk
If you look at the local.yml (which is the default, you will find:
```
environment:
- AIRFLOW__CORE__PLUGINS_FOLDER=/files/plugins
```
We already have files.yml compose added as well in all cases with this
content - so /files is already mounted:
```
services:
airflow:
volumes:
- ../../../files:/files:cached
- ../../../dist:/dist:cached
```
So effectively adding this to remove.yml - similarly as we have in local.yml
should fix the problem
```
environment:
AIRFLOW__CORE__PLUGINS_FOLDER=/files/plugins
```
Slack thread:
https://apache-airflow.slack.com/archives/CQ9QHSFQX/p1739118683352799
<!-- Please keep an empty line above the dashes. -->
---
**^ Add meaningful description above**
Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information.
In case of fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
In case of a new dependency, check compliance with the [ASF 3rd Party
License Policy](https://www.apache.org/legal/resolved.html#category-x).
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](https://github.com/apache/airflow/tree/main/newsfragments).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
