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

   The docker compose tests on linux have been broken by #49681 because of:
   
   a) perrmission problems with config folder - airflow.cfg created
      eventually was owned by root, not airflow user and it was not
      readable by the airflow user
   b) the airflow.cfg has not been initialized in init because airflow
      version command does not create config
   c) config directory has not been crated in the docker-compose test d) /opts/ 
directory was used to create dirs instead of /opt/ when
      changing permissions
   e) chown -R does not work across the volumes
   
   Also it turned out that diagnostic in case of health-check problms has been 
broken and did not show the actual errors - because while handling exception of 
health check api calls were made that also raised exception that was 
subsequently silently swallowed and did not allow the logs and heealth-check 
information from the test to be printed.
   
   This PR fixes those problems:
   
   a) creates config folder during tests
   b) runs "airflow config list" in init that actually creates a
      default config when no manual configuration is specified
   c) changes ownership for the internal folders after the config
      file is created which allows airflow user to read it, also
      spearately changes ownership for /opt/airflow (volume in image)
      and all the shared volumes mounted from the host.
   d) improves diagnostic by switching to rich print and handing the
      health exceptions during exception handling, allowing to print
      detailed logs of what happened
   e) the output of `breeze testing docker-compose-tests` is printed
      directly to stdout (with pytest `-s` flag) - so that we see
      the progress of test as it happens - both locally and in CI.
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   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 an 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/
   -->
   
   
   
   <!-- 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 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/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]

Reply via email to