Dev-iL opened a new pull request, #60278:
URL: https://github.com/apache/airflow/pull/60278

   ```diff
   - This PR was created with the help of AI
   ```
   
   Depends on: #60270 
   
   ### Context
   When using Git DAG bundles with user impersonation (`run_as_user`), tasks 
fail due to permission conflicts. The bundle is cloned by the main airflow 
user, but the impersonated user needs to access the repository files during 
task execution.
   
   #### Specific issues addressed:
   
   1. Repository file permissions: Cloned repositories inherit default umask 
permissions, which may not allow group access for impersonated users
   1. Git "dubious ownership" error: Git 2.35.2+ refuses to operate on 
repositories owned by different users without explicit safe.directory 
configuration
   
   ### Changes
   1. `_apply_permissions_recursively(path)`
   New helper function that walks a directory tree and applies the configured 
dag_bundle_new_folder_permissions and dag_bundle_new_file_permissions to all 
directories and files.
   
   1. `_configure_git_safe_directory(path)`
   New helper function that adds the repository path to git's global 
`safe.directory` configuration, allowing git operations by users who don't own 
the repository.
   
   ### Related Changes
   This is part 2 of 3 PRs to fully address the impersonation + bundles issue:
   
   - #60270: airflow-core - Add permission configuration and apply to 
lock/tracking files
   - PR 2 (this one): providers/git - Apply permissions to cloned repositories 
and configure git safe.directory
   - PR 3: task-sdk - Add startup warning when permissions may cause 
impersonation issues
   <!--
    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