-
Notifications
You must be signed in to change notification settings - Fork 5k
fix(source-zendesk-talk): update CDK to prerelease version with OAuth race condition fix #72383
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
fix(source-zendesk-talk): update CDK to prerelease version with OAuth race condition fix #72383
Conversation
… race condition fix Co-Authored-By: [email protected] <[email protected]>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
👋 Greetings, Airbyte Team Member!Here are some helpful tips and reminders for your convenience. 💡 Show Tips and TricksPR Slash CommandsAirbyte Maintainers (that's you!) can execute the following slash commands on your PR:
📚 Show Repo GuidanceHelpful Resources
|
|
Co-Authored-By: [email protected] <[email protected]>
|
Deploy preview for airbyte-docs ready! ✅ Preview Built with commit b61132c. |
What
Updates the source-zendesk-talk connector to use a prerelease CDK version that fixes an OAuth race condition where multiple streams starting concurrently with an expired token would all attempt to refresh simultaneously, causing failures with single-use refresh tokens.
Related CDK PR: airbytehq/airbyte-python-cdk#883
How
Updates the
baseImageinmetadata.yamlfrom the stable7.6.5to the prerelease7.6.5.post3.dev21398747886which includes thread-safe token refresh with double-checked locking.Review guide
airbyte-integrations/connectors/source-zendesk-talk/metadata.yaml- CDK base image version update and version bumpUser Impact
Users authenticating via OAuth with rotating refresh tokens should no longer experience authentication failures when multiple streams start concurrently with an expired token.
Can this PR be safely reverted and rolled back?
Requested by: [email protected]
Link to Devin run: https://app.devin.ai/sessions/2f784e9440324787893047ac3a1c0fbc