Migrate Airbyte provider to airbyte-api library 1.0 and httpx#68882
Conversation
… for airbyte-api>=1.0 airbyte-api 1.0.0rc2 switched its HTTP layer from requests to httpx. The client parameter now requires an httpx-compatible HttpClient protocol and no longer accepts requests.Session. Changes: - Replace requests.Session proxy setup with httpx.Client(mounts=...) - Update pyproject.toml: airbyte-api>=1.0.0rc2, httpx>=0.28.1, drop requests - Update test to assert isinstance(client, httpx.Client) instead of checking .proxies attribute (not available on httpx.Client) Co-Authored-By: AJ Steers <aj@airbyte.io>
Co-Authored-By: AJ Steers <aj@airbyte.io>
- Test now verifies proxy transport mounts are configured per-scheme - Bump airbyte-api lower bound from >=1.0.0rc2 to >=1.0.0 (GA released) Co-Authored-By: AJ Steers <aj@airbyte.io>
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
|
|
I encountered the same Airbyte compatibility failure in an unrelated PR, so I took a look here, and this PR seems to be addressing the same underlying issue. One small Airflow-specific thing: the PR title currently uses a prefix like I noticed this is still in draft. If you are short on time, I’d be happy to help! |
airbyte-api>=1.0.0rc2 and httpx.Clientairbyte-api library 1.0 and httpx
Co-Authored-By: AJ Steers <aj@airbyte.io>
Co-Authored-By: AJ Steers <aj@airbyte.io>
…-to-airbyte-api-1.0
Co-Authored-By: AJ Steers <aj@airbyte.io>
|
@aaronsteers can you fix the static checks? there are some failures |
|
Quickest fix: git fetch upstream main && git rebase upstream/main
rm uv.lock && uv lock
git add uv.lock && git rebase --continue
git push --force-with-leaseAutomated nudge — ignore if you're not ready to rebase. This comment is updated in place on future |
…er section Co-Authored-By: AJ Steers <aj@airbyte.io>
…igration Co-Authored-By: AJ Steers <aj@airbyte.io>
|
@eladkal - Do you mind approving checks again? I believe we've resolved the failures, and for safety (transitive dependencies changed), I proposed a version bump to 6.0.0, reflecting (at least potentially) breaking changes in this update. |
…breaking Per reviewer feedback, this is not an Airflow-code breaking change, so the version stays release-manager-managed (5.5.2) rather than a hardcoded 6.0.0 bump. The manual 6.0.0 entry in provider.yaml also broke the prepare-provider-documentation CI step, which diffs against the previous version tag (providers-airbyte/5.5.2) that is not yet released. Retitle the changelog section from 'Breaking changes' to 'Transitive dependency changes' and drop the 6.0.0 header. Co-Authored-By: AJ Steers <aj@airbyte.io>
eladkal
left a comment
There was a problem hiding this comment.
LGTM will merge when CI is green
|
Merging. Static checks failure is not related to this PR |
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
Was generative AI tooling used to co-author this PR?
Generated-by: Devin.ai following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.