uplsh580 opened a new issue, #60722:
URL: https://github.com/apache/airflow/issues/60722

   ### What do you see as an issue?
   
   # Description
   Currently, the official Airflow Docker image explicitly sets the environment 
variable `AIRFLOW__CORE__LOAD_EXAMPLES` to `false` by default 
([reference](https://github.com/apache/airflow/blob/0d07c70ae3a67b0fb7d9490a972eb06c2a9f1bcc/Dockerfile#L2052)).
   
   While the [Configuration 
Reference](https://airflow.apache.org/docs/apache-airflow/3.1.6/configurations-ref.html#load-examples)
 
([Code](https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/config_templates/config.yml#L173-L177))
 mentions that the default value for `load_examples` is `True`, it doesn't 
mention that this is overridden in the official image. This can be confusing 
for users who expect example DAGs to be present when they first run the 
official image but find them missing.
   
   **Proposed Change**
   I suggest adding a note to the `load_examples` section in the documentation 
to inform users about this behavior in the official image.
   
   **Suggested addition to the docs:**
   
   > Note: If you are using the Official Airflow Docker Image, this value is 
set to `False` by default via the environment variable 
`AIRFLOW__CORE__LOAD_EXAMPLES`. To enable example DAGs when using the official 
image, you must explicitly set `AIRFLOW__CORE__LOAD_EXAMPLES=True` in your 
environment.
   
   
   ### Solving the problem
   
   _No response_
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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

Reply via email to