emery-finkelstein opened a new issue, #73163:
URL: https://github.com/apache/airflow/issues/73163

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   Airflow 3.3.1
   
   ### What happened and how to reproduce it?
   
   [Configure Google Secrets Backend 
](https://airflow.apache.org/docs/apache-airflow-providers-google/stable/secrets-backends/google-cloud-secret-manager-backend.html)
 To be the primary source for connections.
   
   Add an HTTP connection into the environment with an endpoint that's a public 
website (ie: apache.org).
   It doesn't matter if the connection is provided by the Google Sercrets 
Backend, in the environment directly. So long as the secrets mangager lookup 
occurs.
   
   Set up a task that makes multiple HTTP requests given a hook.
   ```
   @task
   def sample_task(http_conn_id=None)
      hook = HTTPHook(http_conn_id)
      for i in range(10):
         hook.run()
   
   ```
   
   `Getting connection using google.auth.default()` is logged on each iteration.
   
   
   
   
   ### What you think should happen instead?
   
   Secrets manager shouldn't be logging that it's using default credentials on 
each iteration.
   
   Maybe the HTTPHook could cache the connection, to prevent consistent lookups 
of the connection.
   Maybe the Google Secrets Backend can suppress this message (especially when 
running in a cloud composer environment where ADC is the expected method of 
authenticating with the Secret store).
   
   ### Operating System
   
   Cloud composer 3. 
   
   ### Deployment
   
   Google Managed Service for Apache Airflow
   
   ### Apache Airflow Provider(s)
   
   google
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-google==22.3.0
   apache-airflow-providers-http==6.0.5
   
   
   ### Official Helm Chart version
   
   _No response_
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   Normally I'd be willing to submit a PR, but there's too much to untangle 
here, and it's not clear what the best way to handle this is.
   
   ### 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