dabla opened a new pull request, #71941:
URL: https://github.com/apache/airflow/pull/71941
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
https://chris.beams.io/posts/git-commit/
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.
For user-facing UI changes, please attach before/after screenshots (or a
short
screen recording) so reviewers can assess the visual impact.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
Workers deployed behind a corporate HTTP proxy fail to reach Google APIs
with a `socket.gaierror: Name or service not known` even when `HTTPS_PROXY` /
`HTTP_PROXY` are set. The root cause is non-obvious and not documented anywhere
in the provider:
`httplib2` (used by `google-api-python-client` for the `discovery`-based
hook path) does **not** implement HTTP CONNECT tunneling itself — it delegates
*all* proxying to PySocks. Without PySocks installed, `httplib2` silently skips
the proxy and makes a direct DNS lookup that fails in restricted networks.
This PR adds a dedicated "Corporate Proxy" section to the Google Cloud
connection reference documenting:
- the proxy env vars to set (`HTTPS_PROXY`, `HTTP_PROXY`, `NO_PROXY`) for
both
bare-metal and Kubernetes/Helm deployments
- the mandatory `pysocks` dependency and a clear explanation of *why* it is
required
even for an HTTP proxy when the target endpoint is HTTPS
- which hooks are affected (`discovery`-based: BigQuery Jobs API, Dataflow,
Compute,
Cloud SQL, Datastore, Cloud Functions, Marketing Platform, etc.) vs. which
are not
(newer `google-cloud-*` client hooks that use `requests` and already have
native
CONNECT support)
- a quick in-container verification checklist
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ x ] Yes (please specify the tool below)
Claude Sonnet 4.6 (GitHub Copilot)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
