bobu-putheeckal opened a new pull request, #67440:
URL: https://github.com/apache/airflow/pull/67440

   ## Why\n\n`get_async_connection` always called methods through `BaseHook`, 
so async provider hooks such as subclasses of `HttpAsyncHook` could bypass 
subclass `aget_connection` / `get_connection` overrides while resolving 
triggerer-side connections.\n\n## What\n\n- Allow the common compat async 
connection helper to receive the requesting hook class, defaulting to 
`BaseHook` for existing callers.\n- Pass `type(self)` from 
`HttpAsyncHook.config()` so subclass overrides participate in normal 
classmethod dispatch.\n- Add focused tests for async and sync override 
dispatch, plus an HTTP async hook regression test.\n\ncloses: #66845\n\n## 
Tests\n\n- `uv run --project providers/common/compat --group dev pytest 
providers/common/compat/tests/unit/common/compat/connection/test_connection.py`\n-
 `uv run --project providers/http --group dev pytest 
providers/http/tests/unit/http/hooks/test_http.py::TestHttpAsyncHook::test_config_uses_subclass_aget_connection`\n-
 `uv run --project providers/http
  --group dev ruff format 
providers/common/compat/src/airflow/providers/common/compat/connection/__init__.py
 providers/common/compat/tests/unit/common/compat/connection/test_connection.py 
providers/http/src/airflow/providers/http/hooks/http.py 
providers/http/tests/unit/http/hooks/test_http.py`\n- `uv run --project 
providers/http --group dev ruff check 
providers/common/compat/src/airflow/providers/common/compat/connection/__init__.py
 providers/common/compat/tests/unit/common/compat/connection/test_connection.py 
providers/http/src/airflow/providers/http/hooks/http.py 
providers/http/tests/unit/http/hooks/test_http.py`\n\n##### Was generative AI 
tooling used to co-author this PR?\n\n- [X] Yes: OpenAI Codex\n\nGenerated-by: 
OpenAI Codex


-- 
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