-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Source Recharge: use default availability strategy #22473
Source Recharge: use default availability strategy #22473
Conversation
/test connector=connectors/source-recharge
Build FailedTest summary info:
|
Airbyte Code Coverage
|
/test connector=connectors/source-recharge
|
/test connector=connectors/source-recharge
Build FailedTest summary info:
|
/test connector=connectors/source-recharge |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also remove the custom error handling here, as it shouldn't be necessary anymore! :)
/test connector=connectors/source-recharge
Build PassedTest summary info:
|
@erohmensing can you please specify again what piece of code you are mentioning, because the link that you provided points to recharge.md diff (updated it to include PR number in the changelog though) |
@arsenlosenko Sorry about that! It'd be this part of
we can remove that |
/test connector=connectors/source-recharge
Build PassedTest summary info:
|
/test connector=connectors/source-recharge
Build PassedTest summary info:
|
* Source Recharge: use default availability strategy * Remove invalid_config from full_refresh tests * Update changelog * Remove error handling that is covered by HttpAvailabilityStrategy * Keep should_retry, change error handling --------- Co-authored-by: Serhii Lazebnyi <53845333+lazebnyi@users.noreply.github.com>
What
Resolving:
#21784
How
Enable default availability strategy, specify
AllowedHosts
Recommended reading order
x.java
y.python
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user? If yes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changes