zorzigio commented on issue #15572:
URL: https://github.com/apache/airflow/issues/15572#issuecomment-861322038


   @sawaca96
   
   > I want to get more information. then I can try to find cause.
   >What helm chart are you using ? I'm use airflow-stable
   
   I am using the official Helm Chart 
([apache-airflow/airflow](https://github.com/apache/airflow/tree/main/chart))
   
   >I don't think so. but if you want to use module in dags folder then you 
should include dags path.
   
   In the [Airflow 
documentation](https://airflow.apache.org/docs/apache-airflow/stable/modules_management.html#additional-modules-in-airflow)
 it is mentioned:
   
   > Airflow adds three additional directories to the sys.path
   > - DAGS folder: It is configured with option dags_folder in section [core].
   > - Config folder: It is configured by setting AIRFLOW_HOME variable 
({AIRFLOW_HOME}/config) by default.
   > - Plugins Folder: It is configured with option plugins_folder in section 
[core].
   
   However when running `print(sys.path)`, these folder do not appear (see 
[post](https://github.com/apache/airflow/issues/15572#issue-869913582))
   
   >I use this offical values.yaml, I can't find env section
   
   Here it is ([env 
section](https://github.com/apache/airflow/blob/1fba5402bb14b3ffa6429fdc683121935f88472f/chart/values.yaml#L173))
   
   >In addition, explain extraEnv
   
   Here is that section too 
([extraEnv](https://github.com/apache/airflow/blob/1fba5402bb14b3ffa6429fdc683121935f88472f/chart/values.yaml#L219))
   
   > Note
   > change PYTHONPATH: /opt/airflow/dags/repo to PYTHONPATH: 
$PYTHONPATH:/opt/airflow/dags/repo
   > The former overwrites(existing path lost) the existing path and the latter 
is added to the existing path.
   
   The `PYTHONPATH` was not defined in the pods, so this makes no difference
   
   


-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to