atul-astronomer opened a new issue, #48753:
URL: https://github.com/apache/airflow/issues/48753

   ### Apache Airflow version
   
   main (development)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   Dag processor is asking for passphrase everytime its refreshing GitDagBundle.
   This is happening when user has set passphrase instead of keeping it empty
   
   <img width="1595" alt="Image" 
src="https://github.com/user-attachments/assets/2dc4c099-90e9-4a3c-8bff-b91567fe72c8";
 />
   
   ### What you think should happen instead?
   
   _No response_
   
   ### How to reproduce
   
   This is happening when user is trying to read the dags from git bundle.
   
   **init.sh:**
   ```python
   export AIRFLOW_CONN_GIT_DEFAULT='{
     "conn_type": "git",
     "host": "[email protected]:astronomer/qa-scenario-dags.git",
     "extra": {
       "key_file": "/files/pek.txt"
     }
   }'
   
   export AIRFLOW__DAG_PROCESSOR__DAG_BUNDLE_CONFIG_LIST='[
     {
       "name": "qa_scenario_dags",
       "classpath": "airflow.providers.git.bundles.git.GitDagBundle",
        "kwargs": {
           "subdir": "dags",
           "tracking_ref": "3.0-1-master",
           "refresh_interval": 5
           }
   }]'
   ``` 
   
   ### Operating System
   
   Linux
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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