-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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 Google Ads: Better error message handling in check connection #11371
🎉 Source Google Ads: Better error message handling in check connection #11371
Conversation
/test connector=connectors/source-google-ads
|
/publish connector=connectors/source-google-ads |
/publish connector=connectors/source-google-ads |
/publish connector=connectors/source-google-ads
|
What
Previously, if
check_connection
received an error response from Google's API, we would just stringify the response and dump it into the UI (#10786 (comment)). Now we are extracting the error message so it's formatted nicely:Also, we were throwing exceptions rather than returning a
(booleanSuccess, stringMessage)
tuple in some cases; fix that. This manifested as a slightly ugly error message.How
We receive back one (or more) error structs. Extract the
message
from them.We ignore the other fields, which could hide useful information? But I tested a couple different incorrect configs and they all had reasonable error messages. Also, the full exception is logged, so it's still available if needed.
🚨 User Impact 🚨
none
Pre-merge Checklist
Expand the relevant checklist and delete the others.
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 here