potiuk opened a new pull request #17052:
URL: https://github.com/apache/airflow/pull/17052


   The docker-compose v2 parsing of env file bug detected
   in #16949 and eventual disabling of docker-compose-v2 in #16989
   found another workaround after discussing with docker-compose
   maintainers in https://github.com/docker/compose-cli/issues/1917
   
   The VAR=${VAR} pattern seems to work for all cases for Airflow
   because we never rely on the fact if variable is set or not -
   we always take into account value of the variable (that is by
   design and strictly followed everywhere). Therefore we are
   sure this workaround is going to work for us.
   
   However we should remove that workaround once the bug is fixed in
   Docker-Compose V2.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+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 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.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