Kache opened a new issue, #35758:
URL: https://github.com/apache/airflow/issues/35758
### Apache Airflow version
2.7.3
### What happened
`DockerOperator`'s [`env_file`
param](https://github.com/apache/airflow/blob/f8dd19248345ac259153812c68b65fc39accfcfd/airflow/provider
Taragolis commented on issue #35758:
URL: https://github.com/apache/airflow/issues/35758#issuecomment-1819574511
As far as I remember this attribute utilise Templated Fields mechanism and
expected path to the template file .. which evaluated to the string, as you
mention into the example.
potiuk commented on issue #35758:
URL: https://github.com/apache/airflow/issues/35758#issuecomment-1819886545
Yes. It is just a documentation issue only. If you specify value that ends
with .env - it will be expanded from file:
```
template_ext: Sequence[str] = (
".s
Kache commented on issue #35758:
URL: https://github.com/apache/airflow/issues/35758#issuecomment-1819937399
Oh, I see, it's a requirement that the file is under `dag.folder` by default
(or extra paths added to `dag.template_searchpath`)
--
This is an automated message from the Apache Git
Kache closed issue #35758: `DockerOperator`'s `env_file` param accepts "file
contents as text" and not "path to dotenv file"
URL: https://github.com/apache/airflow/issues/35758
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
Taragolis commented on issue #35758:
URL: https://github.com/apache/airflow/issues/35758#issuecomment-1821319884
> In Airflow 2.8.* + you will even be able to pass LieteralValue so that you
could even add "env_file" content which ends with ".env" when you do not want
to expand. https://gith
